From: "Yulin Lu" <luyulin@eswincomputing.com>
To: "Samuel Holland" <samuel.holland@sifive.com>
Cc: "Pinkesh Vaghela" <pinkesh.vaghela@einfochips.com>,
"Darshan Prajapati" <darshan.prajapati@einfochips.com>,
"Pritesh Patel" <pritesh.patel@einfochips.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Paul Walmsley" <pjw@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>,
"Andi Shyti" <andi.shyti@kernel.org>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
"Min Lin" <linmin@eswincomputing.com>
Subject: Re: Re: [PATCH v4 3/7] riscv: dts: eswin: eic7700: add pinctrl support
Date: Fri, 9 Oct 2026 15:22:00 +0800 (GMT+08:00) [thread overview]
Message-ID: <2dd7292f.aba1.1a11f8a5115.Coremail.luyulin@eswincomputing.com> (raw)
In-Reply-To: <b7428a65-b303-4ed4-bdc0-caf5a89b4712@sifive.com>
Hi Samuel,
...
>
> > + default-pins-grp {
>
> My assumption is that there would be one group per peripheral (e.g. SPI bus,
> eMMC, UART) that groups all of the pins used by that peripheral, with multiple
> "-pins" nodes in the case that subsets of those pins need different pinconf
> settings.
>
I think users can define groups based on their usage requirements (a group can
contain definitions for gpio, uart, i2c, and other pins), and referencing a group
will apply the configuration for all the pins in it. Alternatively, users can
reference individual pins directly to configure just one item. Which design to
choose is determined by the user's actual use case, so I have listed out the
definitions for all the pins here.
...
> > diff --git a/arch/riscv/boot/dts/eswin/eic7700.dtsi b/arch/riscv/boot/dts/eswin/eic7700.dtsi
> > index b3a230870315..b16e3e28632c 100644
> > --- a/arch/riscv/boot/dts/eswin/eic7700.dtsi
> > +++ b/arch/riscv/boot/dts/eswin/eic7700.dtsi
> > @@ -349,6 +349,11 @@ gpioD: gpio-port@3 {
> > };
> > };
> >
> > + pinctrl: pinctrl@51600080 {
> > + compatible = "eswin,eic7700-pinctrl";
> > + reg = <0x0 0x51600080 0x0 0x1fff80>;
> > + };
> > +
> > clk: clock-controller@51828000 {
> > compatible = "eswin,eic7700-clock";
> > reg = <0x0 0x51828000 0x0 0x300>;
We will change the other comments in next version.
Regards,
Yulin Lu
next prev parent reply other threads:[~2026-10-09 7:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 7:00 [PATCH v4 0/7] riscv: eswin: eic7700: Add support for clocks, resets, pinctrl, HSP bus, I2C and watchdog Pinkesh Vaghela
2026-08-14 7:00 ` [PATCH v4 1/7] riscv: dts: eswin: add reset generator for EIC7700 SoC Pinkesh Vaghela
2026-08-14 7:00 ` [PATCH v4 2/7] riscv: dts: eswin: add clock " Pinkesh Vaghela
2026-08-14 7:00 ` [PATCH v4 3/7] riscv: dts: eswin: eic7700: add pinctrl support Pinkesh Vaghela
2026-09-29 13:06 ` Samuel Holland
2026-10-09 7:22 ` Yulin Lu [this message]
2026-08-14 7:00 ` [PATCH v4 4/7] riscv: dts: eswin: add hsp bus node Pinkesh Vaghela
2026-08-14 7:00 ` [PATCH v4 5/7] dt-bindings: i2c: dw: add ESWIN EIC7700 SoC I2C controller Pinkesh Vaghela
2026-09-29 21:16 ` Andi Shyti
2026-08-14 7:00 ` [PATCH v4 6/7] riscv: dts: eswin: add I2C controller support Pinkesh Vaghela
2026-09-29 13:10 ` Samuel Holland
2026-09-30 13:06 ` Pinkesh Vaghela
2026-08-14 7:00 ` [PATCH v4 7/7] riscv: dts: eswin: add watchdog support Pinkesh Vaghela
2026-09-29 13:12 ` Samuel Holland
2026-09-30 13:08 ` Pinkesh Vaghela
2026-08-31 13:58 ` [PATCH v4 0/7] riscv: eswin: eic7700: Add support for clocks, resets, pinctrl, HSP bus, I2C and watchdog Pinkesh Vaghela
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=2dd7292f.aba1.1a11f8a5115.Coremail.luyulin@eswincomputing.com \
--to=luyulin@eswincomputing.com \
--cc=alex@ghiti.fr \
--cc=andi.shyti@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=darshan.prajapati@einfochips.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linmin@eswincomputing.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mika.westerberg@linux.intel.com \
--cc=palmer@dabbelt.com \
--cc=pinkesh.vaghela@einfochips.com \
--cc=pjw@kernel.org \
--cc=pritesh.patel@einfochips.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.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