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: Mon, 15 Dec 2025 16:57:45 +0000 [thread overview]
Message-ID: <20251215-skillet-perceive-2b564a29ed71@spud> (raw)
In-Reply-To: <20251214180158.3955285-2-shorne@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1505 bytes --]
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
> reg = <0x91000000 0x1>, <0x91000001 0x1>;
> reg-names = "dat", "dirout";
> gpio-controller;
> #gpio-cells = <2>;
> status = "okay";
> };
>
> Link: https://opencores.org/projects/gpio
> Signed-off-by: Stafford Horne <shorne@gmail.com>
> ---
> Documentation/devicetree/bindings/gpio/gpio-mmio.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/gpio/gpio-mmio.yaml b/Documentation/devicetree/bindings/gpio/gpio-mmio.yaml
> index b4d55bf6a285..0490580df19e 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
>
> --
> 2.51.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-12-15 16:57 UTC|newest]
Thread overview: 11+ 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 [this message]
2025-12-15 18:40 ` Stafford Horne
2025-12-15 19:34 ` Stafford Horne
2025-12-16 0:05 ` Conor Dooley
2025-12-14 18:01 ` [PATCH 2/5] openrisc: dts: Add de0 nano config and devicetree Stafford Horne
2025-12-14 18:01 ` [PATCH 4/5] openrisc: dts: Split simple smp dts to dts and dtsi Stafford Horne
2025-12-15 7:30 ` Stafford Horne
2025-12-15 16:58 ` Conor Dooley
2025-12-15 18:19 ` Stafford Horne
2025-12-14 18:01 ` [PATCH 5/5] 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=20251215-skillet-perceive-2b564a29ed71@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