<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in request_firmware.rst</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>726b5bd3 - Documentation/driver-api: firmware/request_firmware: drop doubled word</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/driver-api/firmware/request_firmware.rst#726b5bd3</link>
        <description>Documentation/driver-api: firmware/request_firmware: drop doubled wordDrop the doubled word &quot;call&quot;.Signed-off-by: Randy Dunlap &lt;rdunlap@infradead.org&gt;Cc: Jonathan Corbet &lt;corbet@lwn.net&gt;Cc: linux-doc@vger.kernel.orgAcked-by: Luis Chamberlain &lt;mcgrof@kernel.org&gt;Link: https://lore.kernel.org/r/20200704034502.17199-6-rdunlap@infradead.orgSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/driver-api/firmware/request_firmware.rst</description>
        <pubDate>Sat, 04 Jul 2020 03:44:50 +0000</pubDate>
        <dc:creator>Randy Dunlap &lt;rdunlap@infradead.org&gt;</dc:creator>
    </item>
<item>
        <title>e4c2c0ff - firmware: Add new platform fallback mechanism and firmware_request_platform()</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/driver-api/firmware/request_firmware.rst#e4c2c0ff</link>
        <description>firmware: Add new platform fallback mechanism and firmware_request_platform()In some cases the platform&apos;s main firmware (e.g. the UEFI fw) may containan embedded copy of device firmware which needs to be (re)loaded into theperipheral. Normally such firmware would be part of linux-firmware, but insome cases this is not feasible, for 2 reasons:1) The firmware is customized for a specific use-case of the chipset / usewith a specific hardware model, so we cannot have a single firmware filefor the chipset. E.g. touchscreen controller firmwares are compiledspecifically for the hardware model they are used with, as they arecalibrated for a specific model digitizer.2) Despite repeated attempts we have failed to get permission toredistribute the firmware. This is especially a problem with customizedfirmwares, these get created by the chip vendor for a specific ODM and thecopyright may partially belong with the ODM, so the chip vendor cannotgive a blanket permission to distribute these.This commit adds a new platform fallback mechanism to the firmware loaderwhich will try to lookup a device fw copy embedded in the platform&apos;s mainfirmware if direct filesystem lookup fails.Drivers which need such embedded fw copies can enable this fallbackmechanism by using the new firmware_request_platform() function.Note that for now this is only supported on EFI platforms and even onthese platforms firmware_fallback_platform() only works ifCONFIG_EFI_EMBEDDED_FIRMWARE is enabled (this gets selected by driverswhich need this), in all other cases firmware_fallback_platform() simplyalways returns -ENOENT.Reported-by: Dave Olsthoorn &lt;dave@bewaar.me&gt;Suggested-by: Peter Jones &lt;pjones@redhat.com&gt;Acked-by: Luis Chamberlain &lt;mcgrof@kernel.org&gt;Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;Link: https://lore.kernel.org/r/20200115163554.101315-5-hdegoede@redhat.comSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/driver-api/firmware/request_firmware.rst</description>
        <pubDate>Wed, 15 Jan 2020 16:35:48 +0000</pubDate>
        <dc:creator>Hans de Goede &lt;hdegoede@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>7dcc0134 - firmware: add firmware_request_nowarn() - load firmware without warnings</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/driver-api/firmware/request_firmware.rst#7dcc0134</link>
        <description>firmware: add firmware_request_nowarn() - load firmware without warningsCurrently the firmware loader only exposes one silent path for queryingoptional firmware, and that is firmware_request_direct(). This functionalso disables the sysfs fallback mechanism, which might not always be thedesired behaviour [0].This patch introduces a variations of request_firmware() that enable thecaller to disable the undesired warning messages but enables the sysfsfallback mechanism. This is equivalent to adding FW_OPT_NO_WARN to theold behaviour.[0]: https://git.kernel.org/linus/c0cc00f250e1Signed-off-by: Andres Rodriguez &lt;andresx7@gmail.com&gt;Reviewed-by: Kees Cook &lt;keescook@chromium.org&gt;Acked-by: Luis R. Rodriguez &lt;mcgrof@kernel.org&gt;[mcgrof: used the old API calls as the full rename is not done yet, and add the caller for when FW_LOADER is disabled, enhance documentation ]Signed-off-by: Luis R. Rodriguez &lt;mcgrof@kernel.org&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/driver-api/firmware/request_firmware.rst</description>
        <pubDate>Thu, 10 May 2018 20:08:45 +0000</pubDate>
        <dc:creator>Andres Rodriguez &lt;andresx7@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>b93815d0 - firmware: some documentation fixes</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/driver-api/firmware/request_firmware.rst#b93815d0</link>
        <description>firmware: some documentation fixesIncluding: - Fixup outdated kernel-doc paths - Slightly too short title underline - Some typosSigned-off-by: Andres Rodriguez &lt;andresx7@gmail.com&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/driver-api/firmware/request_firmware.rst</description>
        <pubDate>Wed, 25 Apr 2018 16:25:39 +0000</pubDate>
        <dc:creator>Andres Rodriguez &lt;andresx7@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>df9267f1 - firmware: Fix firmware documentation for recent file renames</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/driver-api/firmware/request_firmware.rst#df9267f1</link>
        <description>firmware: Fix firmware documentation for recent file renamesfirmware_class.c was split into several files underdrivers/base/firmware_loader. The new main.c has the functions which/request_firmware.rst references.Acked-by: Luis R. Rodriguez &lt;mcgrof@kernel.org&gt;Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;Tested-by: Randy Dunlap &lt;rdunlap@infradead.org&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/driver-api/firmware/request_firmware.rst</description>
        <pubDate>Sun, 08 Apr 2018 16:06:21 +0000</pubDate>
        <dc:creator>Hans de Goede &lt;hdegoede@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>5d42c96e - firmware: add firmware_request_cache() to help with cache on reboot</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/driver-api/firmware/request_firmware.rst#5d42c96e</link>
        <description>firmware: add firmware_request_cache() to help with cache on rebootSome devices have an optimization in place to enable the firmware tobe retaineed during a system reboot, so after reboot the device can skiprequesting and loading the firmware. This can save up to 1s in loadtime. The mt7601u 802.11 device happens to be such a device.When these devices retain the firmware on a reboot and then suspendthey can miss looking for the firmware on resume. To help with this weneed a way to cache the firmware when such an optimization has takenplace.Signed-off-by: Luis R. Rodriguez &lt;mcgrof@kernel.org&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/driver-api/firmware/request_firmware.rst</description>
        <pubDate>Wed, 21 Mar 2018 22:34:29 +0000</pubDate>
        <dc:creator>Luis R. Rodriguez &lt;mcgrof@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>f007cad1 - Revert &quot;firmware: add sanity check on shutdown/suspend&quot;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/driver-api/firmware/request_firmware.rst#f007cad1</link>
        <description>Revert &quot;firmware: add sanity check on shutdown/suspend&quot;This reverts commit 81f95076281fdd3bc382e004ba1bce8e82fccbce.It causes random failures of firmware loading at resume time (well,random for me, it seems to be more reliable for others) because thefirmware disabling is not actually synchronous with any particularresume event, and at least the btusb driver that uses a workqueue toload the firmware at resume seems to occasionally hit the &quot;firmwareloading is disabled&quot; logic because the firmware loader hasn&apos;t gotten theresume event yet.Some kind of sanity check for not trying to load firmware when it&apos;s notpossible might be a good thing, but this commit was not it.Greg seems to have silently suffered the same issue, and pointed to thelikely culprit, and Gabriel C verified the revert fixed it for him too.Reported-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;Pointed-at-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Tested-by: Gabriel C &lt;nix.or.die@gmail.com&gt;Cc: Luis R. Rodriguez &lt;mcgrof@kernel.org&gt;Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;

            List of files:
            /linux-6.15/Documentation/driver-api/firmware/request_firmware.rst</description>
        <pubDate>Mon, 11 Sep 2017 04:19:06 +0000</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>81f95076 - firmware: add sanity check on shutdown/suspend</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/driver-api/firmware/request_firmware.rst#81f95076</link>
        <description>firmware: add sanity check on shutdown/suspendThe firmware API should not be used after we go to suspendand after we reboot/halt. The suspend/resume case is a bitcomplex, so this documents that so things are clearer.We want to know about users of the API in incorrect places sothat their callers are corrected, so this also adds a warnfor those cases.Signed-off-by: Luis R. Rodriguez &lt;mcgrof@kernel.org&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/driver-api/firmware/request_firmware.rst</description>
        <pubDate>Tue, 02 May 2017 08:31:05 +0000</pubDate>
        <dc:creator>Luis R. Rodriguez &lt;mcgrof@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>113ccc38 - firmware: revamp firmware documentation</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/driver-api/firmware/request_firmware.rst#113ccc38</link>
        <description>firmware: revamp firmware documentationUnderstanding this code is getting out of control without anynotes. Give the firmware_class driver a much needed documentation love,and while at it convert it to the new sphinx documentation format.v2: typos and small fixesSigned-off-by: Luis R. Rodriguez &lt;mcgrof@kernel.org&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/driver-api/firmware/request_firmware.rst</description>
        <pubDate>Fri, 16 Dec 2016 11:10:36 +0000</pubDate>
        <dc:creator>Luis R. Rodriguez &lt;mcgrof@kernel.org&gt;</dc:creator>
    </item>
</channel>
</rss>
