From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Jacobe Zang <jacobe.zang@wesion.com>,
Kalle Valo <kvalo@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
van Spriel <arend@broadcom.com>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
brcm80211@lists.linux.dev, brcm80211-dev-list.pdl@broadcom.com
Subject: Re: [PATCH v12 3/5] dt-bindings: net: wireless: brcm4329-fmac: change properties enum structure
Date: Wed, 28 Aug 2024 10:50:43 +0200 [thread overview]
Message-ID: <22fdbe11-830a-4084-aa5e-1b7294f3a7fd@broadcom.com> (raw)
In-Reply-To: <20240828-wireless-mainline-v12-3-9064ac7acf1d@wesion.com>
On 8/28/2024 9:40 AM, Jacobe Zang wrote:
> Add "brcm,bcm4329-fmac" as fallback compatible for wireless devices that
> used PCI ID based compatible. So that can pass the compatible check in
> driver.
Hi Jacobe,
Using the driver implementation as an argument for adding the fallback
compatible to the bindings does sound wrong. The most importants rule
about the bindings is that it is independent of kernel and/or driver
implementation.
Now this actually overlaps my patch series from couple of weeks ago
which also covered some other existing DTS files for Apple platforms. So
my proposal here is to drop this patch for now. I will give it another
shot in v2 of my series after yours is (finally) applied. We can always
hope ;-) That does also mean the compatible check in the driver should
not be moved in brcmf_of_probe(). Also the Khadas Edge2 DTS file should
not use the fallback compatible yet. I can include it in my series later.
Regards,
Arend
> Signed-off-by: Jacobe Zang <jacobe.zang@wesion.com>
> ---
> .../bindings/net/wireless/brcm,bcm4329-fmac.yaml | 20 +++++++++++---------
> 1 file changed, 11 insertions(+), 9 deletions(-)
next prev parent reply other threads:[~2024-08-28 8:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 7:40 [PATCH v12 0/5] Add AP6276P wireless support Jacobe Zang
2024-08-28 7:40 ` [PATCH v12 1/5] dt-bindings: net: wireless: brcm4329-fmac: add pci14e4,449d Jacobe Zang
2024-08-28 7:40 ` [PATCH v12 2/5] dt-bindings: net: wireless: brcm4329-fmac: add clock description for AP6275P Jacobe Zang
2024-08-28 7:40 ` [PATCH v12 3/5] dt-bindings: net: wireless: brcm4329-fmac: change properties enum structure Jacobe Zang
2024-08-28 8:50 ` Arend van Spriel [this message]
2024-08-28 9:02 ` Jacobe Zang
2024-08-28 7:40 ` [PATCH v12 4/5] wifi: brcmfmac: Add optional lpo clock enable support Jacobe Zang
2024-08-28 7:40 ` [PATCH v12 5/5] wifi: brcmfmac: add flag for random seed during firmware download Jacobe Zang
2024-08-28 7:59 ` [PATCH v12 0/5] Add AP6276P wireless support Krzysztof Kozlowski
2024-08-28 8:10 ` Jacobe Zang
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=22fdbe11-830a-4084-aa5e-1b7294f3a7fd@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jacobe.zang@wesion.com \
--cc=krzk+dt@kernel.org \
--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 \
--cc=robh@kernel.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