From: Rob Herring <robh@kernel.org>
To: "Alvin Šipraga" <alvin@pqrs.dk>
Cc: brcm80211-dev-list.pdl@broadcom.com,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Hante Meuleman" <hante.meuleman@broadcom.com>,
"Eric Dumazet" <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
SHA-cyfmac-dev-list@infineon.com, linux-kernel@vger.kernel.org,
"Jakub Kicinski" <kuba@kernel.org>,
linux-wireless@vger.kernel.org, "van Spriel" <arend@broadcom.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Kalle Valo" <kvalo@kernel.org>,
"Alvin Šipraga" <alsi@bang-olufsen.dk>,
"Franky Lin" <franky.lin@broadcom.com>,
netdev@vger.kernel.org, "Rob Herring" <robh+dt@kernel.org>,
"Ahmad Fatoum" <a.fatoum@pengutronix.de>,
"Arend van Spriel" <aspriel@gmail.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: bcm4329-fmac: add optional brcm,ccode-map-trivial
Date: Mon, 18 Jul 2022 12:43:55 -0600 [thread overview]
Message-ID: <20220718184355.GA3325548-robh@kernel.org> (raw)
In-Reply-To: <20220711123005.3055300-2-alvin@pqrs.dk>
On Mon, 11 Jul 2022 14:30:03 +0200, Alvin Šipraga wrote:
> From: Alvin Šipraga <alsi@bang-olufsen.dk>
>
> The bindings already offer a brcm,ccode-map property to describe the
> mapping between the kernel's ISO3166 alpha 2 country code string and the
> firmware's country code string and revision number. This is a
> board-specific property and determined by the CLM blob firmware provided
> by the hardware vendor.
>
> However, in some cases the firmware will also use ISO3166 country codes
> internally, and the revision will always be zero. This implies a trivial
> mapping: cc -> { cc, 0 }.
>
> For such cases, add an optional property brcm,ccode-map-trivial which
> obviates the need to describe every trivial country code mapping in the
> device tree with the existing brcm,ccode-map property. The new property
> is subordinate to the more explicit brcm,ccode-map property.
>
> Signed-off-by: Alvin Šipraga <alsi@bang-olufsen.dk>
> ---
> .../bindings/net/wireless/brcm,bcm4329-fmac.yaml | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-07-18 18:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 12:30 [PATCH 0/2] wifi: brcmfmac: add DT property for trivial ccode mapping Alvin Šipraga
2022-07-11 12:30 ` [PATCH 1/2] dt-bindings: bcm4329-fmac: add optional brcm,ccode-map-trivial Alvin Šipraga
2022-07-14 15:21 ` Ahmad Fatoum
2022-07-18 18:43 ` Rob Herring [this message]
2022-07-28 9:58 ` Kalle Valo
2022-07-11 12:30 ` [PATCH 2/2] wifi: brcmfmac: support brcm,ccode-map-trivial DT property Alvin Šipraga
2022-07-14 15:22 ` Ahmad Fatoum
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=20220718184355.GA3325548-robh@kernel.org \
--to=robh@kernel.org \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=a.fatoum@pengutronix.de \
--cc=alsi@bang-olufsen.dk \
--cc=alvin@pqrs.dk \
--cc=arend@broadcom.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=krzysztof.kozlowski+dt@linaro.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+dt@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;
as well as URLs for NNTP newsgroup(s).