All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux OpenRISC <linux-openrisc@vger.kernel.org>,
	Linus Walleij <linusw@kernel.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 v3 2/6] dt-bindings: gpio-mmio: Add opencores GPIO
Date: Sun, 11 Jan 2026 16:46:52 +0000	[thread overview]
Message-ID: <aWPT_HsRVC0dQ_j6@antec> (raw)
In-Reply-To: <20260111-bold-wolf-of-champagne-58fac7@quoll>

On Sun, Jan 11, 2026 at 11:18:42AM +0100, Krzysztof Kozlowski wrote:
> On Fri, Jan 09, 2026 at 01:43:53PM +0000, Stafford Horne wrote:
> > Add a device tree binding for the opencores GPIO controller.
> > 
> > On FPGA Development boards with GPIOs the OpenRISC architecture uses the
> > opencores gpio verilog rtl which is compatible with the MMIO GPIO driver.
> > 
> > Link: https://opencores.org/projects/gpio
> > Signed-off-by: Stafford Horne <shorne@gmail.com>
> > ---
> > Since v2:
> >  - Fixup patch to simply add opencores,gpio and add an example.
> 
> Simplify? You completely changed the meaning of binding here - now
> device is not compatible.
>
> I don't know which one is correct, but your changelog must explain why
> now devices are not compatible but they were before.

Hello,

Did you miss the 1/6 patch in this series?  We add the compatible string to the
driver there before we add it here.

Sorry, I thought the series and the over letter would be enough to understand
what I meant by the "Fixup" description here.

> > Since v1:
> >  - Fix schema to actually match the example.
> > 
> >  Documentation/devicetree/bindings/gpio/gpio-mmio.yaml | 9 +++++++++
> >  1 file changed, 9 insertions(+)
> > 
> > diff --git a/Documentation/devicetree/bindings/gpio/gpio-mmio.yaml b/Documentation/devicetree/bindings/gpio/gpio-mmio.yaml
> > index ee5d5d25ae82..d44edc181e0a 100644
> > --- a/Documentation/devicetree/bindings/gpio/gpio-mmio.yaml
> > +++ b/Documentation/devicetree/bindings/gpio/gpio-mmio.yaml
> > @@ -23,6 +23,7 @@ properties:
> >        - ni,169445-nand-gpio
> >        - wd,mbl-gpio # Western Digital MyBook Live memory-mapped GPIO controller
> >        - intel,ixp4xx-expansion-bus-mmio-gpio
> > +      - opencores,gpio
> >  
> >    big-endian: true
> >  
> > @@ -160,3 +161,11 @@ examples:
> >              intel,ixp4xx-eb-write-enable = <1>;
> >          };
> >      };
> > +
> > +    gpio@91000000 {
> 
> Please do not grow the examples if they are exactly the same as other.

I figured this is a new compatible string with a different set of 8 bit
registers so having this example would be beneficial.

> > +        compatible = "opencores,gpio";
> > +        reg = <0x91000000 0x1>, <0x91000001 0x1>;
> > +        reg-names = "dat", "dirout";
> > +        gpio-controller;
> > +        #gpio-cells = <2>;
> > +    };
> > -- 
> > 2.51.0
> > 

  reply	other threads:[~2026-01-11 16:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09 13:43 [PATCH v3 0/6] OpenRISC de0 nano single and multicore boards Stafford Horne
2026-01-09 13:43 ` [PATCH v3 1/6] gpio: mmio: Add compatible for opencores GPIO Stafford Horne
2026-01-09 23:19   ` Linus Walleij
2026-01-10 14:03   ` Geert Uytterhoeven
2026-01-09 13:43 ` [PATCH v3 2/6] dt-bindings: gpio-mmio: Add " Stafford Horne
2026-01-09 23:20   ` Linus Walleij
2026-01-10 14:03   ` Geert Uytterhoeven
2026-01-11 10:18   ` Krzysztof Kozlowski
2026-01-11 16:46     ` Stafford Horne [this message]
2026-01-12  7:31       ` Krzysztof Kozlowski
2026-01-12  8:32         ` Stafford Horne
2026-01-11 10:20   ` Krzysztof Kozlowski
2026-01-11 16:34     ` Stafford Horne
2026-01-12  7:32       ` Krzysztof Kozlowski
2026-01-09 13:43 ` [PATCH v3 3/6] openrisc: dts: Add de0 nano config and devicetree Stafford Horne
2026-01-09 13:43 ` [PATCH v3 4/6] openrisc: Fix IPIs on simple multicore systems Stafford Horne
2026-01-09 13:43 ` [PATCH v3 5/6] openrisc: dts: Split simple smp dts to dts and dtsi Stafford Horne
2026-01-09 13:43 ` [PATCH v3 6/6] openrisc: dts: Add de0 nano multicore config and devicetree Stafford Horne

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=aWPT_HsRVC0dQ_j6@antec \
    --to=shorne@gmail.com \
    --cc=brgl@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-openrisc@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.