From: Yoshihiro Kaneko <ykaneko0929@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH/RFT] pinctrl: sh-pfc: r8a77990: Add DRIF pins, groups and functions
Date: Fri, 25 Jan 2019 02:26:03 +0900 [thread overview]
Message-ID: <CAH1o70JnSx_X+e4fridbAd31bDjLbOhvF7diK39qckFcSLTO4Q@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdVcXjeOGr-Xtvhyi5G2d7Y4Gi-raBPK+Qja02-KxBE0wQ@mail.gmail.com>
Hi Geert-san,
Thanks for your review!
2019年1月17日(木) 1:38 Geert Uytterhoeven <geert@linux-m68k.org>:
>
> Hi Kaneko-san,
>
> On Tue, Jan 15, 2019 at 1:01 PM Yoshihiro Kaneko <ykaneko0929@gmail.com> wrote:
> > From: Takeshi Kihara <takeshi.kihara.df@renesas.com>
> >
> > This patch adds DRIF{0,1,2,3} pins, groups and functions to the R8A77990
> > SoC.
> >
> > Signed-off-by: Takeshi Kihara <takeshi.kihara.df@renesas.com>
> > Signed-off-by: Yoshihiro Kaneko <ykaneko0929@gmail.com>
>
> Thanks for your patch!
>
> > --- a/drivers/pinctrl/sh-pfc/pfc-r8a77990.c
> > +++ b/drivers/pinctrl/sh-pfc/pfc-r8a77990.c
>
> > @@ -3523,7 +3716,7 @@ enum {
> > };
> >
> > static const struct {
> > - struct sh_pfc_pin_group common[241];
> > + struct sh_pfc_pin_group common[262];
> > struct sh_pfc_pin_group automotive[2];
> > } pinmux_groups = {
> > .common = {
> > @@ -3555,6 +3748,27 @@ enum {
> > SH_PFC_PIN_GROUP(can0_data),
> > SH_PFC_PIN_GROUP(can1_data),
> > SH_PFC_PIN_GROUP(can_clk),
> > + SH_PFC_PIN_GROUP(drif0_ctrl_a),
> > + SH_PFC_PIN_GROUP(drif0_data0_a),
> > + SH_PFC_PIN_GROUP(drif0_data1_a),
> > + SH_PFC_PIN_GROUP(drif0_ctrl_b),
> > + SH_PFC_PIN_GROUP(drif0_data0_b),
> > + SH_PFC_PIN_GROUP(drif0_data1_b),
> > + SH_PFC_PIN_GROUP(drif1_ctrl),
> > + SH_PFC_PIN_GROUP(drif1_data0),
> > + SH_PFC_PIN_GROUP(drif1_data1),
> > + SH_PFC_PIN_GROUP(drif2_ctrl_a),
> > + SH_PFC_PIN_GROUP(drif2_data0_a),
> > + SH_PFC_PIN_GROUP(drif2_data1_a),
> > + SH_PFC_PIN_GROUP(drif2_ctrl_b),
> > + SH_PFC_PIN_GROUP(drif2_data0_b),
> > + SH_PFC_PIN_GROUP(drif2_data1_b),
> > + SH_PFC_PIN_GROUP(drif3_ctrl_a),
> > + SH_PFC_PIN_GROUP(drif3_data0_a),
> > + SH_PFC_PIN_GROUP(drif3_data1_a),
> > + SH_PFC_PIN_GROUP(drif3_ctrl_b),
> > + SH_PFC_PIN_GROUP(drif3_data0_b),
> > + SH_PFC_PIN_GROUP(drif3_data1_b),
>
> As RZ/G2E (r8a774c0) does not have the DRIF modules, the DRIF pin groups
> should be added to the automotive section, instead of the common section.
I will do that.
>
> > SH_PFC_PIN_GROUP(du_rgb666),
> > SH_PFC_PIN_GROUP(du_rgb888),
> > SH_PFC_PIN_GROUP(du_clk_in_0),
>
> > @@ -4157,7 +4404,7 @@ enum {
> > };
> >
> > static const struct {
> > - struct sh_pfc_function common[44];
> > + struct sh_pfc_function common[48];
> > struct sh_pfc_function automotive[2];
> > } pinmux_functions = {
> > .common = {
> > @@ -4166,6 +4413,10 @@ enum {
> > SH_PFC_FUNCTION(can0),
> > SH_PFC_FUNCTION(can1),
> > SH_PFC_FUNCTION(can_clk),
> > + SH_PFC_FUNCTION(drif0),
> > + SH_PFC_FUNCTION(drif1),
> > + SH_PFC_FUNCTION(drif2),
> > + SH_PFC_FUNCTION(drif3),
>
> Likewise for the DRIF pin functions.
Likewise.
>
> > SH_PFC_FUNCTION(du),
> > SH_PFC_FUNCTION(hscif0),
> > SH_PFC_FUNCTION(hscif1),
>
> The rest looks good to me, so with the above fixed:
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> 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
Best regards,
Kaneko
prev parent reply other threads:[~2019-01-24 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 12:01 [PATCH/RFT] pinctrl: sh-pfc: r8a77990: Add DRIF pins, groups and functions Yoshihiro Kaneko
2019-01-16 16:38 ` Geert Uytterhoeven
2019-01-24 17:26 ` Yoshihiro Kaneko [this message]
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=CAH1o70JnSx_X+e4fridbAd31bDjLbOhvF7diK39qckFcSLTO4Q@mail.gmail.com \
--to=ykaneko0929@gmail.com \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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).