From: Yixun Lan <dlan@gentoo.org>
To: Linus Walleij <linusw@kernel.org>
Cc: Troy Mitchell <troy.mitchell@linux.spacemit.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>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2 0/3] pinctrl: spacemit: support I/O power domain configuration
Date: Tue, 20 Jan 2026 08:31:50 +0800 [thread overview]
Message-ID: <20260120003150-GYA56672@gentoo.org> (raw)
In-Reply-To: <CAD++jLnM=1iyb0-=Jzqq+jPKtSvR+dbb1w8BNNcr+evdQFg4Eg@mail.gmail.com>
Hi Linus,
On 00:52 Tue 20 Jan , Linus Walleij wrote:
> On Thu, Jan 8, 2026 at 7:43 AM Troy Mitchell
> <troy.mitchell@linux.spacemit.com> wrote:
>
> > This series adds support for configuring IO power domain voltage for
> > dual-voltage GPIO banks on the Spacemit K1 SoC.
> >
> > On K1, IO domain power control registers determine whether a GPIO bank
> > operates at 1.8V or 3.3V. These registers default to 3.3V operation,
> > which may lead to functional failures when GPIO banks are externally
> > supplied with 1.8V but internally remain configured for 3.3V.
> >
> > The IO power domain registers are implemented as secure registers and
> > require an explicit unlock sequence via the AIB Secure Access Register
> > (ASAR), located in the APBC register space.
> >
> > This series ensures that pin voltage configuration correctly reflects
> > hardware requirements.
> >
> > Signed-off-by: Troy Mitchell <troy.mitchell@linux.spacemit.com>
>
> Excellent work in this patch series Troy!
>
> > Troy Mitchell (3):
> > dt-bindings: pinctrl: spacemit: add syscon property
> > pinctrl: spacemit: support I/O power domain configuration
>
> These two patches applied to the pin control tree.
>
> > riscv: dts: spacemit: modify pinctrl node in dtsi
>
> Please funnel this one through the SoC tree.
>
Thanks, I will take care of this
> Yours,
> Linus Walleij
>
--
Yixun Lan (dlan)
next prev parent reply other threads:[~2026-01-20 0:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 6:42 [PATCH v2 0/3] pinctrl: spacemit: support I/O power domain configuration Troy Mitchell
2026-01-08 6:42 ` [PATCH v2 1/3] dt-bindings: pinctrl: spacemit: add syscon property Troy Mitchell
2026-01-15 16:02 ` Rob Herring (Arm)
2026-01-08 6:42 ` [PATCH v2 2/3] pinctrl: spacemit: support I/O power domain configuration Troy Mitchell
2026-01-08 6:42 ` [PATCH v2 3/3] riscv: dts: spacemit: modify pinctrl node in dtsi Troy Mitchell
2026-01-08 7:37 ` Yixun Lan
2026-01-09 1:31 ` Troy Mitchell
2026-01-19 23:53 ` Linus Walleij
2026-01-19 23:52 ` [PATCH v2 0/3] pinctrl: spacemit: support I/O power domain configuration Linus Walleij
2026-01-20 0:31 ` Yixun Lan [this message]
2026-01-20 0:55 ` (subset) " Yixun Lan
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=20260120003150-GYA56672@gentoo.org \
--to=dlan@gentoo.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--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-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.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