From: wsa+renesas <wsa+renesas@sang-engineering.com>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>,
Tommaso Merciai <tomm.merciai@gmail.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
"magnus.damm" <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] arm64: dts: renesas: r9a09g047e57-smarc: Add overlay for P3T1085UK-ARD
Date: Wed, 19 Nov 2025 20:43:10 +0100 [thread overview]
Message-ID: <aR4dzmzDoo6lDQUL@shikoro> (raw)
In-Reply-To: <TY3PR01MB11346F52C1E32C9960436561A86D7A@TY3PR01MB11346.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 267 bytes --]
> 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.
Yes. Bus numbers are not stable. Udev rules should help you here.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-11-19 19:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 14:26 [PATCH 0/2] arm64: dts: renesas: r9a09g047e57-smarc: Enable I3C Tommaso Merciai
2025-11-18 14:26 ` [PATCH 1/2] arm64: dts: renesas: rzg3e-smarc-som: Add I3C support Tommaso Merciai
2025-11-18 16:34 ` Wolfram Sang
2025-11-18 22:19 ` Tommaso Merciai
2025-11-18 14:26 ` [PATCH 2/2] arm64: dts: renesas: r9a09g047e57-smarc: Add overlay for P3T1085UK-ARD Tommaso Merciai
2025-11-18 16:43 ` Wolfram Sang
2025-11-18 22:28 ` Tommaso Merciai
2025-11-19 6:12 ` Wolfram Sang
2025-11-19 7:17 ` Biju Das
2025-11-19 19:43 ` wsa+renesas [this message]
2025-11-20 11:07 ` Tommaso Merciai
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=aR4dzmzDoo6lDQUL@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
--cc=tomm.merciai@gmail.com \
--cc=tommaso.merciai.xr@bp.renesas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.