From: Linus Walleij <linus.walleij@linaro.org>
To: Sean Anderson <sean.anderson@seco.com>
Cc: "Vinod Koul" <vkoul@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
linux-phy@lists.infradead.org,
"Madalin Bucur" <madalin.bucur@nxp.com>,
linuxppc-dev@lists.ozlabs.org, devicetree@vger.kernel.org,
"Ioana Ciornei" <ioana.ciornei@nxp.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Camelia Alexandra Groza" <camelia.groza@nxp.com>,
linux-arm-kernel@lists.infradead.org,
"Bagas Sanjaya" <bagasdotme@gmail.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
"Fernández Rojas" <noltari@gmail.com>,
"Jonas Gorski" <jonas.gorski@gmail.com>,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v10 03/13] dt-bindings: Convert gpio-mmio to yaml
Date: Mon, 6 Mar 2023 23:04:10 +0100 [thread overview]
Message-ID: <CACRpkdZ-adsE1siz+MKvewNPoBLfwqhT_EjwDue3N9K9n0ET3A@mail.gmail.com> (raw)
In-Reply-To: <20230306191535.1917656-4-sean.anderson@seco.com>
Hi Sean,
thanks for doing this. I never got around to because time.
On Mon, Mar 6, 2023 at 8:16 PM Sean Anderson <sean.anderson@seco.com> wrote:
> This is a generic binding for simple MMIO GPIO controllers. Although we
> have a single driver for these controllers, they were previously spread
> over several files. Consolidate them. The register descriptions are
> adapted from the comments in the source. There is no set order for the
> registers, so I have not specified one.
>
> Signed-off-by: Sean Anderson <sean.anderson@seco.com>
(...)
> + compatible:
> + enum:
> + - brcm,bcm6345-gpio # Broadcom BCM6345 GPIO controller
> + - wd,mbl-gpio # Western Digital MyBook Live memory-mapped GPIO controller
> + - ni,169445-nand-gpio # National Instruments 169445 GPIO NAND controller
I think you can inline description: statements in the enum instead of
the # hash comments, however IIRC you have to use oneOf and
const: to do it, like I do in
Documentation/devicetree/bindings/input/touchscreen/cypress,cy8ctma340.yaml
but don't overinvest in this if it is cumbersome.
Either way:
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Yours,
Linus Walleij
next prev parent reply other threads:[~2023-03-06 22:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 19:15 [PATCH v10 00/13] phy: Add support for Lynx 10G SerDes Sean Anderson
2023-03-06 19:15 ` [PATCH v10 03/13] dt-bindings: Convert gpio-mmio to yaml Sean Anderson
2023-03-06 20:51 ` Jonas Gorski
2023-03-06 21:27 ` Sean Anderson
2023-03-10 10:33 ` Jonas Gorski
2023-03-06 22:04 ` Linus Walleij [this message]
2023-03-07 8:42 ` Krzysztof Kozlowski
2023-03-07 15:35 ` Sean Anderson
2023-03-08 8:48 ` Krzysztof Kozlowski
2023-03-09 9:16 ` Linus Walleij
2023-03-13 8:53 ` Leonard, Niall
2023-03-13 15:19 ` Sean Anderson
2023-03-13 22:13 ` Linus Walleij
2023-03-08 23:10 ` Rob Herring
2023-03-09 16:03 ` Sean Anderson
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=CACRpkdZ-adsE1siz+MKvewNPoBLfwqhT_EjwDue3N9K9n0ET3A@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=bagasdotme@gmail.com \
--cc=brgl@bgdev.pl \
--cc=camelia.groza@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=ioana.ciornei@nxp.com \
--cc=jonas.gorski@gmail.com \
--cc=kishon@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@nxp.com \
--cc=noltari@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.anderson@seco.com \
--cc=vkoul@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).