The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org, MyungJoo Ham <myungjoo.ham@samsung.com>
Subject: Re: [PATCH] extcon: gpio: Request gpio pin before modifying its state
Date: Wed, 27 Nov 2013 07:41:31 +0900	[thread overview]
Message-ID: <5295239B.7070608@samsung.com> (raw)
In-Reply-To: <52948F0E.9080303@roeck-us.net>

On 11/26/2013 09:07 PM, Guenter Roeck wrote:
> On 11/25/2013 11:55 PM, Chanwoo Choi wrote:
>> Hi Guenter,
>>
>> On 11/23/2013 02:26 AM, Guenter Roeck wrote:
>>> Commit 338de0ca (extcon: gpio: Use gpio driver/chip debounce if supported)
>>> introduced a call to gpio_set_debounce() before actually requesting the
>>> respective gpio pin from the gpio subsystem.
>>>
>>> The gpio subsystem expects that a gpio pin was requested before modifying its
>>> state. Not doing so results in a warning from gpiolib, and the gpio pin is
>>> auto-requested. This in turn causes the subsequent devm_gpio_request_one()
>>> to fail. So devm_gpio_request_one() must be called prior to calling
>>> gpio_set_debounce().
>>>
>>> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
>>> ---
>>>   drivers/extcon/extcon-gpio.c |   11 ++++++-----
>>>   1 file changed, 6 insertions(+), 5 deletions(-)
>>>
>>
>> Applid it on extcon-next branch.
>>
> 
> As this is a bug fix, I think it would make sense to have this applied to the current
> kernel and not wait for 3.14.
> 

OK, I move it on extcon-linus branch.

Thanks,
Chanwoo Choi


  reply	other threads:[~2013-11-26 22:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22 17:26 [PATCH] extcon: gpio: Request gpio pin before modifying its state Guenter Roeck
2013-11-26  7:55 ` Chanwoo Choi
2013-11-26 12:07   ` Guenter Roeck
2013-11-26 22:41     ` Chanwoo Choi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-11-25  2:37 MyungJoo Ham

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=5295239B.7070608@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=myungjoo.ham@samsung.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