From: Claudiu Beznea <claudiu.beznea@tuxon.dev>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-renesas-soc@vger.kernel.org
Cc: 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
Subject: Re: [PATCH] arm64: dts: renesas: rzg3s-smarc: Enable I2C1 and connected power monitor
Date: Wed, 4 Dec 2024 18:30:18 +0200 [thread overview]
Message-ID: <1b691ff5-2240-4eba-bc3a-b33193ba0630@tuxon.dev> (raw)
In-Reply-To: <20241120085345.24638-2-wsa+renesas@sang-engineering.com>
Hi, Wolfram,
On 20.11.2024 10:49, Wolfram Sang wrote:
> Enable I2C1 for the carrier board and the connected power monitor
> ISL28022. Limit the bus speed to the maximum the power monitor supports.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
>
> i2c1 gets enabled in the current SoM-DTSI as well, but to be safe
> regarding other SoM DTSIs to come, I opted for explicitly enabling it in
> the carrier board as well.
>
> I picked the 'average-samples' value using my gut feeling. If someone
> has a reason to pick a better one, I am all for it.
>
> arch/arm64/boot/dts/renesas/rzg3s-smarc.dtsi | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/renesas/rzg3s-smarc.dtsi b/arch/arm64/boot/dts/renesas/rzg3s-smarc.dtsi
> index 7945d44e6ee1..5e4bfaeafd20 100644
> --- a/arch/arm64/boot/dts/renesas/rzg3s-smarc.dtsi
> +++ b/arch/arm64/boot/dts/renesas/rzg3s-smarc.dtsi
> @@ -73,6 +73,19 @@ &i2c0 {
> clock-frequency = <1000000>;
> };
>
> +&i2c1 {
> + status = "okay";
> +
> + clock-frequency = <400000>;
This could be moved before status to comply with [1]. I can take care of it
later as I failed to follow [1] for i2c0 as well.
Other than this:
Reviewed-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
I gave it a try on RZ/G3S:
Tested-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Thank you,
Claudiu
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Documentation/devicetree/bindings/dts-coding-style.rst#n112
> +
> + power-monitor@44 {
> + compatible = "renesas,isl28022";
> + reg = <0x44>;
> + shunt-resistor-micro-ohms = <8000>;
> + renesas,average-samples = <32>;
> + };
> +};
> +
> &pinctrl {
> key-1-gpio-hog {
> gpio-hog;
prev parent reply other threads:[~2024-12-04 16:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 8:49 [PATCH] arm64: dts: renesas: rzg3s-smarc: Enable I2C1 and connected power monitor Wolfram Sang
2024-11-20 9:10 ` Biju Das
2024-11-20 9:13 ` Wolfram Sang
2024-11-20 9:16 ` Geert Uytterhoeven
2024-11-20 9:13 ` Wolfram Sang
2024-11-20 9:24 ` Biju Das
2024-11-27 14:15 ` Geert Uytterhoeven
2024-12-04 16:30 ` Claudiu Beznea [this message]
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=1b691ff5-2240-4eba-bc3a-b33193ba0630@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
--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