write in 30M

hc

2024-02-20 ea08eeccae9297f7aabd2ef7f0c2517ac4549acc

 kernel/Documentation/driver-api/firmware/request_firmware.rst
..
..
@@ -25,6 +25,11 @@
25
25
 .. kernel-doc:: drivers/base/firmware_loader/main.c
26
26
    :functions: firmware_request_nowarn
27
27
 
28
+firmware_request_platform
29
+-------------------------
30
+.. kernel-doc:: drivers/base/firmware_loader/main.c
31
+   :functions: firmware_request_platform
32
+
28
33
 request_firmware_direct
29
34
 -----------------------
30
35
 .. kernel-doc:: drivers/base/firmware_loader/main.c
..
..
@@ -71,5 +76,5 @@
71
76
 the driver has the firmware image accessible in fw_entry->{data,size}.
72
77
 If something went wrong request_firmware() returns non-zero and fw_entry
73
78
 is set to NULL. Once your driver is done with processing the firmware it
74
-can call call release_firmware(fw_entry) to release the firmware image
79
+can call release_firmware(fw_entry) to release the firmware image
75
80
 and any related resource.