[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<TY3PR01MB11346F52C1E32C9960436561A86D7A@TY3PR01MB11346.jpnprd01.prod.outlook.com>
Date: Wed, 19 Nov 2025 07:17:05 +0000
From: Biju Das <biju.das.jz@...renesas.com>
To: wsa+renesas <wsa+renesas@...g-engineering.com>, Tommaso Merciai
<tommaso.merciai.xr@...renesas.com>
CC: Tommaso Merciai <tomm.merciai@...il.com>,
"linux-renesas-soc@...r.kernel.org" <linux-renesas-soc@...r.kernel.org>,
Geert Uytterhoeven <geert+renesas@...der.be>, magnus.damm
<magnus.damm@...il.com>, Rob Herring <robh@...nel.org>, Krzysztof Kozlowski
<krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 2/2] arm64: dts: renesas: r9a09g047e57-smarc: Add overlay
for P3T1085UK-ARD
Hi Wolfram Sang, Tommasso,
> -----Original Message-----
> From: Wolfram Sang <wsa+renesas@...g-engineering.com>
> Sent: 19 November 2025 06:13
> Subject: Re: [PATCH 2/2] arm64: dts: renesas: r9a09g047e57-smarc: Add overlay for P3T1085UK-ARD
>
>
> > Your suggestion is to keep only Patch 1/2 dropping alias line right?
>
> Yes.
When using I3C in I²C-compatible mode, my understanding is that on Linux you need to
select different drivers via the device tree. However, from an application perspective,
an I²C-based Linux application should interact in the same way whether it's controlling
I3C in I²C mode or RIIC. Is that correct?
The whole idea of the Linux HAL is to provide a unified interface for I²C communication
to ensure software portability. If that is the case, if we are using i3c as i2c which
alias it will be assigned? The next unused one. It will change if we define another
alias for normal i2c.
For eg: we have 9 i2c channels and board dts at the moment
defines only 2.
i2c0 = &i2c0;
i2c2 = &i2c2;
Cheers,
Biju
Powered by blists - more mailing lists