From: Krzysztof Kozlowski <krzk@kernel.org>
To: Stafford Horne <shorne@gmail.com>
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: Mon, 12 Jan 2026 08:31:03 +0100 [thread overview]
Message-ID: <fb977dc3-54ea-4c58-be85-111fd7e1c371@kernel.org> (raw)
In-Reply-To: <aWPT_HsRVC0dQ_j6@antec>
On 11/01/2026 17:46, Stafford Horne wrote:
> 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
There is no 1/6!
> driver there before we add it here.
How does it matter? How can you add something to the driver before you
document the ABI? Did you read the submitting patches doc?
>
> Sorry, I thought the series and the over letter would be enough to understand
> what I meant by the "Fixup" description here.
You still did not answer to my comments.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-01-12 7:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260109134409.2153333-1-shorne@gmail.com>
2026-01-09 13:43 ` [PATCH v3 2/6] dt-bindings: gpio-mmio: Add opencores GPIO 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 [this message]
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 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=fb977dc3-54ea-4c58-be85-111fd7e1c371@kernel.org \
--to=krzk@kernel.org \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@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 \
--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