From: Guenter Roeck <linux@roeck-us.net>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Mark Rutland <mark.rutland@arm.com>,
Matti Vaittinen <matti.vaittinen@nsn.com>,
"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: Thu, 28 Aug 2014 10:40:34 -0700 [thread overview]
Message-ID: <20140828174034.GC15307@roeck-us.net> (raw)
In-Reply-To: <20140828172842.GF12769@titan.lakedaemon.net>
On Thu, Aug 28, 2014 at 01:28:42PM -0400, Jason Cooper wrote:
> On Thu, Aug 28, 2014 at 09:48:25AM -0700, Guenter Roeck wrote:
> > On Thu, Aug 28, 2014 at 05:10:25PM +0100, Mark Rutland wrote:
> > > On Thu, Aug 28, 2014 at 04:51:57PM +0100, Guenter Roeck wrote:
> > > > On Thu, Aug 28, 2014 at 01:59:15PM +0100, Mark Rutland wrote:
> > > > > On Thu, Aug 28, 2014 at 01:42:44PM +0100, Matti Vaittinen wrote:
> > > > > > Patch adding support for specifying trickle charger setup from device
> > > > > > tree. Patch is based on linux-next tree.
> > > > > >
> > > > > >
> > > > > > Some DS13XX devices have "trickle chargers". Introduce a device tree binding
> > > > > > for specifying the setup and register values.
> > > > > >
> > > > > > Signed-off-by: Matti Vaittinen <matti.vaittinen@nsn.com>
> > > > > > ---
> > > > > > .../devicetree/bindings/i2c/trivial-devices.txt | 1 -
> > > > > > .../devicetree/bindings/rtc/dallas,ds1339.txt | 19 ++++++++++
> > > > > > drivers/rtc/rtc-ds1307.c | 44 ++++++++++++++++++++--
> > > > > > 3 files changed, 59 insertions(+), 5 deletions(-)
> > > > > > create mode 100644 Documentation/devicetree/bindings/rtc/dallas,ds1339.txt
> > > > > >
> > > > > > diff --git a/Documentation/devicetree/bindings/i2c/trivial-devices.txt b/Documentation/devicetree/bindings/i2c/trivial-devices.txt
> > > > > > index 6af570e..e9206a4 100644
> > > > > > --- a/Documentation/devicetree/bindings/i2c/trivial-devices.txt
> > > > > > +++ b/Documentation/devicetree/bindings/i2c/trivial-devices.txt
> > > > > > @@ -35,7 +35,6 @@ catalyst,24c32 i2c serial eeprom
> > > > > > cirrus,cs42l51 Cirrus Logic CS42L51 audio codec
> > > > > > dallas,ds1307 64 x 8, Serial, I2C Real-Time Clock
> > > > > > dallas,ds1338 I2C RTC with 56-Byte NV RAM
> > > > > > -dallas,ds1339 I2C Serial Real-Time Clock
> > > > > > dallas,ds1340 I2C RTC with Trickle Charger
> > > > > > dallas,ds1374 I2C, 32-Bit Binary Counter Watchdog RTC with Trickle Charger and Reset Input/Output
> > > > > > dallas,ds1631 High-Precision Digital Thermometer
> > > > > > diff --git a/Documentation/devicetree/bindings/rtc/dallas,ds1339.txt b/Documentation/devicetree/bindings/rtc/dallas,ds1339.txt
> > > > > > new file mode 100644
> > > > > > index 0000000..9faf40e
> > > > > > --- /dev/null
> > > > > > +++ b/Documentation/devicetree/bindings/rtc/dallas,ds1339.txt
> > > > > > @@ -0,0 +1,19 @@
> > > > > > +* Dallas DS1339 I2C Serial Real-Time Clock
> > > > > > +
> > > > > > +Required properties:
> > > > > > +- compatible: Should contain "dallas,ds1339".
> > > > > > +- reg: I2C address for chip
> > > > > > +
> > > > > > +Optional properties:
> > > > > > +- trickle_setup : Used Trickle Charger configuration,
> > > > > > + corresponding to 5 lowest bits in trickle charger register.
> > > > >
> > > > The value is provided via platform data, so it is platform specific
> > > > and presumably needs to be configurable. I did, however, not find
> > > > a single in-kernel driver which is actually setting it.
> > > > So this is a good question.
> > >
> > > I'm uncomfortable adding a field we don't understand to DT.
> > >
> > > Is there any publicly-available documentation for the device?
> > >
> >
> > Lots ;-)
> >
> > http://datasheets.maximintegrated.com/en/ds/DS1307.pdf
> > http://datasheets.maximintegrated.com/en/ds/DS1337.pdf
> > http://datasheets.maximintegrated.com/en/ds/DS1338.pdf
> > http://datasheets.maximintegrated.com/en/ds/DS1339.pdf
> > http://datasheets.maximintegrated.com/en/ds/DS1340.pdf
> > http://datasheets.maximintegrated.com/en/ds/DS1388.pdf
> > http://datasheets.maximintegrated.com/en/ds/DS3231.pdf
> >
> > Code suggests that DS1339, DS1339, and DS1340 have the register.
> >
> > Looking into the datasheets, the configuration consists of two parts:
> > - diode connected or not
> > - trickle charger resistor value (250, 2000, or 4000 ohm)
> >
> > Given that, it seems to me that those values should be configured
> > explicitly instead of using a binary value, and that the driver
> > should perform the conversion from dt entry to register value.
>
> iiuc, there is no way for the kernel to determine what is being trickle
> charged, and thus no way to determine how it should set this register.
>
> It may be a bit of overkill, but I think a DT macro would be the most
> maintainable solution here:
>
> #define DS1339_TRCKL_DIODE 0x08
> #define DS1339_TRCKL_NODIODE 0x04
> #define DS1339_TRCKL_R250 0x01
> #define DS1339_TRCKL_R2000 0x02
> #define DS1339_TRCKL_R4000 0x03
>
> trickle_setup = <DS1339_TRCKL_DIODE | DS1339_TRCKL_R250>;
>
> And the driver would take care of oring it with the enable pattern.
>
Yes, that sounds reasonable as well.
Guenter
next prev parent reply other threads:[~2014-08-28 17:40 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
[not found] ` <20140828124237.GA29102-3P0KQDf13zYjNwtGTSXw41mm0B4v8B71Fo5piaCiEZ7R7s880joybQ@public.gmane.org>
2014-08-28 12:59 ` Mark Rutland
2014-08-28 15:51 ` Guenter Roeck
[not found] ` <20140828155157.GB23677-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2014-08-28 16:10 ` Mark Rutland
2014-08-28 16:48 ` Guenter Roeck
[not found] ` <20140828164825.GA12153-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2014-08-28 17:28 ` Jason Cooper
2014-08-28 17:40 ` Guenter Roeck [this message]
[not found] ` <20140828174034.GC15307-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2014-08-29 7:34 ` Matti Vaittinen
[not found] ` <20140829073413.GN4587-3P0KQDf13zYjNwtGTSXw41mm0B4v8B71Fo5piaCiEZ7R7s880joybQ@public.gmane.org>
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
[not found] ` <20140829124829.GD3683-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2014-08-29 13:03 ` Mark Rutland
2014-08-29 14:06 ` Matti Vaittinen
2014-09-08 13:52 ` Pavel Machek
2014-09-08 14:58 ` Mark Rutland
2014-09-09 6:22 ` Matti Vaittinen
[not found] ` <20140909062158.GB21342-3P0KQDf13zYjNwtGTSXw41mm0B4v8B71Fo5piaCiEZ7R7s880joybQ@public.gmane.org>
2014-09-09 11:34 ` Pavel Machek
2014-09-09 11:42 ` Jason Cooper
[not found] ` <20140909114203.GL30828-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
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=20140828174034.GC15307@roeck-us.net \
--to=linux@roeck-us.net \
--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=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;
as well as URLs for NNTP newsgroup(s).