From: Yixun Lan <dlan@gentoo.org>
To: Guodong Xu <guodong@riscstar.com>
Cc: Linus Walleij <linusw@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Troy Mitchell <troy.mitchell@linux.spacemit.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/4] dt-bindings: pinctrl: spacemit: add K3 SoC support
Date: Sat, 10 Jan 2026 06:56:08 +0800 [thread overview]
Message-ID: <20260109225608-GYA8877@gentoo.org> (raw)
In-Reply-To: <CAH1PCMaXW4469pFRGC+HcixO7PGLQpKKJ_Z5VEhHUMdd3DNWTg@mail.gmail.com>
Hi Guodong,
On 20:20 Fri 09 Jan , Guodong Xu wrote:
> Hi, Yixun
>
> On Fri, Jan 2, 2026 at 3:04 PM Yixun Lan <dlan@gentoo.org> wrote:
> >
> > Add new compatible string for SpacemiT K3 SoC, the pinctrl IP shares
> > almost same logic with previous K1 generation, but has different register
> > offset and pin configuration, for example the drive strength and
> > schmitter trigger settings has been changed.
> >
> > Signed-off-by: Yixun Lan <dlan@gentoo.org>
> > ---
> > .../devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml | 10 +++++++++-
> > 1 file changed, 9 insertions(+), 1 deletion(-)
> >
> > diff --git a/Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml
> > index 609d7db97822..9a76cffcbaee 100644
> > --- a/Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml
> > +++ b/Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml
> > @@ -81,6 +83,12 @@ patternProperties:
> > - enum: [ 7, 10, 13, 16, 19, 23, 26, 29 ]
> > description: For K1 SoC, 3.3V voltage output
> >
> > + - enum: [ 2, 4, 6, 7, 9, 11, 13, 14, 21, 23, 25, 26, 28, 30, 31, 33 ]
> > + description: For K3 SoC, 1.8V voltage output
> > +
..
> > + - enum: [ 3, 5, 7, 9, 11, 13, 15, 17, 25, 27, 29, 31, 33, 35, 37, 38 ]
> > + description: For K3 SoC, 1.8V voltage output
>
> Should one of these be 3.3V? Both descriptions currently specify 1.8V.
>
right, the latter one should be changed to 3.3V, I will send a patch
to fix this.
--
Yixun Lan (dlan)
next prev parent reply other threads:[~2026-01-09 22:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 7:00 [PATCH v3 0/4] pinctrl: spacemit: add support for K3 SoC Yixun Lan
2026-01-02 7:00 ` [PATCH v3 1/4] dt-bindings: pinctrl: spacemit: convert drive strength to schema format Yixun Lan
2026-01-02 11:01 ` Krzysztof Kozlowski
2026-01-02 7:00 ` [PATCH v3 2/4] dt-bindings: pinctrl: spacemit: add K3 SoC support Yixun Lan
2026-01-02 11:01 ` Krzysztof Kozlowski
2026-01-09 12:20 ` Guodong Xu
2026-01-09 22:56 ` Yixun Lan [this message]
2026-01-02 7:00 ` [PATCH v3 3/4] pinctrl: spacemit: k3: add initial pin support Yixun Lan
2026-01-02 7:00 ` [PATCH v3 4/4] pinctrl: spacemit: k3: adjust drive strength and schmitter trigger Yixun Lan
2026-01-07 14:09 ` [PATCH v3 0/4] pinctrl: spacemit: add support for K3 SoC 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=20260109225608-GYA8877@gentoo.org \
--to=dlan@gentoo.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=guodong@riscstar.com \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
--cc=troy.mitchell@linux.spacemit.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