linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Stephen Boyd <stephen.boyd@linaro.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Takashi Iwai <tiwai@suse.de>, Kees Cook <keescook@chromium.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Ming Lei <ming.lei@canonical.com>,
	Vikram Mulukutla <markivx@codeaurora.org>,
	Mark Brown <broonie@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mimi Zohar <zohar@linux.vnet.ibm.com>,
	linux-arm-kernel@lists.infradead.org,
	Julia Lawall <julia.lawall@lip6.fr>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [RESEND/PATCHv4 v4 2/3] firmware: Provide infrastructure to make fw caching optional
Date: Mon, 13 Jun 2016 18:53:36 -0700	[thread overview]
Message-ID: <CAB=NE6WQP9V_0W55pre4my=vHS1=eX8_BK2AVJGNpXViw0EVFA@mail.gmail.com> (raw)
In-Reply-To: <20160607164741.31849-3-stephen.boyd@linaro.org>

On Tue, Jun 7, 2016 at 9:47 AM, Stephen Boyd <stephen.boyd@linaro.org> wrote:
> From: Vikram Mulukutla <markivx@codeaurora.org>
>
> Some low memory systems with complex peripherals cannot afford to
> have the relatively large firmware images taking up valuable
> memory during suspend and resume. Change the internal
> implementation of firmware_class to disallow caching based on a
> configurable option. In the near future, variants of
> request_firmware will take advantage of this feature.
>
> Signed-off-by: Vikram Mulukutla <markivx@codeaurora.org>
> [stephen.boyd@linaro.org: Drop firmware_desc design and use flags]
> Signed-off-by: Stephen Boyd <stephen.boyd@linaro.org>
> ---
>  drivers/base/firmware_class.c | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/base/firmware_class.c b/drivers/base/firmware_class.c
> index 01d55723d82c..45ed20cefa10 100644
> --- a/drivers/base/firmware_class.c
> +++ b/drivers/base/firmware_class.c
> @@ -112,6 +112,7 @@ static inline long firmware_loading_timeout(void)
>  #define FW_OPT_FALLBACK                0
>  #endif
>  #define FW_OPT_NO_WARN (1U << 3)
> +#define FW_OPT_NOCACHE (1U << 4)

6 days late -- but even if I wasn't Cc'd I caught this on linux-next
-- but please folks

NACK,

We should not be adding *yet another flag* and *yet another new API*
for a mild tweak to the API. The firmware API is already messed up
enough as it is, enough is enough. I'll post v4 of the new flexible
API which after feedback from v3 series [0] should put this to an end.
That should enable you to add your optional needs via a descriptor
without any other collateral evolutins. I had been waiting to push out
v4 until me and Julia completed some SmPL conversion to help drivers
easily convert over but seeing this patch got merged and I think this
can't wait any more, the SmPL grooviness will have to wait a bit and
some simple manual transformation examples will be provided.

[0] http://lkml.kernel.org/r/1450906497-24179-6-git-send-email-mcgrof@do-not-panic.com

  Luis

  reply	other threads:[~2016-06-14  1:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07 16:47 [RESEND/PATCHv4 v4 0/3] request_firmware() into pre-allocated buffers Stephen Boyd
2016-06-07 16:47 ` [RESEND/PATCHv4 v4 1/3] firmware: Consolidate kmap/read/write logic Stephen Boyd
2016-06-07 20:21   ` Andrew Morton
2016-06-07 16:47 ` [RESEND/PATCHv4 v4 2/3] firmware: Provide infrastructure to make fw caching optional Stephen Boyd
2016-06-14  1:53   ` Luis R. Rodriguez [this message]
2016-06-07 16:47 ` [RESEND/PATCHv4 v4 3/3] firmware: Support loading into a pre-allocated buffer Stephen Boyd
2016-06-12  9:28   ` kbuild test robot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAB=NE6WQP9V_0W55pre4my=vHS1=eX8_BK2AVJGNpXViw0EVFA@mail.gmail.com' \
    --to=mcgrof@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=julia.lawall@lip6.fr \
    --cc=keescook@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=markivx@codeaurora.org \
    --cc=ming.lei@canonical.com \
    --cc=sfr@canb.auug.org.au \
    --cc=stephen.boyd@linaro.org \
    --cc=tiwai@suse.de \
    --cc=zohar@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).