linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/5] pinctrl: r7s72100: add riic groups
Date: Tue, 17 Dec 2013 21:48:52 +0000	[thread overview]
Message-ID: <3802769.F4PZtN5om9@avalon> (raw)
In-Reply-To: <1387316678-10174-2-git-send-email-wsa@the-dreams.de>

Hi Wolfram,

Thank you for the patch.

On Tuesday 17 December 2013 22:44:34 Wolfram Sang wrote:
> From: Wolfram Sang <wsa@sang-engineering.com>
> 
> Tested RIIC2 on a genmai board. Other riic groups are untested but seem
> trivial enough to be added.
> 
> Signed-off-by: Wolfram Sang <wsa@sang-engineering.com>
> Acked-by: Magnus Damm <damm@opensource.se>
> ---
> 
> Note: With the current PFC driver as posted by Magnus, it needs another
> patch to work. Yet, I think this is a seperate PFC issue which needs to be
> sorted out seperately and shouldn't affect these declarations. I'll add the
> needed patch as a response to this mail.
> 
>  drivers/pinctrl/sh-pfc/pfc-r7s72100.c | 45 ++++++++++++++++++++++++++++++++
>  1 file changed, 45 insertions(+)
> 
> diff --git a/drivers/pinctrl/sh-pfc/pfc-r7s72100.c
> b/drivers/pinctrl/sh-pfc/pfc-r7s72100.c index a662876..2b716d1 100644
> --- a/drivers/pinctrl/sh-pfc/pfc-r7s72100.c
> +++ b/drivers/pinctrl/sh-pfc/pfc-r7s72100.c
> @@ -229,6 +229,27 @@ SCIF5(RZ_PIN_AND_MUX)
>  SCIF6(RZ_PIN_AND_MUX)
>  SCIF7(RZ_PIN_AND_MUX)
> 
> +#define RIIC0(fn)			\
> +	fn(riic0, scl, 1, 0, 1)		\
> +	fn(riic0, sda, 1, 1, 1)
> +
> +#define RIIC1(fn)			\
> +	fn(riic1, scl, 1, 2, 1)		\
> +	fn(riic1, sda, 1, 3, 1)
> +
> +#define RIIC2(fn)			\
> +	fn(riic2, scl, 1, 4, 1)		\
> +	fn(riic2, sda, 1, 5, 1)
> +
> +#define RIIC3(fn)			\
> +	fn(riic3, scl, 1, 6, 1)		\
> +	fn(riic3, sda, 1, 7, 1)
> +
> +RIIC0(RZ_PIN_AND_MUX)
> +RIIC1(RZ_PIN_AND_MUX)
> +RIIC2(RZ_PIN_AND_MUX)
> +RIIC3(RZ_PIN_AND_MUX)

Could you please move this above the SCIF declarations (same comment below) ? 
The pfc-*.c files tend to grow pretty big, and keeping entries sorted 
alphabetically helps.

> +
>  static const struct sh_pfc_pin_group pinmux_groups[] = {
>  	SCIF0(RZ_PMX_GROUP)
>  	SCIF1(RZ_PMX_GROUP)
> @@ -238,6 +259,10 @@ static const struct sh_pfc_pin_group pinmux_groups[] > { SCIF5(RZ_PMX_GROUP)
>  	SCIF6(RZ_PMX_GROUP)
>  	SCIF7(RZ_PMX_GROUP)
> +	RIIC0(RZ_PMX_GROUP)
> +	RIIC1(RZ_PMX_GROUP)
> +	RIIC2(RZ_PMX_GROUP)
> +	RIIC3(RZ_PMX_GROUP)
>  };
> 
>  static const char * const scif0_groups[] = {
> @@ -272,6 +297,22 @@ static const char * const scif7_groups[] = {
>  	SCIF7(RZ_GROUPS)
>  };
> 
> +static const char * const riic0_groups[] = {
> +	RIIC0(RZ_GROUPS)
> +};
> +
> +static const char * const riic1_groups[] = {
> +	RIIC1(RZ_GROUPS)
> +};
> +
> +static const char * const riic2_groups[] = {
> +	RIIC2(RZ_GROUPS)
> +};
> +
> +static const char * const riic3_groups[] = {
> +	RIIC3(RZ_GROUPS)
> +};
> +
>  static const struct sh_pfc_function pinmux_functions[] = {
>  	SH_PFC_FUNCTION(scif0),
>  	SH_PFC_FUNCTION(scif1),
> @@ -281,6 +322,10 @@ static const struct sh_pfc_function pinmux_functions[]
> = { SH_PFC_FUNCTION(scif5),
>  	SH_PFC_FUNCTION(scif6),
>  	SH_PFC_FUNCTION(scif7),
> +	SH_PFC_FUNCTION(riic0),
> +	SH_PFC_FUNCTION(riic1),
> +	SH_PFC_FUNCTION(riic2),
> +	SH_PFC_FUNCTION(riic3),
>  };
> 
>  #define PFC_REG(idx, name, reg)						\
-- 
Regards,

Laurent Pinchart


  parent reply	other threads:[~2013-12-17 21:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-17 21:44 [PATCH 0/5] arm: shmobile: r7s72100: add native i2c support Wolfram Sang
2013-12-17 21:44 ` [PATCH 1/5] pinctrl: r7s72100: add riic groups Wolfram Sang
2013-12-17 21:47   ` Wolfram Sang
2013-12-17 21:48   ` Laurent Pinchart [this message]
2013-12-17 21:44 ` [PATCH 2/5] arm: shmobile: r7s72100: add i2c clocks Wolfram Sang
2013-12-18 11:38   ` Sergei Shtylyov
2013-12-18 11:43     ` Wolfram Sang
2013-12-18 11:53       ` Sergei Shtylyov
2013-12-18 12:15         ` Wolfram Sang
2013-12-18 13:49           ` Simon Horman
2013-12-18 14:02             ` Sergei Shtylyov
2013-12-18 14:44               ` Magnus Damm
2013-12-18 15:13                 ` Sergei Shtylyov
2013-12-18 21:00             ` Wolfram Sang
2013-12-17 21:44 ` [PATCH 3/5] arm: shmobile: r7s72100: add nodes for i2c controllers to dtsi Wolfram Sang
2013-12-17 21:55   ` Laurent Pinchart
2013-12-17 22:13     ` Wolfram Sang
2013-12-17 22:16       ` Laurent Pinchart
2013-12-17 21:44 ` [PATCH 4/5] arm: shmobile: genmai: adapt dts to use native i2c driver Wolfram Sang
2013-12-17 21:57   ` Laurent Pinchart
2013-12-18 11:41   ` Sergei Shtylyov
2013-12-17 21:44 ` [PATCH 5/5] i2c: riic: add driver Wolfram Sang
2013-12-18  8:42   ` Geert Uytterhoeven

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=3802769.F4PZtN5om9@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.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).