From: Krzysztof Kozlowski <krzk@kernel.org>
To: Stafford Horne <shorne@gmail.com>, LKML <linux-kernel@vger.kernel.org>
Cc: Linux OpenRISC <linux-openrisc@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v5 1/6] dt-bindings: gpio-mmio: Correct opencores GPIO
Date: Wed, 14 Jan 2026 16:43:35 +0100 [thread overview]
Message-ID: <0bb9de0d-f811-45ff-b673-8811540b5376@kernel.org> (raw)
In-Reply-To: <20260114151328.3827992-2-shorne@gmail.com>
On 14/01/2026 16:13, Stafford Horne wrote:
> In commit f48b5e8bc2e1 ("dt-bindings: gpio-mmio: Add compatible
> string for opencores,gpio") we marked opencores,gpio to be allowed with
> brcm,bcm6345-gpio. This was wrong, opencores,gpio is not hardware
> equivalent to brcm,bcm6345-gpio. It has a different register map and
"is not compatible with brcm,...."
> is 8-bit vs braodcom which is 32-bit. Change opencores,gpio to be a
> separate compatible string for MMIO GPIO.
>
> Fixes: f48b5e8bc2e1 ("dt-bindings: gpio-mmio: Add compatible string for opencores,gpio")
> Signed-off-by: Stafford Horne <shorne@gmail.com>
> ---
> Since v4:
> - New patch.
> - Rebased old patch and rewrote commit message.
>
> .../devicetree/bindings/gpio/gpio-mmio.yaml | 16 ++++++----------
> 1 file changed, 6 insertions(+), 10 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/gpio/gpio-mmio.yaml b/Documentation/devicetree/bindings/gpio/gpio-mmio.yaml
> index 7ee40b9bc562..a8823ca65e78 100644
> --- a/Documentation/devicetree/bindings/gpio/gpio-mmio.yaml
> +++ b/Documentation/devicetree/bindings/gpio/gpio-mmio.yaml
> @@ -18,16 +18,12 @@ description:
>
> properties:
> compatible:
> - oneOf:
> - - 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
> - - items:
> - - enum:
> - - opencores,gpio
> - - const: brcm,bcm6345-gpio
> + 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
> + - opencores,gpio
So if you are changing all of the lines here, you can as well sort it
and put the new entry not at the end but in alphabetical spot.
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-01-14 15:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 15:13 [PATCH v5 0/6] OpenRISC de0 nano single and multicore boards Stafford Horne
2026-01-14 15:13 ` [PATCH v5 1/6] dt-bindings: gpio-mmio: Correct opencores GPIO Stafford Horne
2026-01-14 15:36 ` Geert Uytterhoeven
2026-01-14 15:48 ` Stafford Horne
2026-01-14 15:43 ` Krzysztof Kozlowski [this message]
2026-01-14 15:50 ` Stafford Horne
2026-01-14 15:13 ` [PATCH v5 2/6] gpio: mmio: Add compatible for " Stafford Horne
2026-01-14 15:13 ` [PATCH v5 3/6] openrisc: dts: Add de0 nano config and devicetree Stafford Horne
2026-01-14 15:13 ` [PATCH v5 4/6] openrisc: Fix IPIs on simple multicore systems Stafford Horne
2026-01-14 15:13 ` [PATCH v5 5/6] openrisc: dts: Split simple smp dts to dts and dtsi Stafford Horne
2026-01-14 15:13 ` [PATCH v5 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=0bb9de0d-f811-45ff-b673-8811540b5376@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
all inboxes | Powered by JetHome®