leandrof/linux
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Documentation: fix few typos and clarifications for the firmware loader

Browse Source 
Fix a few typos, and clarify a few sentences.

Reviewed-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
Luis R. Rodriguez
2018-05-10 13:08:48 -07:00
committed by Greg Kroah-Hartman
parent 1bc4d68b06
commit 4fde24d416
2 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
Documentation/driver-api/firmware/fallback-mechanisms.rst
View File

@@ -83,7 +83,7 @@ and a file upload firmware into:
* /sys/$DEVPATH/data * /sys/$DEVPATH/data
To upload firmware you will echo 1 onto the loading file to indicate To upload firmware you will echo 1 onto the loading file to indicate
you are loading firmware. You then cat the firmware into the data file, you are loading firmware. You then write the firmware into the data file,
and you notify the kernel the firmware is ready by echo'ing 0 onto and you notify the kernel the firmware is ready by echo'ing 0 onto
the loading file. the loading file.
@@ -136,7 +136,8 @@ by kobject uevents. This is specially exacerbated due to the fact that most
distributions today disable CONFIG_FW_LOADER_USER_HELPER_FALLBACK. distributions today disable CONFIG_FW_LOADER_USER_HELPER_FALLBACK.
Refer to do_firmware_uevent() for details of the kobject event variables Refer to do_firmware_uevent() for details of the kobject event variables
setup. Variables passwdd with a kobject add event: setup. The variables currently passed to userspace with a "kobject add"
event are:
* FIRMWARE=firmware name * FIRMWARE=firmware name
* TIMEOUT=timeout value * TIMEOUT=timeout value

4
Documentation/driver-api/firmware/firmware_cache.rst
View File

@@ -29,8 +29,8 @@ Some implementation details about the firmware cache setup:
* If an asynchronous call is used the firmware cache is only set up for a * If an asynchronous call is used the firmware cache is only set up for a
device if if the second argument (uevent) to request_firmware_nowait() is device if if the second argument (uevent) to request_firmware_nowait() is
true. When uevent is true it requests that a kobject uevent be sent to true. When uevent is true it requests that a kobject uevent be sent to
userspace for the firmware request. For details refer to the Fackback userspace for the firmware request through the sysfs fallback mechanism
mechanism documented below. if the firmware file is not found.
* If the firmware cache is determined to be needed as per the above two * If the firmware cache is determined to be needed as per the above two
criteria the firmware cache is setup by adding a devres entry for the criteria the firmware cache is setup by adding a devres entry for the