mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: linux-kernel@vger.kernel.org, MyungJoo Ham <myungjoo.ham@samsung.com>
Subject: Re: [PATCH v2 2/6] extcon-gpio: Use gpio driver/chip debounce if supported
Date: Tue, 10 Sep 2013 19:39:32 -0700	[thread overview]
Message-ID: <522FD7E4.90101@roeck-us.net> (raw)
In-Reply-To: <522FD58A.6070407@samsung.com>

On 09/10/2013 07:29 PM, Chanwoo Choi wrote:
> On 09/11/2013 11:16 AM, Guenter Roeck wrote:
>>
>> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
>> ---
>> v2: rephrase patch subject
>>      call gpio_set_debounce before registering extcon device,
>>      and set debounce_jiffies only if the call was not successful
>>
>>   drivers/extcon/extcon-gpio.c |    8 +++++++-
>>   1 file changed, 7 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/extcon/extcon-gpio.c b/drivers/extcon/extcon-gpio.c
>> index 77d35a7..e5a4405 100644
>> --- a/drivers/extcon/extcon-gpio.c
>> +++ b/drivers/extcon/extcon-gpio.c
>> @@ -100,7 +100,13 @@ static int gpio_extcon_probe(struct platform_device *pdev)
>>   	extcon_data->state_off = pdata->state_off;
>>   	if (pdata->state_on && pdata->state_off)
>>   		extcon_data->edev.print_state = extcon_gpio_print_state;
>> -	extcon_data->debounce_jiffies = msecs_to_jiffies(pdata->debounce);
>> +	if (pdata->debounce) {
>> +		ret = gpio_set_debounce(extcon_data->gpio,
>> +					pdata->debounce * 1000);
>> +		if (ret < 0)
>> +			extcon_data->debounce_jiffies =
>> +				msecs_to_jiffies(pdata->debounce);
>> +	}
>>
>>   	ret = extcon_dev_register(&extcon_data->edev, &pdev->dev);
>>   	if (ret < 0)
>>
>
> I'd like you to add patch description for patch feature.
> So I add a little description about using gpio_set_debounce()
>
> I modify patch name as following to maintain patch naming style of extcon.
> Before
> 	extcon-gpio: Do not unnecessarily initialize variables
> 	extcon-gpio: Use gpio driver/chip debounce if supported
> After
> 	extcon: gpio: Do not unnecessarily initialize variables
> 	extcon: gpio: Use gpio driver/chip debounce if supported
>
No problem. I'll try to remember next time. Too late for patch 3/6, though.
Sorry for that.

> Applied it on extcon-linus.
> You can check it on extcon-linus branch in a few minutes.
>
Thanks,
Guenter


  reply	other threads:[~2013-09-11  2:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30  4:29 [PATCH 0/6] extcon-gpio: Add devicetree support Guenter Roeck
2013-08-30  4:29 ` [PATCH 1/6] extcon-gpio: Do not unnecessarily initialize variables Guenter Roeck
2013-09-11  1:16   ` Chanwoo Choi
2013-08-30  4:29 ` [PATCH 2/6] extcon-gpio: If the gpio driver/chip supports debounce, use it Guenter Roeck
2013-09-11  1:16   ` Chanwoo Choi
2013-09-11  1:57     ` Guenter Roeck
2013-09-11  2:03       ` Chanwoo Choi
2013-09-11  2:16   ` [PATCH v2 2/6] extcon-gpio: Use gpio driver/chip debounce if supported Guenter Roeck
2013-09-11  2:29     ` Chanwoo Choi
2013-09-11  2:39       ` Guenter Roeck [this message]
2013-08-30  4:29 ` [PATCH 3/6] extcon-gpio: Add support for active-low presence detect pins Guenter Roeck
2013-09-11  2:14   ` Chanwoo Choi
2013-09-11  2:25     ` [PATCH v2 " Guenter Roeck
2013-09-11 23:57       ` Chanwoo Choi
2013-09-12  0:23         ` Guenter Roeck
2013-08-30  4:29 ` [RFC PATCH 4/6] extcon-gpio: Add devicetree support Guenter Roeck
2013-09-12 16:45   ` Mark Rutland
2013-09-12 17:00     ` Guenter Roeck
2013-08-30  4:29 ` [RFC PATCH 5/6] extcon-gpio: Describe devicetree bindings Guenter Roeck
2013-09-12 16:41   ` Mark Rutland
2013-09-12 16:53     ` Guenter Roeck
2013-09-16 14:21       ` Mark Rutland
2013-09-16 15:19         ` Guenter Roeck
2013-09-18 15:38           ` Mark Rutland
2013-09-19 16:42             ` Mark Brown
2013-09-19 18:28               ` Guenter Roeck
2013-09-19 18:35                 ` Mark Brown
2013-08-30  4:29 ` [RFC PATCH 6/6] extcon-gpio: Describe possible properties to support multi-type cables Guenter Roeck

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=522FD7E4.90101@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=cw00.choi@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®