From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Simon <horms@verge.net.au>, Magnus <magnus.damm@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>
Subject: Re: [PATCH][RFC] sh-pfc: add new PINMUX_IPSR_MODS() macro
Date: Sat, 29 Aug 2015 11:39:09 +0300 [thread overview]
Message-ID: <38944168.Lsx7EbeIaO@avalon> (raw)
In-Reply-To: <87h9nkc7km.wl%kuninori.morimoto.gx@renesas.com>
Hi Morimoto-san,
On Friday 28 August 2015 14:20:41 Kuninori Morimoto wrote:
> From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>
> Actually, PINMUX_IPSR_MODS() macro is same as PINMUX_IPSR_MODSEL_DATA().
> Current PFC driver is very difficult to read, because macro names are
> using different lenth. Especially PINMUX_IPSR_MODSEL_DATA() is well
> used macro
>
> PINMUX_IPSR_NOGP(ispr, ...)
> PINMUX_IPSR_DATA(ipsr, ...)
> PINMUX_IPSR_NOGM(ispr, ...)
> PINMUX_IPSR_NOFN(ipsr, ...)
> PINMUX_IPSR_MSEL(ipsr, ...)
> PINMUX_IPSR_MODSEL_DATA(ipsr, ...)
>
> These are readable
>
> PINMUX_IPSR_NOGP(ispr, ...)
> PINMUX_IPSR_DATA(ipsr, ...)
> PINMUX_IPSR_NOGM(ispr, ...)
> PINMUX_IPSR_NOFN(ipsr, ...)
> PINMUX_IPSR_MSEL(ipsr, ...)
> PINMUX_IPSR_MODS(ipsr, ...)
>
> We can replace all PINMUX_IPSR_MODSEL_DATA() to PINMUX_IPSR_MODS(),
> and remove PINMUX_IPSR_MODSEL_DATA() from header.
I agree that the PINMUX_IPSR_MODSEL_DATA() name makes code harder to read.
However, PINMUX_IPSR_MODS() isn't very descriptive, I think it would make the
code confusing (not that it isn't already...).
The only difference between PINMUX_IPSR_MSEL and PINMUX_IPSR_MODSEL_DATA is
the order in which the MODSEL, GSPR and IPSR registers are written. I wonder
if that's actually important, or if we could merge both macros into a single
one. What do you think ?
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> ---
>
> > LinusW, Laurent
>
> As I mentioned above, if this patch was accepted, I can replace all
> PINMUX_IPSR_MODSEL_DATA() to PINMUX_IPSR_MODS(). But I didn't it since it
> is [RFC] now
>
> drivers/pinctrl/sh-pfc/sh_pfc.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/pinctrl/sh-pfc/sh_pfc.h
> b/drivers/pinctrl/sh-pfc/sh_pfc.h index 0874cfe..40447d54 100644
> --- a/drivers/pinctrl/sh-pfc/sh_pfc.h
> +++ b/drivers/pinctrl/sh-pfc/sh_pfc.h
> @@ -173,6 +173,8 @@ struct sh_pfc_soc_info {
> PINMUX_DATA(fn##_MARK, FN_##ipsr, FN_##ms)
> #define PINMUX_IPSR_MSEL(ipsr, fn, ms) \
> PINMUX_DATA(fn##_MARK, FN_##fn, FN_##ipsr, FN_##ms)
> +#define PINMUX_IPSR_MODS(ipsr, fn, ms) \
> + PINMUX_DATA(fn##_MARK, FN_##ms, FN_##ipsr, FN_##fn)
> #define PINMUX_IPSR_MODSEL_DATA(ipsr, fn, ms) \
> PINMUX_DATA(fn##_MARK, FN_##ms, FN_##ipsr, FN_##fn)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-08-29 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 5:20 [PATCH][RFC] sh-pfc: add new PINMUX_IPSR_MODS() macro Kuninori Morimoto
2015-08-29 8:39 ` Laurent Pinchart [this message]
2015-08-30 23:43 ` Kuninori Morimoto
2015-08-31 0:19 ` Kuninori Morimoto
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=38944168.Lsx7EbeIaO@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-sh@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).