From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH 2/2] pinctrl: renesas: rzg2l: Improve rzg2l_gpio_register()
Date: Mon, 7 Feb 2022 15:33:48 +0100 [thread overview]
Message-ID: <CAMuHMdWy2aF2hjSQbBtXi0ot2LOutwD0Rm2ecaTExeGhVS73DA@mail.gmail.com> (raw)
In-Reply-To: <20220206194614.13209-2-biju.das.jz@bp.renesas.com>
On Sun, Feb 6, 2022 at 8:46 PM Biju Das <biju.das.jz@bp.renesas.com> wrote:
> Update rzg2l_gpio_register() to use driver data for chip->names
> and check for gpio-range. This allows reusing the driver for
> SoC's with different port pin definitions(eg:- RZ/G2UL SoC has
> fewer ports compared to RZ/G2L and port pin definitions are
> different).
>
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
i.e. will queue in renesas-pinctrl-for-v5.18.
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
next prev parent reply other threads:[~2022-02-07 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 19:46 [PATCH 1/2] pinctrl: renesas: Kconfig: Update description for RZ/V2L pin control support Biju Das
2022-02-06 19:46 ` [PATCH 2/2] pinctrl: renesas: rzg2l: Improve rzg2l_gpio_register() Biju Das
2022-02-07 14:33 ` Geert Uytterhoeven [this message]
2022-02-07 14:30 ` [PATCH 1/2] pinctrl: renesas: Kconfig: Update description for RZ/V2L pin control support Geert Uytterhoeven
2022-02-07 14:36 ` Biju Das
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=CAMuHMdWy2aF2hjSQbBtXi0ot2LOutwD0Rm2ecaTExeGhVS73DA@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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;
as well as URLs for NNTP newsgroup(s).