linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Paul Barker <paul.barker.ct@bp.renesas.com>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 Linus Walleij <linus.walleij@linaro.org>,
	linux-renesas-soc@vger.kernel.org,  devicetree@vger.kernel.org,
	linux-gpio@vger.kernel.org,  linux-kernel@vger.kernel.org,  "Lad,
	Prabhakar" <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH 2/9] pinctrl: renesas: rzg2l: Refactor pin to OEN bit translation
Date: Thu, 30 May 2024 14:51:23 +0200	[thread overview]
Message-ID: <CAMuHMdUJsNBw7oYyEYLfyN4JohPGD0ONMv2zrhy3U4MUV4MzQA@mail.gmail.com> (raw)
In-Reply-To: <20240524094603.988-3-paul.barker.ct@bp.renesas.com>

Hi Paul,

On Fri, May 24, 2024 at 11:46 AM Paul Barker
<paul.barker.ct@bp.renesas.com> wrote:
> We currently support setting OEN (Output ENable) bits only for the
> RZ/G3S SoC and so the functions rzg2l_oen_is_supported() and
> rzg2l_pin_to_oen_bit() are hardcoded for the RZ/G3S. To prepare for
> supporting OEN on SoCs in the RZ/G2L family, we need to make this code
> more flexible.
>
> So, the rzg2l_oen_is_supported() and rzg2l_pin_to_oen_bit() functions
> are replaced with a single translation function which is called via a
> pin_to_oen_bit function pointer and returns an error code if OEN is not
> supported for the given pin.
>
> Signed-off-by: Paul Barker <paul.barker.ct@bp.renesas.com>

Thanks for your patch!

> --- a/drivers/pinctrl/renesas/pinctrl-rzg2l.c
> +++ b/drivers/pinctrl/renesas/pinctrl-rzg2l.c
> @@ -256,6 +256,8 @@ struct rzg2l_pinctrl_data {
>         const struct rzg2l_hwcfg *hwcfg;
>         const struct rzg2l_variable_pin_cfg *variable_pin_cfg;
>         unsigned int n_variable_pin_cfg;
> +       int (*pin_to_oen_bit)(const struct rzg2l_hwcfg *hwcfg,
> +                             u32 caps, u32 offset, u8 pin);
>  };

This definitely needs synchronization with Prabhakar, as he introduces
a different set of function pointers to distinguish RZ/G2L (G3S) and
RZ/V2H.  We really like to end up with something that is consistent,
and works for all.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2024-05-30 12:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24  9:45 [PATCH 0/9] Configure GbEth for RGMII on RZ/G2L family Paul Barker
2024-05-24  9:45 ` [PATCH 1/9] pinctrl: renesas: rzg2l: Fix variable names in OEN functions Paul Barker
2024-05-30 12:47   ` Geert Uytterhoeven
2024-05-24  9:45 ` [PATCH 2/9] pinctrl: renesas: rzg2l: Refactor pin to OEN bit translation Paul Barker
2024-05-30 12:51   ` Geert Uytterhoeven [this message]
2024-05-30 13:55     ` Paul Barker
2024-05-24  9:45 ` [PATCH 3/9] pinctrl: renesas: rzg2l: Support output enable on RZ/G2L Paul Barker
2024-05-30 13:13   ` Geert Uytterhoeven
2024-05-24  9:45 ` [PATCH 4/9] arm64: dts: renesas: rzg2l: Enable Ethernet TXC output Paul Barker
2024-05-30 13:40   ` Geert Uytterhoeven
2024-05-24  9:45 ` [PATCH 5/9] arm64: dts: renesas: rzg2lc: " Paul Barker
2024-05-30 13:47   ` Geert Uytterhoeven
2024-05-24  9:46 ` [PATCH 6/9] arm64: dts: renesas: rzg2ul: " Paul Barker
2024-05-30 13:50   ` Geert Uytterhoeven
2024-05-24  9:46 ` [PATCH 7/9] arm64: dts: renesas: rzg2l: Set Ethernet PVDD to 1.8V Paul Barker
2024-05-30 13:51   ` Geert Uytterhoeven
2024-05-24  9:46 ` [PATCH 8/9] arm64: dts: renesas: rzg2lc: " Paul Barker
2024-05-30 13:51   ` Geert Uytterhoeven
2024-05-24  9:46 ` [PATCH 9/9] arm64: dts: renesas: rzg2ul: " Paul Barker
2024-05-30 13:51   ` Geert Uytterhoeven

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=CAMuHMdUJsNBw7oYyEYLfyN4JohPGD0ONMv2zrhy3U4MUV4MzQA@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linus.walleij@linaro.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=paul.barker.ct@bp.renesas.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;
as well as URLs for NNTP newsgroup(s).