From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Philippe De Muyter <phdm@macqel.be>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Alessandro Zummo <a.zummo@towertech.it>,
linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com
Subject: Re: [PATCH v2] rtc: add Abracon ABx80x driver
Date: Wed, 4 Mar 2015 10:06:01 +0100 [thread overview]
Message-ID: <20150304090601.GC3989@piout.net> (raw)
In-Reply-To: <20150304085242.GA24471@frolo.macqel>
On 04/03/2015 at 09:52:42 +0100, Philippe De Muyter wrote :
> > > And is the naming in Philippe's driver appropriate? If it supports the
> > > AB1801 (for example) then why is it described as an "abx805" driver?
> >
> > The real naming is in the form ABx8yz. With:
> >
> > x: 0 or 1, indicate the presence of the reset management
> > y: 0 or 1: 0 is i2c, 1 is spi
> > z: [1-5]: different amount of on chip SRAM. From what I understand, only
> > ABx8y5 are actually recommended for new designs.
>
> My driver is based on the datashet called 'AB18X5 Real-Time Clock with
> Power Management Family', which calls the parts 'AB18X5 family' with X
> being '0' for I2c parts and '1' for SPI parts.
>
> As the part I have and the driver I wrote are I2C, not SPI, I fixed the
> 'X' as 0 in the name of the driver.
>
> The datasheet lists only one part as being 'software and pin compatible'
> with the 'AB1805': the 'AB0805', hence the 'x' in the name I choose : abx805.
>
The "AB08XX Real-Time Clock Family" document states that they are all
software and pin compatible (including the AB18xx).
> Actually, my driver is used in production and works fine, because the
> default(reset) value of the 12/24 mode bit is '24 hour mode' and the
> default value of the 'write RTC bit' enables writing. There is
> no real need to play with them.
>
I know this is unlikely to happen but what if someone messes with the
RTC in the bootloader?
> >
> > What I like in Philippe's driver is the info printed at probe time and
> > the support for trickle charging. However, I wouldn't enable it
> > unconditionally.
>
> My hardware colleagues told me that the only way to enable the 'ultra low-power'
> functionality is enabling the trickle charger. And the 'ultra low-power'
> functionality is the reason we choose that chip, so I would at least
> keep that as the default behaviour.
>
My concern is that you have a static configuration. I would expose a
sysfs interface to configure the diode, resistor and enable/disable the
trickle charger. Would that work for you?
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-04 9:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 10:27 [PATCH v2] rtc: add Abracon ABx80x driver Alexandre Belloni
2015-03-02 8:54 ` Paul Bolle
2015-03-02 23:53 ` Andrew Morton
2015-03-03 1:11 ` Alexandre Belloni
2015-03-03 20:20 ` Andrew Morton
2015-03-03 20:50 ` Alexandre Belloni
2015-03-03 22:32 ` Andrew Morton
2015-03-03 23:09 ` Alexandre Belloni
2015-03-04 8:52 ` Philippe De Muyter
2015-03-04 9:06 ` Alexandre Belloni [this message]
2015-03-04 9:55 ` Philippe De Muyter
2015-03-04 10:38 ` Alexandre Belloni
2015-03-04 11:43 ` Philippe De Muyter
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=20150304090601.GC3989@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phdm@macqel.be \
--cc=rtc-linux@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.