From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Linus Walleij <linus.walleij@linaro.org>,
Simon Horman <horms@verge.net.au>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>
Subject: Re: [RFC PATCH 2/2] pinctrl: sh-pfc: r8a7791: Add can_clk function
Date: Mon, 13 Nov 2017 13:17:59 +0100 [thread overview]
Message-ID: <CAMuHMdVLAdyrqecJmn09qLBY5=vA7YY-Opu79SvaDNdLp5DXtA@mail.gmail.com> (raw)
In-Reply-To: <1510334189-8942-3-git-send-email-fabrizio.castro@bp.renesas.com>
Hi Fabrizio,
On Fri, Nov 10, 2017 at 6:16 PM, Fabrizio Castro
<fabrizio.castro@bp.renesas.com> wrote:
> This patch adds can_clk function to r8a7743/r8a7791 which is cleaner,
> as it reduces duplication, and allows for independent configuration.
>
> Signed-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
> Reviewed-by: Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>
Thanks for your patch!
> --- a/drivers/pinctrl/sh-pfc/pfc-r8a7791.c
> +++ b/drivers/pinctrl/sh-pfc/pfc-r8a7791.c
> @@ -4826,10 +4826,6 @@ static const char * const can0_groups[] = {
> "can0_data_d",
> "can0_data_e",
> "can0_data_f",
> - "can_clk",
> - "can_clk_b",
> - "can_clk_c",
> - "can_clk_d",
As the pin groups and functions are part of the stable DT ABI, you cannot just
remove the can_clk* pins from can0_groups[], as that would break existing users.
I would keep them, but add a comment "/* retained for backwards
compatibility */".
> };
>
> static const char * const can1_groups[] = {
> @@ -4837,6 +4833,9 @@ static const char * const can1_groups[] = {
> "can1_data_b",
> "can1_data_c",
> "can1_data_d",
Likewise.
> +};
> +
> +static const char * const can_clk_groups[] = {
> "can_clk",
> "can_clk_b",
> "can_clk_c",
Adding a new can_clk_groups[] ...
> @@ -5308,7 +5307,7 @@ static const char * const vin2_groups[] = {
> };
>
> static const struct {
> - struct sh_pfc_function common[56];
> + struct sh_pfc_function common[57];
> struct sh_pfc_function r8a779x[2];
> } pinmux_functions = {
> .common = {
> @@ -5316,6 +5315,7 @@ static const struct {
> SH_PFC_FUNCTION(avb),
> SH_PFC_FUNCTION(can0),
> SH_PFC_FUNCTION(can1),
> + SH_PFC_FUNCTION(can_clk),
and can_clk function is OK, though.
> SH_PFC_FUNCTION(du),
> SH_PFC_FUNCTION(du0),
> SH_PFC_FUNCTION(du1),
My comments apply to your r8a7794 patch, too. Except that on r8a7794 we
didn't have CAN support in pfc-r8a7794.c before, but I would like to treat all
R-Car Gen2 and RZ/G1 SoCs in the same way.
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:[~2017-11-13 12:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 15:10 [PATCH 0/8] Add CAN support to iwg2[02]d Fabrizio Castro
2017-11-07 15:10 ` [PATCH 2/8] pinctrl: sh-pfc: r8a7745: Add CAN[01] support Fabrizio Castro
2017-11-10 10:00 ` Geert Uytterhoeven
2017-11-10 17:16 ` [RFC PATCH 0/2] Add can_clk function Fabrizio Castro
2017-11-10 17:16 ` [RFC PATCH 1/2] pinctrl: sh-pfc: r8a7794: " Fabrizio Castro
2017-11-10 17:16 ` [RFC PATCH 2/2] pinctrl: sh-pfc: r8a7791: " Fabrizio Castro
2017-11-13 12:17 ` Geert Uytterhoeven [this message]
2017-11-14 15:40 ` Fabrizio Castro
2017-11-20 10:07 ` [PATCH 0/8] Add CAN support to iwg2[02]d Simon Horman
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='CAMuHMdVLAdyrqecJmn09qLBY5=vA7YY-Opu79SvaDNdLp5DXtA@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=ramesh.shanmugasundaram@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).