From: Pavel Machek <pavel@denx.de>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Matti Vaittinen <matti.vaittinen@nsn.com>,
ext Guenter Roeck <linux@roeck-us.net>,
Jason Cooper <jason@lakedaemon.net>,
"a.zummo@towertech.it" <a.zummo@towertech.it>,
"jic23@kernel.org" <jic23@kernel.org>,
"arno@natisbad.org" <arno@natisbad.org>,
"jgunthorpe@obsidianresearch.com"
<jgunthorpe@obsidianresearch.com>,
"san@rosetechnology.dk" <san@rosetechnology.dk>,
"hs@denx.de" <hs@denx.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rtc-linux@googlegroups.com" <rtc-linux@googlegroups.com>,
Sverdlin Alexander <alexander.sverdlin@nsn.com>
Subject: Re: [PATCH] rtc: ds1307: add trickle charger device tree binding
Date: Mon, 8 Sep 2014 15:52:42 +0200 [thread overview]
Message-ID: <20140908135242.GA21412@amd> (raw)
In-Reply-To: <20140829104001.GB19424@leverpostej>
Hi!
> I would suggest we have two properties that describe the resistor's
> rating and whether or not there is a diode:
>
> trickle-resistor-ohms = <250>
> diode-connected;
>
> That's easy for a human to write and/or validate, we can easily extend
> it in future, requires no proliferation of macros, and describes the
> hardware rather than telling software what to do.
>
> The driver becomes a little more complicated, but gains sanity checking,
> which is a good thing.
Certainly looks better than register bit defines.
As rtc-bq32k has similar options, I'm interested, too. I believe we
should add
trickle-charge-enable;
(we may not want to charge at all), and I believe the diode should be
disconnect-diode;
... With diode connected, charge is slower, and that probably should
be the default value. We don't want to give too much current in
default case. (bq32k has hard-coded resistor value for
diode/not-diode case).
Thanks and best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2014-09-08 13:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 12:42 [PATCH] rtc: ds1307: add trickle charger device tree binding Matti Vaittinen
2014-08-28 12:59 ` Mark Rutland
2014-08-28 15:51 ` Guenter Roeck
2014-08-28 16:10 ` Mark Rutland
2014-08-28 16:48 ` Guenter Roeck
2014-08-28 17:28 ` Jason Cooper
2014-08-28 17:40 ` Guenter Roeck
2014-08-29 7:34 ` Matti Vaittinen
2014-08-29 10:40 ` Mark Rutland
2014-08-29 12:19 ` Matti Vaittinen
2014-08-29 12:24 ` Jason Cooper
2014-08-29 12:42 ` Mark Rutland
2014-08-29 12:48 ` Jason Cooper
2014-08-29 13:03 ` Mark Rutland
2014-08-29 14:06 ` Matti Vaittinen
2014-09-08 13:52 ` Pavel Machek [this message]
2014-09-08 14:58 ` Mark Rutland
2014-09-09 6:22 ` Matti Vaittinen
2014-09-09 11:34 ` Pavel Machek
2014-09-09 11:42 ` Jason Cooper
2014-09-09 13:48 ` VS: " Vaittinen, Matti (NSN - FI/Oulu)
2014-08-29 7:41 ` Matti Vaittinen
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=20140908135242.GA21412@amd \
--to=pavel@denx.de \
--cc=a.zummo@towertech.it \
--cc=alexander.sverdlin@nsn.com \
--cc=arno@natisbad.org \
--cc=devicetree@vger.kernel.org \
--cc=hs@denx.de \
--cc=jason@lakedaemon.net \
--cc=jgunthorpe@obsidianresearch.com \
--cc=jic23@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=matti.vaittinen@nsn.com \
--cc=rtc-linux@googlegroups.com \
--cc=san@rosetechnology.dk \
/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