From: Conor Dooley <conor@kernel.org>
To: Stafford Horne <shorne@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux OpenRISC <linux-openrisc@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/5] dt-bindings: Add compatible string opencores,gpio to gpio-mmio
Date: Tue, 16 Dec 2025 00:05:06 +0000 [thread overview]
Message-ID: <20251216-area-commuting-d20343c98fce@spud> (raw)
In-Reply-To: <aUBi0Fid8vF-G8Wl@antec>
[-- Attachment #1: Type: text/plain, Size: 2028 bytes --]
On Mon, Dec 15, 2025 at 07:34:40PM +0000, Stafford Horne wrote:
> On Mon, Dec 15, 2025 at 06:40:49PM +0000, Stafford Horne wrote:
> > On Mon, Dec 15, 2025 at 04:57:45PM +0000, Conor Dooley wrote:
> > > On Sun, Dec 14, 2025 at 06:01:41PM +0000, Stafford Horne wrote:
> > > > In FPGA Development boards with GPIOs we use the opencores gpio verilog
> > > > rtl. This is compatible with the gpio-mmio. Add the compatible string
> > > > to allow as below.
> > > >
> > > > Example:
> > > >
> > > > gpio0: gpio@91000000 {
> > > > compatible = "opencores,gpio", "brcm,bcm6345-gpio";
> > >
> > > What you have done below does not permit this, it only permits
> > > opencores,gpio in isolation.
> > > pw-bot: changes-requested
> >
> > Understood, I was not familar with the new schema. I was trying to follow what
> > was seen in some other patches, now I see where I went wrong. I will fix this
> > and use the schema validation tools to verify.
> >
> > Thanks for pointing it out.
>
> I think the below is correct. But, would this be ok to put in one patch?
>
> I do:
> - Convert compatible from simple enum to oneOf.
> - Add items: for the openrisc,gpio compatiblity string.
>
> properties:
> compatible:
> - enum:
> - - brcm,bcm6345-gpio
> - - ni,169445-nand-gpio
> - - wd,mbl-gpio # Western Digital MyBook Live memory-mapped GPIO controller
> - - intel,ixp4xx-expansion-bus-mmio-gpio
> + oneOf:
> + - const: brcm,bcm6345-gpio
> + - const: ni,169445-nand-gpio
> + - const: wd,mbl-gpio # Western Digital MyBook Live memory-mapped GPIO controller
> + - const: intel,ixp4xx-expansion-bus-mmio-gpio
This is fine, but keep the enum instead of making these into a bunch of
const entries. IOW, just put a - in front of the existing enum: and
reindent it to be correct under the oneOf.
> + - items:
> + - enum:
> + - opencores,gpio
> + - const: brcm,bcm6345-gpio
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-12-16 0:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251214180158.3955285-1-shorne@gmail.com>
2025-12-14 18:01 ` [PATCH 1/5] dt-bindings: Add compatible string opencores,gpio to gpio-mmio Stafford Horne
2025-12-15 16:57 ` Conor Dooley
2025-12-15 18:40 ` Stafford Horne
2025-12-15 19:34 ` Stafford Horne
2025-12-16 0:05 ` Conor Dooley [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=20251216-area-commuting-d20343c98fce@spud \
--to=conor@kernel.org \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-openrisc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=shorne@gmail.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).