From: Conor Dooley <conor@kernel.org>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux@ew.tq-group.com, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt: bindings: arm: add bindings for TQMa95xxSA
Date: Mon, 28 Apr 2025 17:50:49 +0100 [thread overview]
Message-ID: <20250428-scalding-coffee-70507d952247@spud> (raw)
In-Reply-To: <20250428135915.520432-1-alexander.stein@ew.tq-group.com>
[-- Attachment #1: Type: text/plain, Size: 1587 bytes --]
On Mon, Apr 28, 2025 at 03:59:08PM +0200, Alexander Stein wrote:
> TQMa95xxSA is a SOM using NXP i.MX95 CPU. MB-SMARC-2 is a carrier
> reference design.
>
> [1] https://www.tq-group.com/en/products/tq-embedded/arm-architecture/tqma95xxsa/
>
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> Changes in v2:
> * None
>
> Documentation/devicetree/bindings/arm/fsl.yaml | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml b/Documentation/devicetree/bindings/arm/fsl.yaml
> index 447054b52ea39..a6cf65e10d43f 100644
> --- a/Documentation/devicetree/bindings/arm/fsl.yaml
> +++ b/Documentation/devicetree/bindings/arm/fsl.yaml
> @@ -1419,6 +1419,16 @@ properties:
> - const: kontron,imx93-osm-s # Kontron OSM-S i.MX93 SoM
> - const: fsl,imx93
>
> + - description:
> + TQMa95xxSA is a series of SOM featuring NXP i.MX95 SoC variants.
> + It has the SMARC form factor and is designed to be placed on
> + different carrier boards. MB-SMARC-2 is a carrier reference design.
> + items:
> + - enum:
> + - tq,imx95-tqma9596sa-mb-smarc-2 # TQ-Systems GmbH i.MX95 TQMa95xxSA SOM on MB-SMARC-2
> + - const: tq,imx95-tqma9596sa # TQ-Systems GmbH i.MX95 TQMa95xxSA SOM
> + - const: fsl,imx95
> +
> - description:
> Freescale Vybrid Platform Device Tree Bindings
>
> --
> 2.43.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-04-28 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 13:59 [PATCH v2 1/2] dt: bindings: arm: add bindings for TQMa95xxSA Alexander Stein
2025-04-28 13:59 ` [PATCH v2 2/2] arm64: dt: imx95: Add TQMa95xxSA Alexander Stein
2025-04-28 16:47 ` Wolfram Sang
2025-04-29 5:52 ` Alexander Stein
2025-04-29 6:40 ` Wolfram Sang
2025-04-28 16:50 ` Conor Dooley [this message]
2025-05-09 14:32 ` [PATCH v2 1/2] dt: bindings: arm: add bindings for TQMa95xxSA Shawn Guo
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=20250428-scalding-coffee-70507d952247@spud \
--to=conor@kernel.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=geert+renesas@glider.be \
--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=linux-renesas-soc@vger.kernel.org \
--cc=linux@ew.tq-group.com \
--cc=magnus.damm@gmail.com \
--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