From: "Gary Lau" <zgliu@foxmail.com>
To: "Stafford Horne" <shorne@gmail.com>
Cc: linusw <linusw@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-openrisc <linux-openrisc@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>, robh <robh@kernel.org>,
krzk+dt <krzk+dt@kernel.org>, conor+dt <conor+dt@kernel.org>,
geert+renesas <geert+renesas@glider.be>,
"krzysztof.kozlowski" <krzysztof.kozlowski@oss.qualcomm.com>,
brgl <brgl@kernel.org>, linux-gpio <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v6 1/6] dt-bindings: gpio-mmio: Correct opencores GPIO
Date: Fri, 23 Jan 2026 22:08:40 +0800 [thread overview]
Message-ID: <tencent_5B5F194F6B5511962378DEC1B1B043F3A705@qq.com> (raw)
Hi Stafford,
I've tested the "brcm,bcm6345-gpio" driver with the OpenCores 8-bit GPIO core, and it is working as expected.
For reference, here is the hardware connection logic I used for the OpenRISC to OpenCores GPIO interface:
Verilog:
simple_gpio gpio0 (
.clk_i (clk_i),
.rst_i (rst_i),
.cyc_i (cyc_i & (|sel_i)),
.stb_i (stb_i & (|sel_i)),
.adr_i (adr_i[2]),
.we_i (we_i),
.dat_i (dat_i[7:0]),
.ack_o (ack_o),
.dat_o (dat_o[7:0]),
.gpio (gpio[7:0]),
.gpio_i (gpio_i)
);
And here is the corresponding part of my dts:
gpio0: gpio@91000000 {
compatible = "brcm,bcm6345-gpio";
reg = <0x91000000 0x4>, <0x91000004 0x4>;
reg-names = "dat", "dirout";
gpio-controller;
big-endian;
status = "okay";
next reply other threads:[~2026-01-23 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 14:08 Gary Lau [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-23 14:18 Gary Lau
2026-01-24 12:36 ` Stafford Horne
2026-01-15 15:09 [PATCH v6 0/6] OpenRISC de0 nano single and multicore boards Stafford Horne
2026-01-15 15:09 ` [PATCH v6 1/6] dt-bindings: gpio-mmio: Correct opencores GPIO Stafford Horne
2026-01-18 23:19 ` Linus Walleij
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=tencent_5B5F194F6B5511962378DEC1B1B043F3A705@qq.com \
--to=zgliu@foxmail.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--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®