From: "Troy Mitchell" <troy.mitchell@linux.dev>
To: "Troy Mitchell" <troy.mitchell@linux.dev>,
"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>, "Yixun Lan" <dlan@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>
Cc: <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 v3 6/6] riscv: dts: spacemit: Add CTF2301 on K3 CoM260
Date: Mon, 10 Aug 2026 16:20:05 +0800 [thread overview]
Message-ID: <DKL487DPH7KA.3GNYMRSBR1JY3@linux.dev> (raw)
In-Reply-To: <20260805134119-GKJ77474@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
> > +&pinctrl {
> > + i2c6-1-cfg {
> I'd prefer to use the reference, keep it short & close to where it's used
>
> &i2c6_1_cfg
>
> > + i2c6-1-pins {
> > + power-source = <3300>;
> > + };
> > + };
> > +};
> > +
> > +&i2c6 {
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&i2c6_1_cfg>;
> > + status = "okay";
> > +
> > + temperature-sensor@4c {
> > + compatible = "sensylink,ctf2301";
> > + reg = <0x4c>;
> > + };
> > +};
My intention here was to keep all board-specific pin configuration
overrides under a single &pinctrl block, so that they can be found and
maintained in one place. Using a separate top-level reference for each pin
group would tend to scatter those overrides throughout the board DTS as
more groups are customized. The &pinctrl block is also placed immediately
before the &i2c6 consumer.
Would keeping the current structure be acceptable for that reason? If you
still prefer the direct reference, I will change it to &i2c6_1_cfg in the
next revision.
- Troy
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Troy Mitchell" <troy.mitchell@linux.dev>
To: "Troy Mitchell" <troy.mitchell@linux.dev>,
"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>, "Yixun Lan" <dlan@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>
Cc: <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 v3 6/6] riscv: dts: spacemit: Add CTF2301 on K3 CoM260
Date: Mon, 10 Aug 2026 16:20:05 +0800 [thread overview]
Message-ID: <DKL487DPH7KA.3GNYMRSBR1JY3@linux.dev> (raw)
In-Reply-To: <20260805134119-GKJ77474@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 1070 bytes --]
> > +&pinctrl {
> > + i2c6-1-cfg {
> I'd prefer to use the reference, keep it short & close to where it's used
>
> &i2c6_1_cfg
>
> > + i2c6-1-pins {
> > + power-source = <3300>;
> > + };
> > + };
> > +};
> > +
> > +&i2c6 {
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&i2c6_1_cfg>;
> > + status = "okay";
> > +
> > + temperature-sensor@4c {
> > + compatible = "sensylink,ctf2301";
> > + reg = <0x4c>;
> > + };
> > +};
My intention here was to keep all board-specific pin configuration
overrides under a single &pinctrl block, so that they can be found and
maintained in one place. Using a separate top-level reference for each pin
group would tend to scatter those overrides throughout the board DTS as
more groups are customized. The &pinctrl block is also placed immediately
before the &i2c6 consumer.
Would keeping the current structure be acceptable for that reason? If you
still prefer the direct reference, I will change it to &i2c6_1_cfg in the
next revision.
- Troy
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-08-10 8:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 8:52 [PATCH v3 0/6] hwmon: (lm63) Add Sensylink CTF2301 support Troy Mitchell
2026-08-05 8:52 ` Troy Mitchell
2026-08-05 9:00 ` [PATCH v3 1/6] dt-bindings: vendor-prefixes: Add Sensylink Troy Mitchell
2026-08-05 9:00 ` Troy Mitchell
2026-08-05 9:27 ` sashiko-bot
2026-08-06 8:00 ` Krzysztof Kozlowski
2026-08-06 8:00 ` Krzysztof Kozlowski
2026-08-05 9:00 ` [PATCH v3 2/6] dt-bindings: hwmon: Move LM63 family to a dedicated binding Troy Mitchell
2026-08-05 9:00 ` Troy Mitchell
2026-08-05 9:35 ` sashiko-bot
2026-08-06 8:02 ` Krzysztof Kozlowski
2026-08-06 8:02 ` Krzysztof Kozlowski
2026-08-05 9:00 ` [PATCH v3 3/6] dt-bindings: hwmon: Add Sensylink CTF2301 Troy Mitchell
2026-08-05 9:00 ` Troy Mitchell
2026-08-05 9:30 ` sashiko-bot
2026-08-06 8:02 ` Krzysztof Kozlowski
2026-08-06 8:02 ` Krzysztof Kozlowski
2026-08-05 9:00 ` [PATCH v3 4/6] hwmon: (lm63) Add Sensylink CTF2301 support Troy Mitchell
2026-08-05 9:00 ` Troy Mitchell
2026-08-05 9:40 ` sashiko-bot
2026-08-06 19:30 ` Guenter Roeck
2026-08-06 19:30 ` Guenter Roeck
2026-08-05 9:00 ` [PATCH v3 5/6] riscv: dts: spacemit: Add K3 I2C6 pinctrl state Troy Mitchell
2026-08-05 9:00 ` Troy Mitchell
2026-08-05 9:32 ` sashiko-bot
2026-08-05 9:00 ` [PATCH v3 6/6] riscv: dts: spacemit: Add CTF2301 on K3 CoM260 Troy Mitchell
2026-08-05 9:00 ` Troy Mitchell
2026-08-05 9:30 ` sashiko-bot
2026-08-05 13:41 ` Yixun Lan
2026-08-05 13:41 ` Yixun Lan
2026-08-10 8:20 ` Troy Mitchell [this message]
2026-08-10 8:20 ` Troy Mitchell
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=DKL487DPH7KA.3GNYMRSBR1JY3@linux.dev \
--to=troy.mitchell@linux.dev \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dlan@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=robh@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=spacemit@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.