From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: rtc-linux@googlegroups.com
Cc: akpm@linux-foundation.org,
"Jüri Reitel" <juri.reitel@liewenthal.ee>,
linux-kernel@vger.kernel.org,
"David Brownell" <david-b@pacbell.net>,
"Jean Delvare" <khali@linux-fr.org>,
"Rodolfo Giometti" <giometti@linux.it>
Subject: Re: [rtc-linux] Re: invalid default values in RTC chip
Date: Thu, 16 Oct 2008 23:41:08 +0200 [thread overview]
Message-ID: <20081016234108.1268f65c@i1501.lan.towertech.it> (raw)
In-Reply-To: <20081016135846.8b06d9f8.akpm@linux-foundation.org>
On Thu, 16 Oct 2008 13:58:46 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> > My question relates to RTC driver linux/drivers/rtc/rtc-ds1307.c for
> > device m41t00. Driver probe function will fail if some of the chip's
> > registers contain invalid date time values i.e. if month register is 32
> > or minutes is 61. Is this correct behavior? Probe function's purpose is
> > to check if the device is as was assumed (this time RTC and it is). The
> > chip's values are incorrect but the chip works, even the m41t00 chip
> > manual states that after initial powerup (RTC battery power applied)
> > internal registers will contain random data.
> >
> > There are two solutions first is driver patch and another is i2c-dev and
> > i2cset tool to use from user space during bootup. Whitch one should be used?
Given we transitioned to the new i2c model, which mandates
a platform device to be declared, there's no more the need
to check for the device in the probing function.
this should be fixed in the driver.
however, a driver may still return a failure when reading
the time if there are inappropriate values in the registers.
the solution is to patch the driver for detection and then
use a recent hwclock on bootup to write the time if required.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
next prev parent reply other threads:[~2008-10-16 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 9:00 Jüri Reitel
2008-10-16 20:58 ` Andrew Morton
2008-10-16 21:41 ` Alessandro Zummo [this message]
2008-10-16 22:22 ` [rtc-linux] " David Brownell
2008-10-23 7:43 ` Jüri Reitel
2008-10-23 9:04 ` David Brownell
2008-10-23 9:55 ` Jüri Reitel
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=20081016234108.1268f65c@i1501.lan.towertech.it \
--to=alessandro.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=giometti@linux.it \
--cc=juri.reitel@liewenthal.ee \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome