From: Stefano Radaelli <stefano.radaelli21@gmail.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev
Subject: [RFC] arm64: dts: freescale: imx93-var-som: Align dts adding missing components
Date: Mon, 22 Sep 2025 18:11:20 +0200 [thread overview]
Message-ID: <aNF1KOCs0eHL1Njb@Lord-Beerus> (raw)
Hi all,
the current device tree for the i.MX93 VAR-SOM is incomplete.
In particular, several peripherals that are present on the hardware
are not yet described, such as:
- audio codec
- PMIC
- WiFi + Bluetooth module
My plan is to align the DTS with the actual hardware by adding these
missing nodes.
Before preparing the patches, I would like to ask for your advice:
should I send one patch that performs the full DTS alignment (describing the
patch as an alignemnt of the dts with the actual hardware), or would
you prefer a patch series with one patch per peripheral (e.g. one for
codec, one for PMIC, one for WiFi/BT, etc.)?
I will do the same with the other Variscite SOMs and Carrier Boards
Thanks for your guidance.
Best regards,
Stefano
next reply other threads:[~2025-09-22 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 16:11 Stefano Radaelli [this message]
2025-09-22 20:43 ` [RFC] arm64: dts: freescale: imx93-var-som: Align dts adding missing components Fabio Estevam
2025-09-22 20:47 ` 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=aNF1KOCs0eHL1Njb@Lord-Beerus \
--to=stefano.radaelli21@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/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