Re: [PATCH v3 6/6] riscv: dts: spacemit: Add CTF2301 on K3 CoM260
"Troy Mitchell" <[email protected]>
| Newsgroups | dev.linux.lists.spacemit,org.infradead.lists.linux-riscv,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-doc,org.kernel.vger.linux-hwmon,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
> > +&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
signature.asc
(application/pgp-signature, 273 B)
-----BEGIN PGP SIGNATURE----- iJcEABYKAD8WIQSL4Ay2cExaPXAQcU2YCe+A+TM0LwUCanmJtSEcdHJveS5taXRj aGVsbEBsaW51eC5zcGFjZW1pdC5jb20ACgkQmAnvgPkzNC8CFgEAiJSPpno04iz/ cz/ScQC1rhjqbfbKZVHCF6VJ27Lw8fwA/jzuR+UYxLorJLN/rAcuXQS8gF7HrQ5p lCjF5MwhGh8J =4F8l -----END PGP SIGNATURE-----