From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: "Michael Büsch" <m@bues.ch>
Cc: Gregory Hermant <gregory.hermant@calao-systems.com>,
rtc-linux@googlegroups.com
Subject: Re: [rtc-linux] rv3029 EEPROM handling
Date: Sun, 28 Feb 2016 01:31:39 +0100 [thread overview]
Message-ID: <20160228003139.GB2398@piout.net> (raw)
In-Reply-To: <20160227153918.3c3d3853@wiggum>
Hi,
On 27/02/2016 at 15:39:18 +0100, Michael B=C3=BCsch wrote :
> I'm currently trying to use the Linux RV3029 RTC driver for one of my
> applications. So far the basic functionality works fine.
> However I need a way to (initially) program the EEPROM on the RTC chip
> to enable such things as temperature compensation or the trickle
> charger.
> As of now the Linux driver does not support that though. So I'm
> wondering how we should implement that. As an initial idea I think we
> could have about some sysfs attributes for these settings. Is there a
> better way (more standard API) to do this?
> If not, I'll do an implementation of this based on sysfs attributes.
>=20
trickle charging is usually enabled using device tree, however, I'd
really like to see more standardization on the property names.
I'm not sure yet about the temperature compensation. I've just merged
the crystal offset modification api with a sysfs interface in rtc-next:
http://git.kernel.org/cgit/linux/kernel/git/abelloni/linux.git/commit/?h=3D=
rtc-next&id=3D5f23807caab7801c3333c68417bb13c7e2439193
But this doesn't seem enough for that particular RTC.
--=20
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--=20
--=20
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---=20
You received this message because you are subscribed to the Google Groups "=
rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2016-02-28 0:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 14:39 [rtc-linux] rv3029 EEPROM handling Michael Büsch
2016-02-28 0:31 ` Alexandre Belloni [this message]
2016-02-28 8:44 ` Michael Büsch
2016-02-28 10:41 ` Alexandre Belloni
2016-02-28 11:58 ` Michael Büsch
2016-02-28 12:36 ` Alexandre Belloni
2016-02-28 17:14 ` Michael Büsch
2016-02-28 21:39 ` Alexandre Belloni
2016-02-29 17:07 ` Michael Büsch
2016-02-29 19:52 ` Alexandre Belloni
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=20160228003139.GB2398@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=gregory.hermant@calao-systems.com \
--cc=m@bues.ch \
--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.