diff options
author | Luis R. Rodriguez <[email protected]> | 2014-07-02 09:55:05 -0700 |
---|---|---|
committer | Greg Kroah-Hartman <[email protected]> | 2014-07-08 15:28:16 -0700 |
commit | c868edf42b4db89907b467c92b7f035c8c1cb0e5 (patch) | |
tree | 739f930880e8c098f01f88eb44a0bb5fac2c54c3 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | a76040d835776f0e8cc2bf5f9edcfa2092449ae9 (diff) |
firmware loader: inform direct failure when udev loader is disabled
Now that the udev firmware loader is optional request_firmware()
will not provide any information on the kernel ring buffer if
direct firmware loading failed and udev firmware loading is disabled.
If no information is needed request_firmware_direct() should be used
for optional firmware, at which point drivers can take on the onus
over informing of any failures, if udev firmware loading is disabled
though we should at the very least provide some sort of information
as when the udev loader was enabled by default back in the days.
With this change with a simple firmware load test module [0]:
Example output without FW_LOADER_USER_HELPER_FALLBACK
platform fake-dev.0: Direct firmware load for fake.bin failed
with error -2
Example with FW_LOADER_USER_HELPER_FALLBACK
platform fake-dev.0: Direct firmware load for fake.bin failed with error -2
platform fake-dev.0: Falling back to user helper
Without this change without FW_LOADER_USER_HELPER_FALLBACK we
get no output logged upon failure.
Cc: Tom Gundersen <[email protected]>
Cc: Ming Lei <[email protected]>
Cc: Abhay Salunke <[email protected]>
Cc: Stefan Roese <[email protected]>
Cc: Arnd Bergmann <[email protected]>
Cc: Kay Sievers <[email protected]>
Signed-off-by: Luis R. Rodriguez <[email protected]>
Reviewed-by: Takashi Iwai <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions