Received: by 10.192.165.148 with SMTP id m20csp1397274imm; Sat, 21 Apr 2018 07:32:58 -0700 (PDT) X-Google-Smtp-Source: AIpwx48J0xazSigR42Q+73xgmMsqhWptymyjOdED+fsnPgrdKCSsOEoul48TU3Zf4H8yAt7LzoPA X-Received: by 10.99.95.14 with SMTP id t14mr11019841pgb.94.1524321178574; Sat, 21 Apr 2018 07:32:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524321178; cv=none; d=google.com; s=arc-20160816; b=HtHTeHfSiq4QvhCJVxEX7z+88pXGFuqvtHKCH/5KXlAugeD7dhzcfDIVx8CLXniLSe cD6SHmqtUp/TuWhV27pRMo10lnj36psZvZdf99+P4EP5pIPO8GLslBtm7qD4G+8wJmQT aLxS5Nk+WmgVJJBnssYRjYexT4w1+MHoC8sc1U2ZfkoOp5nbxc2MWpFu9mOPDfZLdu4G S0HbrPBYEkYLnRKzLs6734R8ZWaFUOqPOzads7kA5LOueErORcg57HdMjFfGQ2VmuM7H cTWYhRWSIYP9b3OqGPPHOu2nUtWD2HlYTVHnWYhmzhYGn67pNgt48K4DjAIIzyTb3Gdt F1hQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=1AqN43Ya/z/vDHEsSiW4FTGn80k5JpOHRZDmNSVuk/k=; b=uXpibUbtD+4PzZsGAHinThXhV+gjBPXb5uhM28J7c/5JeQCjP9nCyi4qVaAztph94d F6rKq9MurEeNdLGXPeflhmkGryHyJQhR/qIxVLkczRF0LgdgT4j2QQxB4x2UrwPsHQIW yFE/GGmXanqyB9LcmGA6PKjnotrsPpo/E/10EZrOcJvWRW8TtGTWUMrMxwP0cuJqLETr AHLRtyTm7Enykn1cm6gzrQ2TtvspBmJloGX315IAImjSLLXpyRfNN81//Mcu/JcSTB6z wG9B9jRKnY7pCvA8nLwIlRG4tbsulG+TBvy/5Aqz+j/k+9ZkVWDd2LMPXj4szIW1CFoA 0MiA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a87si2465556pfl.165.2018.04.21.07.31.49; Sat, 21 Apr 2018 07:32:58 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752785AbeDUO06 (ORCPT + 99 others); Sat, 21 Apr 2018 10:26:58 -0400 Received: from mx2.suse.de ([195.135.220.15]:50239 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752700AbeDUO05 (ORCPT ); Sat, 21 Apr 2018 10:26:57 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 66455ACAD; Sat, 21 Apr 2018 14:26:56 +0000 (UTC) Date: Sat, 21 Apr 2018 16:26:56 +0200 From: "Luis R. Rodriguez" To: Andres Rodriguez , Hans de Goede Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org, mcgrof@kernel.org, alexdeucher@gmail.com, ckoenig.leichtzumerken@gmail.com, kvalo@codeaurora.org, arend.vanspriel@broadcom.com Subject: Re: [PATCH 3/9] firmware: add kernel-doc for enum fw_opt Message-ID: <20180421142656.GP14440@wotan.suse.de> References: <20180417153307.3693-1-andresx7@gmail.com> <20180417153307.3693-4-andresx7@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180417153307.3693-4-andresx7@gmail.com> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 17, 2018 at 11:33:01AM -0400, Andres Rodriguez wrote: > Some basic definitions for the FW_OPT_* values > > Signed-off-by: Andres Rodriguez > --- > drivers/base/firmware_loader/firmware.h | 11 +++++++++++ > 1 file changed, 11 insertions(+) > > diff --git a/drivers/base/firmware_loader/firmware.h b/drivers/base/firmware_loader/firmware.h > index 957396293b92..8ef23c334135 100644 > --- a/drivers/base/firmware_loader/firmware.h > +++ b/drivers/base/firmware_loader/firmware.h > @@ -10,6 +10,17 @@ > > #include > > +/** > + * enum fw_opt - options to control firmware loading behaviour > + * > + * @FW_OPT_UEVENT: Enable the uevent fallback path. No, that is not what this does. This sends a kobject uevent to userspace when the fallback mechanism is used. So please use: "Enables the fallback mechanism to send a kobject uevent when the firmware is not found. Userspace is in charge to load the firmware using the sysfs loading facility." > + * @FW_OPT_NOWAIT: Executing inside an asynchronous firmware request. Please use "Used to describe the firmware request is asynchronous.". > + * @FW_OPT_USERHELPER: Enable the usermode fallback path. The notion of "userhelper" only causes confusion since the kernel has its own usermode helper (kernel/umh.c), and the only use case that the firmware loader has for it is for when CONFIG_UEVENT_HELPER_PATH is set to call out to userspace helper for kobject uevents. In practice *no one* is setting or using this these days. So I have been going on a small nomenclature crusade to clean this mess up bon on kernel/umh.c and the firmware loader. This is why the entire fallback mechanism is now stuffed into a file called fallback.c. I don't want to confuse people further so please do not refer to "usermode" anymore for the fallback mechanism, it is completely misleading. We should eventually just rename this flag to fallback or something. Therefore please be consistent with the documentation and use: "Enable the fallback mechanism, in case the direct filesystem lookup fails at finding the firmware. For details refer to fw_sysfs_fallback()." Since fw_sysfs_fallback() is used in documentation and we don't want to clash with other documentation names, then rename fw_sysfs_fallback() to use the firmware_ prefix. That would be a separate patch. So Hans -- same goes for your call which can be added after Andres' patch series. > + * @FW_OPT_NO_WARN: Quiet, avoid printing warning messages. > + * @FW_OPT_NOCACHE: Firmware caching will be disabled for this request. Although we have good documentation about this on Documentation/driver-api/firmware/firmware_cache.rst best to describe this a bit more here. Please use (modulo adjust lengths accordingly): * @FW_OPT_NOCACHE: Disables firmware caching. Firmware caching is used to cache the firmware upon suspend, so that upon resume races against the firmware file lookup on storage is avoided. Used for calls where the file may be too big, or where the driver takes charge of its own firmware caching mechanism. Note that an example driver which does its own firmware caching mechanism is iwlwifi, IIRC. > + * @FW_OPT_NOFALLBACK: Disable the fallback path. Takes precedence over > + * &FW_OPT_UEVENT and &FW_OPT_USERHELPER. Please replace "fallback path" with "fallback mechanism" to be consistent with the documentation. Luis > + */ > enum fw_opt { > FW_OPT_UEVENT = (1U << 0), > FW_OPT_NOWAIT = (1U << 1), > -- > 2.14.1 > > -- Do not panic