From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linusw@kernel.org, brgl@kernel.org,
linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Subject: Re: [PATCH] pinctrl: renesas: rzg2l: Add GPIO set_config
Date: Mon, 16 Mar 2026 12:19:05 +0200 [thread overview]
Message-ID: <2772d5e1-2127-4808-bd9d-aa40b4ad7104@tuxon.dev> (raw)
In-Reply-To: <CAMuHMdWv1dQ55NcwMga_X0G8K97RgMRXoDu_FV10fNQv7AadbA@mail.gmail.com>
Hi, Geert,
On 3/13/26 15:15, Geert Uytterhoeven wrote:
> Hi Claudiu,
>
> On Wed, 18 Feb 2026 at 16:19, Claudiu <claudiu.beznea@tuxon.dev> wrote:
>> From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>>
>> Add GPIO set_config to allow setting GPIO specific functionalities.
>>
>> Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>
> Thanks for your patch!
>
>> --- a/drivers/pinctrl/renesas/pinctrl-rzg2l.c
>> +++ b/drivers/pinctrl/renesas/pinctrl-rzg2l.c
>> @@ -1848,6 +1848,25 @@ static void rzg2l_gpio_free(struct gpio_chip *chip, unsigned int offset)
>> rzg2l_gpio_direction_input(chip, offset);
>> }
>>
>> +static int rzg2l_gpio_set_config(struct gpio_chip *chip, unsigned int offset,
>> + unsigned long config)
>> +{
>> + switch (pinconf_to_config_param(config)) {
>> + case PIN_CONFIG_BIAS_DISABLE:
>> + case PIN_CONFIG_BIAS_PULL_UP:
>> + case PIN_CONFIG_BIAS_PULL_DOWN:
>> + case PIN_CONFIG_DRIVE_OPEN_DRAIN:
>> + case PIN_CONFIG_DRIVE_PUSH_PULL:
>> + case PIN_CONFIG_SLEW_RATE:
>> + case PIN_CONFIG_DRIVE_STRENGTH:
>> + case PIN_CONFIG_DRIVE_STRENGTH_UA:
>> + case PIN_CONFIG_POWER_SOURCE:
>
> Shouldn't you handle all types that are supported by
> rzg2l_pinctrl_pinconf_[gs]et()?
>
> The following are missing:
> PIN_CONFIG_INPUT_ENABLE
> PIN_CONFIG_OUTPUT_ENABLE
> PIN_CONFIG_OUTPUT_IMPEDANCE_OHMS
> PIN_CONFIG_INPUT_SCHMITT_ENABLE
> RENESAS_RZV2H_PIN_CONFIG_OUTPUT_IMPEDANCE
I'll add these as well.
Thank you for your review,
Claudiu
next prev parent reply other threads:[~2026-03-16 10:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 15:19 Claudiu
2026-02-19 9:21 ` Bartosz Golaszewski
2026-02-19 19:04 ` Lad, Prabhakar
2026-02-24 9:08 ` Linus Walleij
2026-03-13 13:15 ` Geert Uytterhoeven
2026-03-16 10:19 ` claudiu beznea [this message]
2026-03-24 17:28 ` Geert Uytterhoeven
2026-03-24 19:02 ` Geert Uytterhoeven
2026-03-25 10:48 ` 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=2772d5e1-2127-4808-bd9d-aa40b4ad7104@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=brgl@kernel.org \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=geert@linux-m68k.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.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
all inboxes | Powered by JetHome®