From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750805AbdALOnC (ORCPT ); Thu, 12 Jan 2017 09:43:02 -0500 Received: from mail.kernel.org ([198.145.29.136]:34590 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750720AbdALOnB (ORCPT ); Thu, 12 Jan 2017 09:43:01 -0500 From: "Luis R. Rodriguez" To: gregkh@linuxfoundation.org, ming.lei@canonical.com Cc: bp@alien8.de, wagi@monom.org, teg@jklm.no, mchehab@osg.samsung.com, zajec5@gmail.com, linux-kernel@vger.kernel.org, markivx@codeaurora.org, stephen.boyd@linaro.org, broonie@kernel.org, zohar@linux.vnet.ibm.com, tiwai@suse.de, johannes@sipsolutions.net, chunkeey@googlemail.com, hauke@hauke-m.de, jwboyer@fedoraproject.org, dmitry.torokhov@gmail.com, dwmw2@infradead.org, jslaby@suse.com, torvalds@linux-foundation.org, luto@amacapital.net, fengguang.wu@intel.com, rpurdie@rpsys.net, j.anaszewski@samsung.com, Abhay_Salunke@dell.com, Julia.Lawall@lip6.fr, Gilles.Muller@lip6.fr, nicolas.palix@imag.fr, dhowells@redhat.com, bjorn.andersson@linaro.org, arend.vanspriel@broadcom.com, kvalo@codeaurora.org, "Luis R. Rodriguez" Subject: [PATCH v4 0/2] firmware: fw doc revamp follow up Date: Thu, 12 Jan 2017 06:42:48 -0800 Message-Id: <20170112144250.12376-1-mcgrof@kernel.org> X-Mailer: git-send-email 2.11.0 In-Reply-To: <20161213030828.17820-4-mcgrof@kernel.org> References: <20161213030828.17820-4-mcgrof@kernel.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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