firmware: Be a bit more verbose about direct firmware loading failure
authorNeil Horman <nhorman@tuxdriver.com>
Fri, 6 Sep 2013 19:36:08 +0000 (15:36 -0400)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 26 Sep 2013 22:35:30 +0000 (15:35 -0700)
commit3e358ac2bb5bb9c9f4842145ca0da2384d13fd98
tree2cce5ee4430e67107d5b82c6518a8a6c9ce21447
parentcfec0bc835c84d3d3723d4955587f05a94879b26
firmware: Be a bit more verbose about direct firmware loading failure

The direct firmware loading interface is a bit quiet about failures.  Failures
that occur during loading are masked if firmware exists in multiple locations,
and may be masked entirely in the event that we fall back to the user mode
helper code.  It would be nice to see some of the more unexpected errors get
logged, so in the event that you expect the direct firmware loader to work (like
if CONFIG_FW_LOADER_USER_HELPER is enabled), and something goes wrong, you can
figure out what happened.

Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Acked-by: Ming Lei <ming.lei@canonical.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/base/firmware_class.c