From: Mark Salyzyn <salyzyn@android.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, kernel-team@android.com,
Tim Murray <timmurray@google.com>,
Venkata Narendra Kumar Gutta <vnkgutta@codeaurora.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Luis Chamberlain <mcgrof@kernel.org>
Subject: Re: [PATCH] firmware_class: make firmware caching configurable
Date: Wed, 13 Nov 2019 14:33:44 -0800 [thread overview]
Message-ID: <4bca568b-4ffd-f880-7273-37db4d9f8f54@android.com> (raw)
In-Reply-To: <20191113215031.GA3944533@kroah.com>
On 11/13/19 1:50 PM, Greg Kroah-Hartman wrote:
> On Wed, Nov 13, 2019 at 01:01:13PM -0800, Mark Salyzyn wrote:
>> Because firmware caching generates uevent messages that are sent over
>> a netlink socket, it can prevent suspend on many platforms. It's
>> also not always useful, so make it a configurable option.
>>
>> Signed-off-by: Mark Salyzyn <salyzyn@android.com>
>> Cc: Tim Murray <timmurray@google.com>
>> Cc: Venkata Narendra Kumar Gutta <vnkgutta@codeaurora.org>
>> Acked-by: Luis Chamberlain <mcgrof@kernel.org>
>> ---
>> drivers/base/Kconfig | 13 +++++++++++++
>> drivers/base/firmware_loader/main.c | 6 +++---
>> 2 files changed, 16 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/base/Kconfig b/drivers/base/Kconfig
>> index 28b92e3cc570..36351c3a62b0 100644
>> --- a/drivers/base/Kconfig
>> +++ b/drivers/base/Kconfig
>> @@ -89,6 +89,19 @@ config PREVENT_FIRMWARE_BUILD
>>
>> source "drivers/base/firmware_loader/Kconfig"
>>
>> +config FW_CACHE
>> + bool "Enable firmware caching during suspend"
>> + depends on PM_SLEEP
>> + default y
>> + help
>> + Because firmware caching generates uevent messages that are sent
>> + over a netlink socket, it can prevent suspend on many platforms.
>> + It is also not always useful, so on such platforms we have the
>> + option.
>> +
>> + If unsure, say Y.
>> +
>> +
> Shouldn't this entry go into drivers/base/firmware_loader/Kconfig
> instead and depend on FW_LOADER by putting it in the correct location in
> that file?
Good point, respin on its way.
>
> Also, no need for two blank lines.
<not sure how the double lines showed up, checkpatch,pl should look for
this>
>
> And finally, 'default y' is only a good idea if your machine can not
> boot without the option. I don't think that's the case here, correct?
>
> thanks,
>
> greg k-h
I am concerned about the change in user space behavior and to prevent
defconfig churn.
next prev parent reply other threads:[~2019-11-13 22:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 21:01 Mark Salyzyn
2019-11-13 21:31 ` Luis Chamberlain
2019-11-13 21:50 ` Greg Kroah-Hartman
2019-11-13 22:13 ` Luis Chamberlain
2019-11-13 22:33 ` Mark Salyzyn [this message]
2019-11-13 22:54 ` [PATCH v2] " Mark Salyzyn
2019-11-13 23:16 ` Luis Chamberlain
2019-11-14 0:16 ` Mark Salyzyn
2019-11-14 0:26 ` Luis Chamberlain
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=4bca568b-4ffd-f880-7273-37db4d9f8f54@android.com \
--to=salyzyn@android.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=rafael@kernel.org \
--cc=timmurray@google.com \
--cc=vnkgutta@codeaurora.org \
/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
all inboxes | Powered by JetHome®