From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 01/12] sh-pfc: r8a7778: add I2C pin groups
Date: Thu, 16 May 2013 14:45:47 +0000 [thread overview]
Message-ID: <5194F11B.8000100@cogentembedded.com> (raw)
In-Reply-To: <87hai3wg4d.wl%kuninori.morimoto.gx@renesas.com>
On 16-05-2013 11:14, Kuninori Morimoto wrote:
> Add I2C SDA/SCL pin groups to R8A7778 PFC driver.
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> ---
> drivers/pinctrl/sh-pfc/pfc-r8a7778.c | 54 ++++++++++++++++++++++++++++++++++
> 1 file changed, 54 insertions(+)
> diff --git a/drivers/pinctrl/sh-pfc/pfc-r8a7778.c b/drivers/pinctrl/sh-pfc/pfc-r8a7778.c
> index bc20083..ed78f74 100644
> --- a/drivers/pinctrl/sh-pfc/pfc-r8a7778.c
> +++ b/drivers/pinctrl/sh-pfc/pfc-r8a7778.c
> @@ -1339,6 +1339,32 @@ SH_PFC_MUX1(ether_link, ETH_LINK);
> SH_PFC_PINS(ether_magic, RCAR_GP_PIN(4, 20));
> SH_PFC_MUX1(ether_magic, ETH_MAGIC);
>
> +/* - I2C macro ------------------------------------------------------------- */
> +#define I2C_PFC_PIN(name, args...) SH_PFC_PINS(name, args)
> +#define I2C_PFC_DAT(name, sda, scl) SH_PFC_MUX2(name, sda, scl)
Why not just I2C_PFC_PINS() and I2C_PFC_DATA()?
Also, I don't think I2C_PFC_DAT() is a really good name, since the
group includes both data and clock lines. Why not just use SH_PFC_MUX2()?
> @@ -1788,6 +1839,9 @@ static const char * const vin1_groups[] = {
>
> static const struct sh_pfc_function pinmux_functions[] = {
> SH_PFC_FUNCTION(ether),
> + SH_PFC_FUNCTION(i2c1),
> + SH_PFC_FUNCTION(i2c2),
> + SH_PFC_FUNCTION(i2c3),
I comes *after* H in the alphabet, and this list should be sorted,
as well as all the above stuff.
WBR, Sergei
next prev parent reply other threads:[~2013-05-16 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 7:14 [PATCH 01/12] sh-pfc: r8a7778: add I2C pin groups Kuninori Morimoto
2013-05-16 14:45 ` Sergei Shtylyov [this message]
2013-05-17 0:21 ` Kuninori Morimoto
2013-05-17 12:28 ` 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=5194F11B.8000100@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.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).