From: Wolfram Sang <wsa+renesas@sang-engineering.com>
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 2/2] arm64: dt: imx95: Add TQMa95xxSA
Date: Tue, 29 Apr 2025 08:40:33 +0200 [thread overview]
Message-ID: <aBB0Ydxwn2CM_uu5@shikoro> (raw)
In-Reply-To: <2436245.ElGaqSPkdT@steina-w>
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
> renesas-soc gets triggered ;-) I'll pay attention for further patches.
No need from my side. I just wondered and can live with what
get_maintainers provides or I would fix MAINTAINERS myself.
> This is a SMARC-2 module, but there is no i3c interface in this standard.
I have a SMARC2 module where the I3C connector is placed on the SoC
board. I guess SMARC2-AFB could be used as an alternative, too? Anyhow,
I was just interested in other easily accessible I3C controllers, so
thanks for your heads up, even if no cigar here.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-04-29 6:42 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 [this message]
2025-04-28 16:50 ` [PATCH v2 1/2] dt: bindings: arm: add bindings for TQMa95xxSA Conor Dooley
2025-05-09 14:32 ` 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=aBB0Ydxwn2CM_uu5@shikoro \
--to=wsa+renesas@sang-engineering.com \
--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;
as well as URLs for NNTP newsgroup(s).