linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Bo Shen <voice.shen@atmel.com>
Cc: shubhrajyoti@ti.com, nicolas.ferre@atmel.com, jm.lin@atmel.com,
	linux-input@vger.kernel.org
Subject: Re: [PATCH v2] input: dts: qt1070: add device tree support
Date: Tue, 21 Aug 2012 22:55:37 -0700	[thread overview]
Message-ID: <20120822055537.GE20624@core.coreip.homeip.net> (raw)
In-Reply-To: <1345434070-6539-1-git-send-email-voice.shen@atmel.com>

Hi Bo,

On Mon, Aug 20, 2012 at 11:41:10AM +0800, Bo Shen wrote:
> This patch enable the qt1070 device tree support
> 
> If using device tree, the node of qt1070 looks like
> i2c@0 {					     // this is an example
>  	status = "okay";		     // Enable i2c master
>  	qt1070@1b {
>  		compatible = "atmel,qt1070"; // FDT device id
>  		reg = <0x1b>;		     // qt1070 i2c address
>  		change-gpio = <&pioA 7 1>;   // gpio used as interrupt
>  	};
> };
> 
> Signed-off-by: Bo Shen <voice.shen@atmel.com>
> ---
> change since v1
>   Add gpio relative stuff, gpio_is_valid, gpio_request
> 
> ---
>  drivers/input/keyboard/qt1070.c |   31 +++++++++++++++++++++++++++----
>  1 file changed, 27 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/input/keyboard/qt1070.c b/drivers/input/keyboard/qt1070.c
> index ca68f29..2717bb4 100644
> --- a/drivers/input/keyboard/qt1070.c
> +++ b/drivers/input/keyboard/qt1070.c
> @@ -33,6 +33,8 @@
>  #include <linux/interrupt.h>
>  #include <linux/jiffies.h>
>  #include <linux/delay.h>
> +#include <linux/of.h>
> +#include <linux/of_gpio.h>
>  
>  /* Address for each register */
>  #define CHIP_ID            0x00
> @@ -155,11 +157,25 @@ static int __devinit qt1070_probe(struct i2c_client *client,
>  		return -ENODEV;
>  	}
>  
> -	if (!client->irq) {
> +	if (client->dev.of_node)
> +		client->irq = of_get_named_gpio(client->dev.of_node,
> +				"change-gpio", 0);

I'd say this gpio to irq DT mapping should be done by the same code that
parses I2C address and creates client structure.

> +
> +	if (!client->irq || client->irq < 0) {
>  		dev_err(&client->dev, "please assign the irq to this device\n");
>  		return -EINVAL;
>  	}
>  
> +	if (gpio_is_valid(client->irq)) {
> +		if (gpio_request(client->irq, "qt1070-change")) {
> +			dev_err(&client->dev, "request gpio failed\n");
> +			return -EINVAL;
> +		}
> +	} else {
> +		dev_err(&client->dev, "gpio is not valid\n");
> +		return -EINVAL;
> +	}
> +
>  	/* Identify the qt1070 chip */
>  	if (!qt1070_identify(client))
>  		return -ENODEV;
> @@ -200,9 +216,9 @@ static int __devinit qt1070_probe(struct i2c_client *client,
>  	qt1070_write(client, RESET, 1);
>  	msleep(QT1070_RESET_TIME);
>  
> -	err = request_threaded_irq(client->irq, NULL, qt1070_interrupt,
> -				   IRQF_TRIGGER_NONE | IRQF_ONESHOT,
> -				   client->dev.driver->name, data);
> +	err = request_threaded_irq(gpio_to_irq(client->irq), NULL,

This will surely break non-DT case.

> +			qt1070_interrupt, IRQF_TRIGGER_NONE | IRQF_ONESHOT,
> +			"qt1070-change", data);
>  	if (err) {
>  		dev_err(&client->dev, "fail to request irq\n");
>  		goto err_free_mem;
> @@ -243,6 +259,12 @@ static int __devexit qt1070_remove(struct i2c_client *client)
>  	return 0;
>  }
>  
> +static const struct of_device_id atmel_qt1070_of_match[] = {
> +	{ .compatible = "atmel,qt1070", },
> +	{ },
> +};
> +MODULE_DEVICE_TABLE(of, atmel_qt1070_of_match);
> +
>  static const struct i2c_device_id qt1070_id[] = {
>  	{ "qt1070", 0 },
>  	{ },
> @@ -253,6 +275,7 @@ static struct i2c_driver qt1070_driver = {
>  	.driver	= {
>  		.name	= "qt1070",
>  		.owner	= THIS_MODULE,
> +		.of_match_table = atmel_qt1070_of_match,
>  	},
>  	.id_table	= qt1070_id,
>  	.probe		= qt1070_probe,
> -- 
> 1.7.10
> 

Thanks.

-- 
Dmitry

  reply	other threads:[~2012-08-22  5:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-20  3:41 [PATCH v2] input: dts: qt1070: add device tree support Bo Shen
2012-08-22  5:55 ` Dmitry Torokhov [this message]
2012-08-23  8:50   ` Bo Shen

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=20120822055537.GE20624@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=jm.lin@atmel.com \
    --cc=linux-input@vger.kernel.org \
    --cc=nicolas.ferre@atmel.com \
    --cc=shubhrajyoti@ti.com \
    --cc=voice.shen@atmel.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).