devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: Andrew Davis <afd@ti.com>
Cc: "Francesco Dolcini" <francesco@dolcini.it>,
	"Nishanth Menon" <nm@ti.com>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	"Tero Kristo" <kristo@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Parth Pancholi" <parth.pancholi@toradex.com>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Emanuele Ghidoli" <emanuele.ghidoli@toradex.com>,
	"Ernest Van Hoecke" <ernest.vanhoecke@toradex.com>,
	"João Paulo Gonçalves" <joao.goncalves@toradex.com>,
	"Francesco Dolcini" <francesco.dolcini@toradex.com>
Subject: Re: [PATCH v1 2/3] arm64: dts: ti: Add Aquila AM69 Support
Date: Thu, 6 Nov 2025 16:03:09 +0100	[thread overview]
Message-ID: <20251106150309.GA44898@francesco-nb> (raw)
In-Reply-To: <be8040c0-76b1-46e3-bd89-841cbfa10c84@ti.com>

Hello Andrew,

On Thu, Nov 06, 2025 at 07:32:44AM -0600, Andrew Davis wrote:
> On 11/6/25 4:19 AM, Francesco Dolcini wrote:
> > On Wed, Nov 05, 2025 at 02:01:35PM -0600, Andrew Davis wrote:
> > > On 11/5/25 5:53 AM, Francesco Dolcini wrote:
> > > > On Tue, Nov 04, 2025 at 11:41:54AM -0600, Andrew Davis wrote:
> > > > > On 11/4/25 8:52 AM, Francesco Dolcini wrote:

...

> > > > > > +/* Aquila SPI_1 */
> > > > > > +&main_spi2 {
> > > > > > +	pinctrl-names = "default";
> > > > > > +	pinctrl-0 = <&pinctrl_main_spi2>, <&pinctrl_main_spi2_cs0>;
> > > > > > +	status = "disabled";
> > > > > 
> > > > > This is already disabled by default in the SoC dtsi file.
> > > > 
> > > > Yes, known. Is this an issue?
> > > > 
> > > > This node must be disabled, no matter what is present in any included
> > > > dtsi file, it's a deliberate decision.
> > > > 
> > > > This dtsi file describes a SoM, the used pins/functions are defined on
> > > > the pinout, but this node cannot be enabled unless the SoM is mated with
> > > > a carrier board that is exposing it.
> > > 
> > > Same as my point above, you shouldn't enable nodes that are not used
> > > or have anything attached. The SoM only has some edge connectors so
> > > it should not be enabled at the SoM level, that we seem to agree, but
> > > the carrier board doesn't connect those lines to anything either. They
> > > just run to a pin header with nothing attached, how is that header
> > > any different than the pins on the edge of the SoM?
> > 
> > You are commenting something unrelated here, or I am not understanding
> > you.
> 
> Yes this was a bit of a tangent to the comment above. The point here
> was more on the pinmux, as a new carrier board might use these pins
> for something other than SPI, the pinmuxing shouldn't be done at the
> SoM dtsi level. Instead do it at the point the node is connected to
> some hardware on the carrier board in its DTS.

Our SoM implements a specific pinout, with well defined functions,
therefore the functionality of the pin is defined at the SoM level [1].

[1] https://docs1.toradex.com/116801-aquila_family_specification.pdf
	  page 13, 14, 15


Francesco


  reply	other threads:[~2025-11-06 15:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04 14:49 [PATCH v1 0/3] arm64: dts: ti: Add Aquila AM69 Support Francesco Dolcini
2025-11-04 14:52 ` [PATCH v1 1/3] dt-bindings: arm: ti: add Toradex Aquila AM69 Francesco Dolcini
2025-11-04 14:52   ` [PATCH v1 2/3] arm64: dts: ti: Add Aquila AM69 Support Francesco Dolcini
2025-11-04 17:41     ` Andrew Davis
2025-11-05 11:53       ` Francesco Dolcini
2025-11-05 20:01         ` Andrew Davis
2025-11-06 10:19           ` Francesco Dolcini
2025-11-06 13:32             ` Andrew Davis
2025-11-06 15:03               ` Francesco Dolcini [this message]
2025-11-04 14:52   ` [PATCH v1 3/3] arm64: dts: ti: am69-aquila: Add Clover Francesco Dolcini
2025-11-04 17:20   ` [PATCH v1 1/3] dt-bindings: arm: ti: add Toradex Aquila AM69 Conor Dooley

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=20251106150309.GA44898@francesco-nb \
    --to=francesco@dolcini.it \
    --cc=afd@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=emanuele.ghidoli@toradex.com \
    --cc=ernest.vanhoecke@toradex.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=joao.goncalves@toradex.com \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=parth.pancholi@toradex.com \
    --cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).