From: Stephen Warren <swarren@wwwdotorg.org>
To: Rhyland Klein <rklein@nvidia.com>
Cc: Anton Vorontsov <anton@enomsg.org>,
David Woodhouse <dwmw2@infradead.org>,
Manish Badarkhe <badarkhe.manish@gmail.com>,
Darbha Sriharsha <dsriharsha@nvidia.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [Patch V2] drivers: power: Add support for bq24735 charger
Date: Tue, 24 Sep 2013 17:10:19 -0600 [thread overview]
Message-ID: <52421BDB.50303@wwwdotorg.org> (raw)
In-Reply-To: <5241C041.7020208@nvidia.com>
On 09/24/2013 10:39 AM, Rhyland Klein wrote:
> On 9/23/2013 6:05 PM, Stephen Warren wrote:
>> On 09/23/2013 04:01 PM, Rhyland Klein wrote:
>>> On 9/23/2013 5:53 PM, Stephen Warren wrote:
>>>> On 09/19/2013 10:18 AM, Rhyland Klein wrote:
>>>>> Adding driver support for bq24735 charger chipset.
>>>>
>>>>> diff --git a/Documentation/devicetree/bindings/power_supply/ti,bq24735.txt b/Documentation/devicetree/bindings/power_supply/ti,bq24735.txt
>>
>>>>> + - ti,charge-current : Used to control and set the charging current. This value
>>>>> + must follow the below guidelines:
>>>>> + bit 0 - 5: Not used
>>>>> + bit 6: 1 = Adds 64mA of charger current
>>>>> + bit 7: 1 = Adds 128mA of charger current
>>>>> + bit 8: 1 = Adds 256mA of charger current
>>>>> + bit 9: 1 = Adds 512mA of charger current
>>>>> + bit 10: 1 = Adds 1024mA of charger current
>>>>> + bit 11: 1 = Adds 2048mA of charger current
>>>>> + bit 12: 1 = Adds 4096mA of charger current
>>>>> + bit 13 - 15: Not used
>>>>
>>>> That's a little odd. Why not just put the number of mA directly into the
>>>> property unshifted?
>>>
>>> This is how the hw register is defined, its the literal number of mA.
>>> This is cleaned up in the upcoming revision.
>>
>> OK. If you still want to use the raw register encoding, which seems
>> reasonable, why not just say:
>>
>> ti,charge-current: Value for charge current register as described in the
>> HW documentation.
>
> I had written this for v3:
>
> - ti,charge-current : Used to control and set the charging current. This
> value must be between 128mA and 8.128A with a 64mA step resolution. The
> POR value is 0x0000h. See spec for more details.
>
> Do you think the range is unnecessary or is it fine?
It's probably fine, although I expect unnecessary. I would mention the
exact register name from the spec, to make searching for it easier.
prev parent reply other threads:[~2013-09-24 23:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 16:18 Rhyland Klein
2013-09-19 20:27 ` Thierry Reding
2013-09-19 20:45 ` Rhyland Klein
2013-09-20 7:53 ` Thierry Reding
2013-09-20 16:21 ` Rhyland Klein
2013-09-24 18:13 ` Rhyland Klein
2013-09-24 18:31 ` Thierry Reding
2013-09-23 21:53 ` Stephen Warren
2013-09-23 22:01 ` Rhyland Klein
2013-09-23 22:05 ` Stephen Warren
2013-09-24 16:39 ` Rhyland Klein
2013-09-24 23:10 ` Stephen Warren [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=52421BDB.50303@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=anton@enomsg.org \
--cc=badarkhe.manish@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dsriharsha@nvidia.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rklein@nvidia.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
Powered by JetHome