From: Chanwoo Choi <cw00.choi@samsung.com>
To: jonghwa3.lee@samsung.com
Cc: linux-kernel@vger.kernel.org, myungjoo.ham@samsung.com,
r.baldyga@samsung.com
Subject: Re: [PATCH] extcon: max77693: Fix a bug occured at changing ADC debounce time.
Date: Wed, 03 Sep 2014 15:56:05 +0900 [thread overview]
Message-ID: <5406BB85.1050903@samsung.com> (raw)
In-Reply-To: <5406B786.3020301@samsung.com>
On 09/03/2014 03:39 PM, jonghwa3.lee@samsung.com wrote:
> On 2014년 09월 03일 14:55, Chanwoo Choi wrote:
>
>> On 09/03/2014 02:50 PM, Jonghwa Lee wrote:
>>> When it writes some value other than 0 to BTLDset and JIGset, muic device
>>> will be reset automatically. And it happens during updating ADC debounce time,
>>> because it shares same register. To update ADC debounce time without reset,
>>> set value only to ADCDbset and 0 to BTLDset and JIGset.
>>>
>>> Signed-off-by: Jonghwa Lee <jonghwa3.lee@samsung.com>
>>> ---
>>> drivers/extcon/extcon-max77693.c | 11 ++++++++---
>>> 1 file changed, 8 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/extcon/extcon-max77693.c b/drivers/extcon/extcon-max77693.c
>>> index 77460f2..661a3bb 100644
>>> --- a/drivers/extcon/extcon-max77693.c
>>> +++ b/drivers/extcon/extcon-max77693.c
>>> @@ -255,10 +255,15 @@ static int max77693_muic_set_debounce_time(struct max77693_muic_info *info,
>>> case ADC_DEBOUNCE_TIME_10MS:
>>> case ADC_DEBOUNCE_TIME_25MS:
>>> case ADC_DEBOUNCE_TIME_38_62MS:
>>> - ret = regmap_update_bits(info->max77693->regmap_muic,
>>> + /*
>>> + * Don't touch BTLDset, JIGset when you want to change adc
>>> + * debounce time. BTLDset, JIGset reflects actual pin status
>>> + * and are not configurable.
>>> + */
>>> + ret = regmap_write_bits(info->max77693->regmap_muic,
>>> MAX77693_MUIC_REG_CTRL3,
>>> - CONTROL3_ADCDBSET_MASK,
>>> - time << CONTROL3_ADCDBSET_SHIFT);
>>> + (CONTROL3_ADCDBSET_MASK &
>>> + time << CONTROL3_ADCDBSET_SHIFT));
>>
>> Do you make this patch on extcon-next branch?
>>
>> The max77693_muic_set_debounce_time() of extcon-max77693.c
>> use regmap_update_bits instead of regmap_write_bits as following:
>
>
> This patch intends to use 'regmap_write_bits()' not 'regmap_update_bits()'.
You're right. It is my mistake to review this patch.
> With using regmap_update_bits(), it would writes some value to BTLDset and
> JIGset then muic device will loose current state.
OK, I'll apply yout next patch(v2).
Thanks,
Chanwoo Choi
prev parent reply other threads:[~2014-09-03 6:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 5:50 [PATCH] extcon: max77693: Fix a bug occured at changing ADC debounce time Jonghwa Lee
2014-09-03 5:55 ` Chanwoo Choi
2014-09-03 6:39 ` jonghwa3.lee
2014-09-03 6:56 ` Chanwoo Choi [this message]
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=5406BB85.1050903@samsung.com \
--to=cw00.choi@samsung.com \
--cc=jonghwa3.lee@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=r.baldyga@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