Devicetree
 help / color / mirror / Atom feed
From: Stefano Radaelli <stefano.radaelli21@gmail.com>
To: Daniel Baluta <daniel.baluta@oss.nxp.com>
Cc: Frank Li <Frank.Li@nxp.com>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	pierluigi.p@variscite.com,
	Stefano Radaelli <stefano.r@variscite.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH v2 1/1] arm64: dts: freescale: imx93-var: Add Cortex-M33 configurations
Date: Thu, 19 Nov 2026 10:28:42 +0100	[thread overview]
Message-ID: <av7BStmo7w4_rPci@Lord-Beerus.station> (raw)
In-Reply-To: <be20af64-e729-4d1e-aba1-c8512ac6e775@oss.nxp.com>

On Thu, Nov 19, 2026 at 11:18:45AM +0200, Daniel Baluta wrote:
> 
> Use "reserved" instead of "disabled" for all the nodes that need not to probe
> on the Application processor because they are used by the M33 FW.
> 
> Also, instead of disable in the commit message I think it is better to say "reserve".
> 

Hi Daniel,

That makes sense, thank you for your review!

I'll use "reserved" for the peripherals used directly by the Cortex-M
firmware, and keep "disabled" for devices that become unavailable as a
consequence.
For example, Wi-Fi cannot use its reset GPIO because GPIO4 is reserved
for the M33.

Does that match what you had in mind?

Best regards,
Stefano

  reply	other threads:[~2026-11-19  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19  9:06 [PATCH v2 1/1] arm64: dts: freescale: imx93-var: Add Cortex-M33 configurations Stefano Radaelli
2026-11-19  9:18 ` Daniel Baluta
2026-11-19  9:28   ` Stefano Radaelli [this message]
2026-11-19  9:42     ` Daniel Baluta
2026-11-19  9:58       ` Stefano Radaelli

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=av7BStmo7w4_rPci@Lord-Beerus.station \
    --to=stefano.radaelli21@gmail.com \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel.baluta@oss.nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierluigi.p@variscite.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=stefano.r@variscite.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