From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 02/13] sh-pfc: r8a73a4: Support sparse GPIO numbers
Date: Tue, 26 Mar 2013 15:52:40 +0000 [thread overview]
Message-ID: <2838812.HaWCubMcGG@avalon> (raw)
In-Reply-To: <20130326134959.31366.93833.sendpatchset@w520>
Hi Magnus,
Thanks for the patch.
On Tuesday 26 March 2013 22:49:59 Magnus Damm wrote:
> From: Magnus Damm <damm@opensource.se>
>
> The r8a73a4 SoC has sparse GPIO numbers. Declare ranges for
> pin numbers in the PFC SoC data. Pin numbers shall be used
> with the GPIO API from this point on.
>
> Signed-off-by: Magnus Damm <damm@opensource.se>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
>
> arch/arm/mach-shmobile/include/mach/r8a73a4.h | 2 +-
> drivers/pinctrl/sh-pfc/pfc-r8a73a4.c | 16 ++++++++++++++++
> 2 files changed, 17 insertions(+), 1 deletion(-)
>
> --- 0007/arch/arm/mach-shmobile/include/mach/r8a73a4.h
> +++ work/arch/arm/mach-shmobile/include/mach/r8a73a4.h 2013-03-26
> 20:20:54.000000000 +0900 @@ -86,7 +86,7 @@ enum {
> GPIO_PORT325, GPIO_PORT326, GPIO_PORT327, GPIO_PORT328, GPIO_PORT329,
>
> /* Port0 */
> - GPIO_FN_LCDD0,
> + GPIO_FN_LCDD0 = 330,
> GPIO_FN_PDM2_CLK_0,
> GPIO_FN_DU0_DR0,
> GPIO_FN_IRQ0,
> --- 0007/drivers/pinctrl/sh-pfc/pfc-r8a73a4.c
> +++ work/drivers/pinctrl/sh-pfc/pfc-r8a73a4.c 2013-03-26
21:12:07.000000000
> +0900 @@ -1424,6 +1424,20 @@ static struct sh_pfc_pin pinmux_pins[] > GPIO_PORT_ALL(),
> };
>
> +static const struct pinmux_range pinmux_ranges[] = {
> + {.begin = 0, .end = 30,},
> + {.begin = 32, .end = 40,},
> + {.begin = 64, .end = 85,},
> + {.begin = 96, .end = 126,},
> + {.begin = 128, .end = 134,},
> + {.begin = 160, .end = 178,},
> + {.begin = 192, .end = 222,},
> + {.begin = 224, .end = 250,},
> + {.begin = 256, .end = 283,},
> + {.begin = 288, .end = 308,},
> + {.begin = 320, .end = 329,},
> +};
I wonder whether it wouldn't be a better idea to add the pin number to the
sh_pfc_pin structure and compute the ranges array at runtime. Pin numbers
would be hidden in the GPIO_PORT_ALL() macro. What's your opinion ?
I'm of course not asking you to implement that solution, your patch is fine as
it is.
> +
> #define PINMUX_FN_BASE ARRAY_SIZE(pinmux_pins)
>
> static const struct pinmux_func pinmux_func_gpios[] = {
> @@ -2815,6 +2829,8 @@ const struct sh_pfc_soc_info r8a73a4_pin
>
> .pins = pinmux_pins,
> .nr_pins = ARRAY_SIZE(pinmux_pins),
> + .ranges = pinmux_ranges,
> + .nr_ranges = ARRAY_SIZE(pinmux_ranges),
> .func_gpios = pinmux_func_gpios,
> .nr_func_gpios = ARRAY_SIZE(pinmux_func_gpios),
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-03-26 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 13:49 [PATCH 02/13] sh-pfc: r8a73a4: Support sparse GPIO numbers Magnus Damm
2013-03-26 15:52 ` Laurent Pinchart [this message]
2013-03-27 16:44 ` Magnus Damm
2013-03-27 17:20 ` Linus Walleij
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=2838812.HaWCubMcGG@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@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;
as well as URLs for NNTP newsgroup(s).