From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Claudiu Beznea <claudiu.beznea@kernel.org>
Cc: geert+renesas@glider.be, linusw@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, magnus.damm@gmail.com,
prabhakar.mahadev-lad.rj@bp.renesas.com,
claudiu.beznea@tuxon.dev, linux-renesas-soc@vger.kernel.org,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Subject: Re: [PATCH v2 6/7] pinctrl: renesas: rzg2l: Add RZ/G3S support for selecting the I3C power source
Date: Thu, 28 May 2026 13:24:17 +0200 [thread overview]
Message-ID: <ahgl4aH8xm2X5wwV@shikoro> (raw)
In-Reply-To: <20260528080439.615958-7-claudiu.beznea@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
On Thu, May 28, 2026 at 11:04:38AM +0300, Claudiu Beznea wrote:
> From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>
> The Renesas RZ/G3S I3C pins can be powered at either 1.8V or 1.2V. The
> pin controller provides a register to select between these two options.
> Update the Renesas RZ/G2L pin controller driver to allow selecting the
> I3C power source on RZ/G3S SoC.
>
> Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
I am not a super-expert of this driver, but this implementation looks
reasonable to me.
Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-05-28 11:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 8:04 [PATCH v2 0/7] pinctrl: renesas: rzg2l: Add support for RZ/G3S I3C Claudiu Beznea
2026-05-28 8:04 ` [PATCH v2 1/7] pinctrl: renesas: rzg2l: Generalize the power source code Claudiu Beznea
2026-05-28 8:48 ` sashiko-bot
2026-05-28 8:04 ` [PATCH v2 2/7] pinctrl: renesas: rzg2l: Drop defines present in struct rzg2l_hwcfg Claudiu Beznea
2026-05-28 8:16 ` Biju Das
2026-05-28 8:46 ` Claudiu Beznea
2026-05-28 8:54 ` Biju Das
2026-05-28 11:20 ` Wolfram Sang
2026-05-28 8:04 ` [PATCH v2 3/7] pinctrl: renesas: rzg2l: Keep member documentation aligned Claudiu Beznea
2026-05-28 11:21 ` Wolfram Sang
2026-05-28 8:04 ` [PATCH v2 4/7] pinctrl: renesas: rzg2l: Use tab instead of spaces Claudiu Beznea
2026-05-28 11:23 ` Wolfram Sang
2026-05-28 8:04 ` [PATCH v2 5/7] dt-bindings: pinctrl: renesas,rzg2l-pinctrl: Document the missing I3C power source option Claudiu Beznea
2026-05-28 11:23 ` Wolfram Sang
2026-05-28 8:04 ` [PATCH v2 6/7] pinctrl: renesas: rzg2l: Add RZ/G3S support for selecting the I3C power source Claudiu Beznea
2026-05-28 11:24 ` Wolfram Sang [this message]
2026-05-28 8:04 ` [PATCH v2 7/7] arm64: dts: renesas: rzg3s-smarc-som: Enable I3C Claudiu Beznea
2026-05-28 11:25 ` Wolfram Sang
2026-05-28 8:15 ` [PATCH v2 0/7] pinctrl: renesas: rzg2l: Add support for RZ/G3S I3C Claudiu Beznea
2026-05-28 11:34 ` Wolfram Sang
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=ahgl4aH8xm2X5wwV@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=claudiu.beznea@kernel.org \
--cc=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=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@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