From: Rob Herring <robh@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-mmc@vger.kernel.org, linux-wireless@vger.kernel.org,
Wright Feng <wright.feng@infineon.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Chi-hsien Lin <chi-hsien.lin@infineon.com>,
Julian Calaby <julian.calaby@gmail.com>,
SHA-cyfmac-dev-list@infineon.com,
Arend van Spriel <aspriel@gmail.com>,
devicetree@vger.kernel.org,
Chung-hsien Hsu <chung-hsien.hsu@infineon.com>,
brcm80211-dev-list.pdl@broadcom.com,
Franky Lin <franky.lin@broadcom.com>
Subject: Re: [PATCH v2] dt-bindings: Convert the BCM4329 bindings to YAML and extend
Date: Wed, 24 Mar 2021 11:47:37 -0600 [thread overview]
Message-ID: <20210324174737.GA3319687@robh.at.kernel.org> (raw)
In-Reply-To: <20210315105911.138553-1-linus.walleij@linaro.org>
On Mon, 15 Mar 2021 11:59:11 +0100, Linus Walleij wrote:
> This converts the BCM4329 family bindings to YAML schema, and
> extends and fixes the bindings like this:
>
> - Name the bindings after the first chip (BCM4329) since
> wildcards like 43xx are nowadays frowned upon by the DT
> binding reviewers. We call this the "BCM4329 family"
> - Add compatible strings for all the variants that seem to
> exist in the wild. (Derived from firmware listings.)
> - Support specific-to-generic compatible strings (as already
> in use in DTS files).
> - Add required reg property (SDIO function number)
> - Add reset-gpios property (some systems wire this to a GPIO
> line).
> - I have only listed Arend as maintainer for now, volunteers
> can be added.
>
> Cc: Arend van Spriel <aspriel@gmail.com>
> Cc: Franky Lin <franky.lin@broadcom.com>
> Cc: Hante Meuleman <hante.meuleman@broadcom.com>
> Cc: Chi-hsien Lin <chi-hsien.lin@infineon.com>
> Cc: Wright Feng <wright.feng@infineon.com>
> Cc: Chung-hsien Hsu <chung-hsien.hsu@infineon.com>
> Cc: Julian Calaby <julian.calaby@gmail.com>
> Cc: brcm80211-dev-list.pdl@broadcom.com
> Cc: SHA-cyfmac-dev-list@infineon.com
> Cc: linux-mmc@vger.kernel.org
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v1->v2:
> - Specify specific-to-generic compatible strings such as
> "brcm,bcm4334-fmac", "brcm,bcm4329-fmac"
> - Also allow just "brcm,bcm4329-fmac" for legacy platforms.
> - Use this scheme in the example.
> ---
> .../net/wireless/brcm,bcm4329-fmac.yaml | 101 ++++++++++++++++++
> .../net/wireless/brcm,bcm43xx-fmac.txt | 38 -------
> 2 files changed, 101 insertions(+), 38 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml
> delete mode 100644 Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt
>
Applied, thanks!
prev parent reply other threads:[~2021-03-24 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 10:59 [PATCH v2] dt-bindings: Convert the BCM4329 bindings to YAML and extend Linus Walleij
2021-03-19 13:44 ` Ulf Hansson
2021-03-24 17:47 ` Rob Herring [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=20210324174737.GA3319687@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=chi-hsien.lin@infineon.com \
--cc=chung-hsien.hsu@infineon.com \
--cc=devicetree@vger.kernel.org \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=julian.calaby@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wright.feng@infineon.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;
as well as URLs for NNTP newsgroup(s).