devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: tomm.merciai@gmail.com, linux-renesas-soc@vger.kernel.org,
	biju.das.jz@bp.renesas.com,
	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, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: renesas: r9a09g047e57-smarc: Add overlay for P3T1085UK-ARD
Date: Tue, 18 Nov 2025 23:28:34 +0100	[thread overview]
Message-ID: <aRzzEgeetDFlE3YC@tom-desktop> (raw)
In-Reply-To: <aRyiQJsu6gob3Gf9@shikoro>

Hi Wolfram,
Thank you for your review!

On Tue, Nov 18, 2025 at 05:43:44PM +0100, Wolfram Sang wrote:
> Hi Tommaso,
> 
> > +/*
> > + * #define I3C_BUS_MODE_PURE 1 (for I3C bus mode pure - default)
> > + * #define I3C_BUS_MODE_PURE 0 (for I3C bus mode mixed-fast)
> > + */
> > +#define I3C_BUS_MODE_PURE	1
> 
> Sorry, but I really think this is configuration and not hardware
> description. The board has only I3C capable devices, so unless you
> connect more devices externally, you can always use pure-i3c-mode.
> Enforcing mixed-mode is only for debugging.
> 
> > +
> > +#if I3C_BUS_MODE_PURE
> > +&i3c {
> > +	i2c-scl-hz = <400000>;
> > +	i3c-scl-hz = <12500000>;
> > +	status = "okay";
> > +};
> 
> So, the above is all that is needed. Which is the basic enablement for
> the I3C bus in general. I mean, auto-detecting devices is a key feature
> of I3C :) Which basically means IMHO that this overlay is superfluous.
> 
> 
> > +#else /* I3C_BUS_MODE_MIXED_FAST */
> > +&i3c {
> > +	status = "okay";
> > +
> > +	#address-cells = <1>;
> > +	#size-cells = <0>;
> > +
> > +	i2c-scl-hz = <400000>;
> > +	i3c-scl-hz = <12500000>;
> 
> Despite this else block being debug only...
> 
> > +
> > +	eeprom@1a {
> > +		compatible = "atmel,24c02";
> > +		reg = <0x1a 0 (I2C_FM | I2C_FILTER)>;
> > +	};
> 
> ... there is no device listening to 0x1a on this board? What do you see
> there? Did I forget something?

Ouch :'(
Sorry, my bad I forgot to remove this 0x1a (audio codec)
device from the bring-up/testing session.

> 
> > +
> > +	/* U2 */
> > +	temperature-sensor@48 {
> > +		compatible = "nxp,p3t1085";
> > +		reg = <0x48 0 (I2C_FM | I2C_FILTER)>;
> > +	};
> > +
> > +	/* U1 NOT MOUNTED as default */
> > +	temp-sense@4c {
> > +		status = "disabled";
> > +		compatible = "national,lm75";
> 
> Yes, mounting U1 is a hack I introduced. The compatible should be
> "nxp,p3t1755" BTW. But as said, the whole MIXED_MODE block is not
> hardware description, I'd say.

Ack, thanks.

Please correct me if I'm wrong.
Your suggestion is to keep only Patch 1/2 dropping alias line right?
Thanks in advance.

> 
> Happy hacking,
> 
>    Wolfram
> 

Kind Regards,
Tommaso



  reply	other threads:[~2025-11-18 22:28 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 [this message]
2025-11-19  6:12       ` Wolfram Sang
2025-11-19  7:17         ` Biju Das
2025-11-19 19:43           ` wsa+renesas
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=aRzzEgeetDFlE3YC@tom-desktop \
    --to=tommaso.merciai.xr@bp.renesas.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=wsa+renesas@sang-engineering.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 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).