From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/3 v3] sh-pfc: r8a7778: add common PFC macro helper
Date: Mon, 22 Apr 2013 10:06:26 +0000 [thread overview]
Message-ID: <3998361.LvOaInl8Ye@avalon> (raw)
In-Reply-To: <8738un6wwd.wl%kuninori.morimoto.gx@renesas.com>
Hi Morimoto-san,
On Thursday 18 April 2013 20:07:34 Kuninori Morimoto wrote:
> pfc-r8a7778 will have many devices pfc support in the future,
> and current pfc-r8a7778 is using pin/mux definition macro for SCIF.
> The device definition style using macro is readable code IMO,
> but creating new macro for each devices is not good sense.
> This patch adds common SH_PFC_xx() macro for each new feature devices
>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> ---
> v2 -> v3
>
> - new patch
>
> drivers/pinctrl/sh-pfc/pfc-r8a7778.c | 26 ++++++++++++++++++--------
> 1 file changed, 18 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/pinctrl/sh-pfc/pfc-r8a7778.c
> b/drivers/pinctrl/sh-pfc/pfc-r8a7778.c index ddbd27b..139f9dd 100644
> --- a/drivers/pinctrl/sh-pfc/pfc-r8a7778.c
> +++ b/drivers/pinctrl/sh-pfc/pfc-r8a7778.c
> @@ -1303,15 +1303,25 @@ static struct sh_pfc_pin pinmux_pins[] = {
> */
> #define PIN_NUMBER(row, col) (1000+((row)-1)*25+(col)-1)
>
> -/* - SCIF macro
> ------------------------------------------------------------- */ -#define
> SCIF_PFC_PIN(name, args...) \
> +/* - macro */
> +#define SH_PFC_PINS(name, args...) \
> static const unsigned int name ##_pins[] = { args }
> -#define SCIF_PFC_DAT(name, tx, rx) \
> - static const unsigned int name ##_mux[] = { tx##_MARK, rx##_MARK, }
> -#define SCIF_PFC_CTR(name, cts, rts) \
> - static const unsigned int name ##_mux[] = { cts##_MARK, rts##_MARK, }
> -#define SCIF_PFC_CLK(name, sck) \
> - static const unsigned int name ##_mux[] = { sck##_MARK, }
> +#define SH_PFC_MUX1(name, arg1) \
> + static const unsigned int name ##_mux[] = { arg1##_MARK }
> +#define SH_PFC_MUX2(name, arg1, arg2) \
> + static const unsigned int name ##_mux[] = { arg1##_MARK, arg2##_MARK, }
> +#define SH_PFC_MUX3(name, arg1, arg2, arg3) \
> + static const unsigned int name ##_mux[] = { arg1##_MARK, arg2##_MARK,
\
> + arg3##_MARK }
> +#define SH_PFC_MUX4(name, arg1, arg2, arg3, arg4) \
> + static const unsigned int name ##_mux[] = { arg1##_MARK, arg2##_MARK, \
> + arg3##_MARK, arg4##_MARK }
What's your plan for groups of more than 4 pins ? :-)
At some point, when the groups get large, I think it's better to define the
arrays explicitly.
I'm fine with this patch though.
> +/* - SCIF macro
> ------------------------------------------------------------- */ +#define
> SCIF_PFC_PIN(name, args...) SH_PFC_PINS(name, args)
> +#define SCIF_PFC_DAT(name, tx, rx) SH_PFC_MUX2(name, tx, rx)
> +#define SCIF_PFC_CTR(name, cts, rts) SH_PFC_MUX2(name, cts, rts)
> +#define SCIF_PFC_CLK(name, sck) SH_PFC_MUX1(name, sck)
>
> /* - HSCIF0
> ----------------------------------------------------------------- */
> SCIF_PFC_PIN(hscif0_data_a, RCAR_GP_PIN(1, 17), RCAR_GP_PIN(1, 18));
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-04-22 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 3:07 [PATCH 1/3 v3] sh-pfc: r8a7778: add common PFC macro helper Kuninori Morimoto
2013-04-22 5:24 ` Simon Horman
2013-04-22 10:06 ` Laurent Pinchart [this message]
2013-04-23 0:32 ` Kuninori Morimoto
2013-04-26 18:33 ` Sergei Shtylyov
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=3998361.LvOaInl8Ye@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).