linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Cohen <david.a.cohen@linux.intel.com>
To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Cc: linux-sh@vger.kernel.org, linux-gpio@vger.kernel.org,
	Simon Horman <horms@verge.net.au>
Subject: Re: [PATCH] gpio: rcar: Support both edge trigger with DT
Date: Thu, 14 Nov 2013 20:43:50 -0800	[thread overview]
Message-ID: <5285A686.4000405@linux.intel.com> (raw)
In-Reply-To: <1384359983-29178-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>

Hi Laurent,

On 11/13/2013 08:26 AM, Laurent Pinchart wrote:
> Some versions of the R-Car GPIO controller support triggering on both
> edges of the input signal. Whether this capability is supported is
> currently specified in platform data. R-Car GPIO devices instantiated
> from the device tree have the capability turned off even when the
> hardware supports it.
> 
> To fix this, add DT match data support to the driver, initialize both
> edge trigger support from match data and enable both edge trigger in
> r8a7790 and r8a7791 match data.
> 
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> ---
>  drivers/gpio/gpio-rcar.c | 56 +++++++++++++++++++++++++++++++++++++-----------
>  1 file changed, 43 insertions(+), 13 deletions(-)
> 
> The patch has been tested on a Lager board. Simon, I've understood that you
> need this to add GPIO keys support to the Lager DT. Would you be able to test
> that ?
> 
> diff --git a/drivers/gpio/gpio-rcar.c b/drivers/gpio/gpio-rcar.c
> index 6038966..68b0940 100644
> --- a/drivers/gpio/gpio-rcar.c
> +++ b/drivers/gpio/gpio-rcar.c
> @@ -283,7 +283,34 @@ static struct irq_domain_ops gpio_rcar_irq_domain_ops = {
>  	.map	= gpio_rcar_irq_domain_map,
>  };
>  
> -static void gpio_rcar_parse_pdata(struct gpio_rcar_priv *p)
> +struct gpio_rcar_info {
> +	bool has_both_edge_trigger;
> +};
> +
> +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,
> +		},
> +	}, {
> +		.compatible = "renesas,gpio-r8a7791",
> +		.data = (void *)&(const struct gpio_rcar_info) {
> +			.has_both_edge_trigger = true,
> +		},
> +	}, {
> +		.compatible = "renesas,gpio-rcar",
> +		.data = (void *)&(const struct gpio_rcar_info) {
> +			.has_both_edge_trigger = false,
> +		},
> +	}, {
> +		/* Terminator */
> +	},

According to ANSI C, you can't initialize struct with empty { }. You
would need at least one 0 inside.
Despite gcc accepts it, there are some ppl over there trying kernel
with different compilers :)

(Hope I'm not being too nitpicky)

Br, David Cohen

  parent reply	other threads:[~2013-11-15  4:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13 16:26 [PATCH] gpio: rcar: Support both edge trigger with DT Laurent Pinchart
2013-11-14  6:12 ` Magnus Damm
2013-11-28 15:31   ` Laurent Pinchart
2013-11-29 12:23     ` Linus Walleij
2013-11-15  4:43 ` David Cohen [this message]
2013-11-17  0:57   ` Laurent Pinchart
2013-11-17  2:38     ` David Cohen

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=5285A686.4000405@linux.intel.com \
    --to=david.a.cohen@linux.intel.com \
    --cc=horms@verge.net.au \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-gpio@vger.kernel.org \
    --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).