From: Yixun Lan <dlan@kernel.org>
To: Troy Mitchell <troy.mitchell@linux.dev>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hwmon@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-doc@vger.kernel.org
Subject: Re: [PATCH v5 5/6] riscv: dts: spacemit: Add K3 I2C6 pinctrl state
Date: Tue, 15 Sep 2026 09:04:33 +0000 [thread overview]
Message-ID: <20260915090433-GKA266329@kernel.org> (raw)
In-Reply-To: <20260914-ctl2301-v5-5-522def70acb4@linux.dev>
Hi Troy,
On 16:18 Mon 14 Sep , Troy Mitchell wrote:
> Add the K3 I2C6 pinctrl state used by boards that route I2C6 to pads 7
> and 8. Use a 25 mA drive strength, which is supported for both K3 IO
> voltage domains, and leave board-specific IO voltage selection to board
> files.
>
> Signed-off-by: Troy Mitchell <troy.mitchell@linux.dev>
> ---
> arch/riscv/boot/dts/spacemit/k3-pinctrl.dtsi | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
Reviewed-by: Yixun Lan <dlan@kernel.org>
> diff --git a/arch/riscv/boot/dts/spacemit/k3-pinctrl.dtsi b/arch/riscv/boot/dts/spacemit/k3-pinctrl.dtsi
> index 6482d24be1394..cb4f4f4e33aff 100644
> --- a/arch/riscv/boot/dts/spacemit/k3-pinctrl.dtsi
> +++ b/arch/riscv/boot/dts/spacemit/k3-pinctrl.dtsi
> @@ -101,6 +101,17 @@ i2c2-1-pins {
> };
> };
>
> + /omit-if-no-ref/
> + i2c6_1_cfg: i2c6-1-cfg {
> + i2c6-1-pins {
> + pinmux = <K3_PADCONF(7, 6)>, /* i2c6 scl */
> + <K3_PADCONF(8, 6)>; /* i2c6 sda */
> +
> + bias-pull-up = <0>;
> + drive-strength = <25>;
> + };
> + };
> +
> /omit-if-no-ref/
> i2c8_cfg: i2c8-cfg {
> i2c8-pins {
>
> --
> 2.55.0
>
--
Yixun Lan (dlan)
next prev parent reply other threads:[~2026-09-15 9:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 8:03 [PATCH v5 0/6] hwmon: (lm63) Add Sensylink CTF2301 support Troy Mitchell
2026-09-14 8:03 ` [PATCH v5 1/6] dt-bindings: vendor-prefixes: Add Sensylink Troy Mitchell
2026-09-14 15:26 ` Guenter Roeck
2026-09-14 8:03 ` [PATCH v5 2/6] dt-bindings: hwmon: Move LM63 family to a dedicated binding Troy Mitchell
2026-09-14 15:27 ` Guenter Roeck
2026-09-14 8:18 ` [PATCH v5 3/6] dt-bindings: hwmon: Add Sensylink CTF2301 Troy Mitchell
2026-09-14 15:27 ` Guenter Roeck
2026-09-14 8:18 ` [PATCH v5 4/6] hwmon: (lm63) Add Sensylink CTF2301 support Troy Mitchell
2026-09-14 15:28 ` Guenter Roeck
2026-09-14 8:18 ` [PATCH v5 5/6] riscv: dts: spacemit: Add K3 I2C6 pinctrl state Troy Mitchell
2026-09-15 9:04 ` Yixun Lan [this message]
2026-09-14 8:18 ` [PATCH v5 6/6] riscv: dts: spacemit: Add CTF2301 on K3 CoM260 Troy Mitchell
2026-09-15 9:05 ` 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=20260915090433-GKA266329@kernel.org \
--to=dlan@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=rdunlap@infradead.org \
--cc=robh@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=spacemit@lists.linux.dev \
--cc=troy.mitchell@linux.dev \
/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®