From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Kalle Valo <kvalo@kernel.org>, Hermes Zhang <chenhui.zhang@axis.com>
Cc: Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
kernel@axis.com, Hermes Zhang <chenhuiz@axis.com>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
SHA-cyfmac-dev-list@infineon.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] brcmfmac: of: introduce new property to allow disable PNO
Date: Sun, 24 Apr 2022 21:13:40 +0200 [thread overview]
Message-ID: <c44646ab-95e0-5d9b-69de-e66b2550c4fa@broadcom.com> (raw)
In-Reply-To: <8735i5odyo.fsf@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 625 bytes --]
On 4/22/2022 7:59 AM, Kalle Valo wrote:
> Hermes Zhang <chenhui.zhang@axis.com> writes:
>
>> From: Hermes Zhang <chenhuiz@axis.com>
>>
>> The PNO feature need to be disable for some scenario in different
>> product. This commit introduce a new property to allow the
>> product-specific toggling of this feature.
>
> "some scenario"? That's not really helpful.
The firmware feature PNO is used to provide the scheduled scan
functionality. User-space can choose whether or not to use scheduled
scan. If the scheduled scan is not working I would rather see a bug
report so it can be properly investigated.
Regards,
Arend
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4219 bytes --]
prev parent reply other threads:[~2022-04-24 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 4:44 [PATCH v2] brcmfmac: of: introduce new property to allow disable PNO Hermes Zhang
2022-04-22 5:59 ` Kalle Valo
2022-04-24 19:13 ` Arend van Spriel [this message]
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=c44646ab-95e0-5d9b-69de-e66b2550c4fa@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=chenhui.zhang@axis.com \
--cc=chenhuiz@axis.com \
--cc=davem@davemloft.net \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=kernel@axis.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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