linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Yoshihiro Kaneko <ykaneko0929@gmail.com>
Cc: linux-gpio@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	Simon Horman <horms@verge.net.au>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-sh@vger.kernel.org
Subject: Re: [PATCH v2] gpio: rcar: Add r8a7793 and r8a7794 support
Date: Fri, 12 Dec 2014 21:17:50 +0200	[thread overview]
Message-ID: <2188270.mR2n2an5Xq@avalon> (raw)
In-Reply-To: <1415361248-24610-1-git-send-email-ykaneko0929@gmail.com>

On Friday 07 November 2014 20:54:08 Yoshihiro Kaneko wrote:
> From: Hisashi Nakamura <hisashi.nakamura.ak@renesas.com>
> 
> The device tree probing for R-Car M2-N (r8a7793) and R-Car E2 (r8a7794)
> is added.
> 
> Signed-off-by: Hisashi Nakamura <hisashi.nakamura.ak@renesas.com>
> Signed-off-by: Yoshihiro Kaneko <ykaneko0929@gmail.com>
> ---
> 
> This patch is based on for-next branch of Linus Walleij's gpio tree.
> 
> v2 [Yoshihiro Kaneko]
> * As suggested by Geert Uytterhoeven
>   - clean up 4 identical copies of struct gpio_rcar_info.
> 
>  .../devicetree/bindings/gpio/renesas,gpio-rcar.txt |  4 +++-
>  drivers/gpio/gpio-rcar.c                           | 27 ++++++++++++-------
>  2 files changed, 21 insertions(+), 10 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/gpio/renesas,gpio-rcar.txt
> b/Documentation/devicetree/bindings/gpio/renesas,gpio-rcar.txt index
> 941a26a..38fb86f 100644
> --- a/Documentation/devicetree/bindings/gpio/renesas,gpio-rcar.txt
> +++ b/Documentation/devicetree/bindings/gpio/renesas,gpio-rcar.txt
> @@ -6,7 +6,9 @@ Required Properties:
>      - "renesas,gpio-r8a7778": for R8A7778 (R-Mobile M1) compatible GPIO
> controller.
>      - "renesas,gpio-r8a7779": for R8A7779 (R-Car H1) compatible GPIO
> controller.
>      - "renesas,gpio-r8a7790": for R8A7790 (R-Car H2) compatible GPIO
> controller.
> -    - "renesas,gpio-r8a7791": for R8A7791 (R-Car M2) compatible GPIO
> controller.
> +    - "renesas,gpio-r8a7791": for R8A7791 (R-Car M2-W) compatible GPIO
> controller.
> +    - "renesas,gpio-r8a7793": for R8A7793 (R-Car M2-N) compatible GPIO
> controller.
> +    - "renesas,gpio-r8a7794": for R8A7794 (R-Car E2) compatible GPIO
> controller.
>      - "renesas,gpio-rcar": for generic R-Car GPIO controller.
> 
>    - reg: Base address and length of each memory resource used by the GPIO
> diff --git a/drivers/gpio/gpio-rcar.c b/drivers/gpio/gpio-rcar.c
> index ef71ca8..24f0343 100644
> --- a/drivers/gpio/gpio-rcar.c
> +++ b/drivers/gpio/gpio-rcar.c
> @@ -1,6 +1,7 @@
>  /*
>   * Renesas R-Car GPIO Support
>   *
> + *  Copyright (C) 2014 Renesas Electronics Corporation
>   *  Copyright (C) 2013 Magnus Damm
>   *
>   * This program is free software; you can redistribute it and/or modify
> @@ -315,22 +316,30 @@ struct gpio_rcar_info {
>  	bool has_both_edge_trigger;
>  };
> 
> +static const struct gpio_rcar_info gpio_rcar_info_gen1 = {
> +	.has_both_edge_trigger = false,
> +};
> +
> +static const struct gpio_rcar_info gpio_rcar_info_gen2 = {
> +	.has_both_edge_trigger = true,
> +};

Seriously, doesn't this call for a "renesas,gpio-rcar-gen2" compatible string 
?

>  static const struct of_device_id gpio_rcar_of_table[] = {
>  	{
>  		.compatible = "renesas,gpio-r8a7790",
> -		.data = (void *)&(const struct gpio_rcar_info) {
> -			.has_both_edge_trigger = true,
> -		},
> +		.data = &gpio_rcar_info_gen2,
>  	}, {
>  		.compatible = "renesas,gpio-r8a7791",
> -		.data = (void *)&(const struct gpio_rcar_info) {
> -			.has_both_edge_trigger = true,
> -		},
> +		.data = &gpio_rcar_info_gen2,
> +	}, {
> +		.compatible = "renesas,gpio-r8a7793",
> +		.data = &gpio_rcar_info_gen2,
> +	}, {
> +		.compatible = "renesas,gpio-r8a7794",
> +		.data = &gpio_rcar_info_gen2,
>  	}, {
>  		.compatible = "renesas,gpio-rcar",
> -		.data = (void *)&(const struct gpio_rcar_info) {
> -			.has_both_edge_trigger = false,
> -		},
> +		.data = &gpio_rcar_info_gen1,
>  	}, {
>  		/* Terminator */
>  	},

-- 
Regards,

Laurent Pinchart


  parent reply	other threads:[~2014-12-12 19:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-07 11:54 [PATCH v2] gpio: rcar: Add r8a7793 and r8a7794 support Yoshihiro Kaneko
2014-11-14 10:04 ` Linus Walleij
2014-12-12 19:17 ` Laurent Pinchart [this message]
2014-12-15  2:03   ` Magnus Damm
2014-12-15  8:41     ` Geert Uytterhoeven
2014-12-15  8:49     ` Laurent Pinchart
2014-12-15  9:39       ` Magnus Damm

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=2188270.mR2n2an5Xq@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=gnurou@gmail.com \
    --cc=horms@verge.net.au \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=ykaneko0929@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).