[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YmXJiCamPQSRqiCq@lunn.ch>
Date: Mon, 25 Apr 2022 00:04:56 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Hermes Zhang <chenhui.zhang@...s.com>
Cc: Arend van Spriel <aspriel@...il.com>,
Franky Lin <franky.lin@...adcom.com>,
Hante Meuleman <hante.meuleman@...adcom.com>,
Kalle Valo <kvalo@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, kernel@...s.com,
Hermes Zhang <chenhuiz@...s.com>,
linux-wireless@...r.kernel.org,
brcm80211-dev-list.pdl@...adcom.com,
SHA-cyfmac-dev-list@...ineon.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] brcmfmac: of: introduce new property to allow disable
PNO
On Sun, Apr 24, 2022 at 10:22:24AM +0800, Hermes Zhang wrote:
> From: Hermes Zhang <chenhuiz@...s.com>
>
> Some versions of the Broadcom firmware for this chip seem to hang
> if the PNO feature is enabled when connecting to a dummy or
> non-existent AP.
> Add a new property to allow the disabling of PNO for devices with
> this specific firmware.
If you know the specific version of the firmware which is broken, why
do you need a DT property? Why not just check the firmware version and
disable it automatically?
It does not seem like you are describing hardware here, which is what
DT is for.
Andrew
Powered by blists - more mailing lists