[PATCH v4 0/2] firmware: fw doc revamp follow up

Luis R. Rodriguez
2017-01-12T14:43:02Z

This v4 addresses the last 2 remaining patches from the last doc revamp series,
which relate only to the firmware custom fallback mechanism. One of the
patches just needed minor adjustments to account for a conjunction on SmPL
grammar. We also keep the leds-lp55xx-common white-list annotation of
DECLARE_FW_CUSTOM_FALLBACK() given despite the fact that it is acknowledged
that we could do better, old userspace already exists and relies on using
request firmware instead of using sysfs to enable custom control of LEDs.

As clarified in the last series, most users of the custom fallback mechanism
have been typo issues on part of the driver developer. The custom fallback
mechanism is needed today to help with custom fetching of firmware outside of
the typical standard firmware path, and for out of tree drivers for remote-proc
firmware for really large firmware files for which initramfs is not suitable. A
proper upstream solution for this need has been discussed and we can address
this using the *standard fallback mechanism* using *kobject uevents*, what we
need is a proper design paired with corresponding userspace component. That is
underway. Given this, there is no longer any need *upstream* for these uses. To
avoid further issues and to help understand the reason and logic behind old
custom uses this adds a white-list upstream to help report if further faulty
uses are added upstream.

Luis R. Rodriguez (2):
firmware: add SmPL report for custom fallback mechanism
firmware: add DECLARE_FW_CUSTOM_FALLBACK() annotation

.../driver-api/firmware/fallback-mechanisms.rst | 20 +++++++++++
drivers/firmware/dell_rbu.c | 1 +
drivers/leds/leds-lp55xx-common.c | 1 +
include/linux/firmware.h | 7 ++++
.../api/request_firmware-custom-fallback.cocci | 42 ++++++++++++++++++++++
5 files changed, 71 insertions(+)
create mode 100644 scripts/coccinelle/api/request_firmware-custom-fallback.cocci

--
2.11.0