linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Igor Grinberg <grinberg@compulab.co.il>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] input: ads7846: fix gpio_pendown configuration
Date: Wed, 04 May 2011 09:42:32 +0300	[thread overview]
Message-ID: <4DC0F558.90705@compulab.co.il> (raw)
In-Reply-To: <20110503161818.GD6509@core.coreip.homeip.net>

On 05/03/11 19:18, Dmitry Torokhov wrote:

> On Tue, May 03, 2011 at 07:02:53PM +0300, Igor Grinberg wrote:
>> The pendown gpio was requested but not configured for input.
>> Request and configure it in one shot.
>>
>> Signed-off-by: Igor Grinberg <grinberg@compulab.co.il>
> There is no significant change from the previos version of the patch by
> Sourav Poddar that I tried to apply and had to revert. Does it compile
> if !CONFIG_GENERIC_GPIO?

shout!?!? It has been just several month we had this discussion,
but I've completely forgot it took place... shame on me...

Back to business, either way, the gpio direction must be configured
before accessing the gpio.
I can propose two solutions to this:
1) ads7846 relies on gpio subsystem, so add depend on
   CONFIG_GENERIC_GPIO to Kconfig ads7846 entry.
2) just don't use gpio_request_one(),
   but gpio_request() and then gpio_direction_input().

Logic behind 1 is that platforms that don't use CONFIG_GENERIC_GPIO
most likely don't use ads7846. Anybody know of such platform?
The second one is less intrusive and more local, but will do the job.

What do you think is more preferable?

>> ---
>>  drivers/input/touchscreen/ads7846.c |    3 ++-
>>  1 files changed, 2 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/input/touchscreen/ads7846.c b/drivers/input/touchscreen/ads7846.c
>> index c24946f..bf067aa 100644
>> --- a/drivers/input/touchscreen/ads7846.c
>> +++ b/drivers/input/touchscreen/ads7846.c
>> @@ -956,7 +956,8 @@ static int __devinit ads7846_setup_pendown(struct spi_device *spi, struct ads784
>>  		ts->get_pendown_state = pdata->get_pendown_state;
>>  	} else if (gpio_is_valid(pdata->gpio_pendown)) {
>>  
>> -		err = gpio_request(pdata->gpio_pendown, "ads7846_pendown");
>> +		err = gpio_request_one(pdata->gpio_pendown, GPIOF_IN,
>> +				       "ads7846_pendown");
>>  		if (err) {
>>  			dev_err(&spi->dev, "failed to request pendown GPIO%d\n",
>>  				pdata->gpio_pendown);
>> -- 
>> 1.7.3.4
>>

-- 
Regards,
Igor.


  reply	other threads:[~2011-05-04  6:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03 16:02 [PATCH] input: ads7846: fix gpio_pendown configuration Igor Grinberg
2011-05-03 16:18 ` Dmitry Torokhov
2011-05-04  6:42   ` Igor Grinberg [this message]
2011-05-05 16:13     ` Dmitry Torokhov
2011-05-08  8:44       ` [PATCH v2] " Igor Grinberg
2011-05-11 22:44         ` Dmitry Torokhov

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=4DC0F558.90705@compulab.co.il \
    --to=grinberg@compulab.co.il \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@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).