All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
	Francesco Dolcini <francesco.dolcini@toradex.com>,
	Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 3/5] arm64: dts: ti: add verdin am62
Date: Tue, 30 May 2023 11:53:51 -0500	[thread overview]
Message-ID: <20230530165351.rqpu7go3kw6j3upc@storable> (raw)
In-Reply-To: <ZHYl8/8k4CTm/2LW@francesco-nb.int.toradex.com>

On 18:36-20230530, Francesco Dolcini wrote:
> On Tue, May 30, 2023 at 07:10:44AM -0500, Nishanth Menon wrote:
> > On 16:36-20230524, Francesco Dolcini wrote:
> > > +/* Verdin I2C_2_DSI */
> > > +&main_i2c2 {
> > > +	status = "okay";
> > 
> > Here and few other dtsis:
> > you should set status along with pinmux.
> This is already done in the SoM dtsi, same applies to the other comment
> you have on this pinmux topic.
> 
> To rephrase what's hopefully is already written in the commit
> message/series description, or at least it was in my intention.
> 
> The system is modular, with multiple SoM variant and multiple carrier
> boards. Standard interfaces are defined at the family level, e.g.
> already in the SoM, in the carrier board DT file peripherals are just
> enabled, the pinmux is already defined in the common som.dtsi [1][2][3]
> files and the carrier board just use those unless there is some kind of
> non-standard deviation.
> 
> This prevents duplication and simplify writing device tree file for board
> that use standard Verdin family interfaces. This should be visible
> looking at this series in which 3 different boards (Dev, Yavia and
> Dahlia) are added.

It helps clarity if the node is marked "okay" when all the necessary
properties required for operation (in this case pinmux) is enabled. I
don't see a big change as a result. Just stops people from hunting for
where pinmux is actually done.

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
	Francesco Dolcini <francesco.dolcini@toradex.com>,
	Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 3/5] arm64: dts: ti: add verdin am62
Date: Tue, 30 May 2023 11:53:51 -0500	[thread overview]
Message-ID: <20230530165351.rqpu7go3kw6j3upc@storable> (raw)
In-Reply-To: <ZHYl8/8k4CTm/2LW@francesco-nb.int.toradex.com>

On 18:36-20230530, Francesco Dolcini wrote:
> On Tue, May 30, 2023 at 07:10:44AM -0500, Nishanth Menon wrote:
> > On 16:36-20230524, Francesco Dolcini wrote:
> > > +/* Verdin I2C_2_DSI */
> > > +&main_i2c2 {
> > > +	status = "okay";
> > 
> > Here and few other dtsis:
> > you should set status along with pinmux.
> This is already done in the SoM dtsi, same applies to the other comment
> you have on this pinmux topic.
> 
> To rephrase what's hopefully is already written in the commit
> message/series description, or at least it was in my intention.
> 
> The system is modular, with multiple SoM variant and multiple carrier
> boards. Standard interfaces are defined at the family level, e.g.
> already in the SoM, in the carrier board DT file peripherals are just
> enabled, the pinmux is already defined in the common som.dtsi [1][2][3]
> files and the carrier board just use those unless there is some kind of
> non-standard deviation.
> 
> This prevents duplication and simplify writing device tree file for board
> that use standard Verdin family interfaces. This should be visible
> looking at this series in which 3 different boards (Dev, Yavia and
> Dahlia) are added.

It helps clarity if the node is marked "okay" when all the necessary
properties required for operation (in this case pinmux) is enabled. I
don't see a big change as a result. Just stops people from hunting for
where pinmux is actually done.

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-05-30 16:54 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24 14:36 [PATCH v1 0/5] Add Toradex Verdin AM62 Francesco Dolcini
2023-05-24 14:36 ` Francesco Dolcini
2023-05-24 14:36 ` [PATCH v1 1/5] dt-bindings: arm: ti: add toradex,verdin-am62 et al Francesco Dolcini
2023-05-24 14:36   ` Francesco Dolcini
2023-05-24 17:48   ` Andrew Davis
2023-05-24 17:48     ` Andrew Davis
2023-05-24 19:10     ` Nishanth Menon
2023-05-24 19:10       ` Nishanth Menon
2023-05-24 19:20     ` Francesco Dolcini
2023-05-24 19:20       ` Francesco Dolcini
2023-05-31  8:29     ` Krzysztof Kozlowski
2023-05-31  8:29       ` Krzysztof Kozlowski
2023-05-24 19:15   ` Conor Dooley
2023-05-24 19:15     ` Conor Dooley
2023-05-30 12:12   ` Nishanth Menon
2023-05-30 12:12     ` Nishanth Menon
2023-05-30 16:58     ` Francesco Dolcini
2023-05-30 16:58       ` Francesco Dolcini
2023-05-24 14:36 ` [PATCH v1 2/5] arm64: defconfig: enable drivers for Verdin AM62 Francesco Dolcini
2023-05-24 14:36   ` Francesco Dolcini
2023-05-24 14:36 ` [PATCH v1 3/5] arm64: dts: ti: add verdin am62 Francesco Dolcini
2023-05-24 14:36   ` Francesco Dolcini
2023-05-30 10:18   ` Francesco Dolcini
2023-05-30 10:18     ` Francesco Dolcini
2023-05-30 12:10   ` Nishanth Menon
2023-05-30 12:10     ` Nishanth Menon
2023-05-30 13:31     ` Raghavendra, Vignesh
2023-05-30 13:31       ` Raghavendra, Vignesh
2023-05-30 16:36     ` Francesco Dolcini
2023-05-30 16:36       ` Francesco Dolcini
2023-05-30 16:53       ` Nishanth Menon [this message]
2023-05-30 16:53         ` Nishanth Menon
2023-05-30 17:17         ` Francesco Dolcini
2023-05-30 17:17           ` Francesco Dolcini
2023-05-24 14:36 ` [PATCH v1 4/5] arm64: dts: ti: add verdin am62 dahlia Francesco Dolcini
2023-05-24 14:36   ` Francesco Dolcini
2023-05-24 14:36 ` [PATCH v1 5/5] arm64: dts: ti: add verdin am62 yavia Francesco Dolcini
2023-05-24 14:36   ` Francesco Dolcini

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=20230530165351.rqpu7go3kw6j3upc@storable \
    --to=nm@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=francesco.dolcini@toradex.com \
    --cc=francesco@dolcini.it \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@ti.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 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.