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:34:36 +0000 [thread overview]
Message-ID: <aWPRHHhdjGE2f8aT@antec> (raw)
In-Reply-To: <20260111-amorphous-cow-of-stamina-6f2720@quoll>
On Sun, Jan 11, 2026 at 11:20:38AM +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.
> > Since v1:
> > - Fix schema to actually match the example.
> >
> > Documentation/devicetree/bindings/gpio/gpio-mmio.yaml | 9 +++++++++
> > 1 file changed, 9 insertions(+)
>
> This does not even apply now. Your previous version was applied almost
> one month before and you WERE notified about it.
>
> Why did you ignore Bartosz's reply?
Hi Krzysztof,
Sorry for the confusion, we discussed [1] this patch in the last Series with Geert
and Linus W. We decided to Fixup (replace) the original patch with this and a
patch to the GPIO MMIO driver instead. I pointed it out in the cover letter but
it may have not been clear.
I will reply to Bartosz's original mail too so he can understand the intent.
[1] https://lore.kernel.org/lkml/CAD++jLm1u9ChqsftwvbOptiG3Qo2KWxPjqN2snOVuZDYuVST5Q@mail.gmail.com/
-Stafford
next prev parent reply other threads:[~2026-01-11 16:34 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
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 [this message]
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=aWPRHHhdjGE2f8aT@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox