From: Claudiu Beznea <claudiu.beznea@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
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 1/7] pinctrl: renesas: rzg2l: Generalize the power source code
Date: Wed, 3 Jun 2026 11:19:33 +0300 [thread overview]
Message-ID: <096df078-1027-44f2-b02c-c0a27b646a87@kernel.org> (raw)
In-Reply-To: <ah9BkQjUKwZ9KXMH@ninjato>
On 6/2/26 23:48, Wolfram Sang wrote:
> On Thu, May 28, 2026 at 11:04:33AM +0300, Claudiu Beznea wrote:
>> From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>>
>> The current functions used to get/set the pin power source check the
>> OTHER_POC register, which is specific to the RZ/G3L SoC only. To allow the
>> code to be extended for other power source functionalities (e.g. I3C on
>> RZ/G3S), generalize the functions used to get/set the pin power source.
>>
>> For this, introduce the struct rzg2l_register_masks data structure whose
>> purpose is to store SoC specific register bit masks. The members of this
>> structure are then used in rzg2l_caps_to_pwr_reg() to retrieve the bitmask
>> corresponding to a SoC specific power source capability.
>>
>> The conversion between HW specific power source values and SW specific
>> power source values is now handled through rzg2l_pwr_reg_val_to_ps() and
>> rzg2l_ps_to_pwr_reg_val().
>>
>> Finally, to keep the code generic, the register update in
>> rzg2l_set_power_source() was changed to a read-modify-write approach to
>> cover all cases.
>>
>> Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>
> Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
>
> Have you seen the comment from Sashiko about this patch? Doesn't sound
> entirely wrong to me...
Indeed, that should be fixed. I'll add a fix patch in the next version.
Thank you for testing this,
Claudiu
next prev parent reply other threads:[~2026-06-03 8:19 UTC|newest]
Thread overview: 28+ 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-06-02 20:48 ` Wolfram Sang
2026-06-03 8:19 ` Claudiu Beznea [this message]
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-06-02 20:49 ` 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
2026-06-02 20:50 ` Wolfram Sang
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-06-02 20:53 ` 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
2026-06-02 11:35 ` Wolfram Sang
2026-06-02 12:48 ` Claudiu Beznea
2026-06-02 20:56 ` Wolfram Sang
2026-06-02 13:39 ` Claudiu Beznea
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=096df078-1027-44f2-b02c-c0a27b646a87@kernel.org \
--to=claudiu.beznea@kernel.org \
--cc=claudiu.beznea.uj@bp.renesas.com \
--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 \
--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
Powered by JetHome