From: valentin.longchamp@epfl.ch (Valentin Longchamp)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [RTC] Add Freescale MC13783 RTC driver
Date: Wed, 04 Nov 2009 19:12:51 +0100 [thread overview]
Message-ID: <4AF1C423.3010407@epfl.ch> (raw)
In-Reply-To: <20091101203443.GB18116@pengutronix.de>
Hi Uwe,
Uwe Kleine-K?nig wrote:
> Hello,
>
> On Sat, Oct 24, 2009 at 10:35:42AM +0200, Uwe Kleine-K?nig wrote:
>> This driver provides support for the RTC part integrated into the
>> Freescale MC13783 PMIC and bases on patch created earlier by Sascha
>> Hauer.
>>
>> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
>> Signed-off-by: Uwe Kleine-K?nig <u.kleine-k?nig@pengutronix.de>
>> Cc: Valentin Longchamp <valentin.longchamp@epfl.ch>
>> Cc: Paul Gortmaker <p_gortmaker@yahoo.com>
>> Cc: Alessandro Zummo <a.zummo@towertech.it>
>> Cc: rtc-linux at googlegroups.com
>> ---
>> Hello,
>>
>> this patch depends on
>>
>> mfd/mc13783: near complete rewrite
>>
>> sent earlier on lkml[1]. Compared to the earlier version of rtc support
>> on mc13783 as sent by Sascha, this driver got reset detection and
>> therefore depends on the patch above.
>>
>> A tree runnable on Phytec's PCM038 is available in my git tree
>>
>> git://git.pengutronix.de/git/ukl/linux-2.6.git mc13783
>>
>> . (Maybe I will rewrite these commits, so please expect it might change
>> in a non-fast-forward manner.)
>
> Valentin, could you already test this? Any comments by the others?
>
I have tested your patches (taken your mc13783 branch today, and merged
it into my patches rebased on 2.6.32-rc6).
Your mfd/mc13783 rewrite seems to work for me (but since there is no
real usage for now, I don't use ADC yet and regulator don't do a lot).
But it runs fine on my hardware.
However, I get the hctosys: unable to read the hardware clock error
message at boot (from drivers/rtc/hctosys.c:62). Is it normal ?
Furthermore, the date and time are saved during system off, but the time
is not updated: if I shut down the system during 10 minutes, my time
will get a 10 minute delay. Is this a normal behavior with you current
implementation or is there something we have wrong in our design/code
(we have battery for the mc13783) ? I will have a further look at this
later, didn't have time now.
Val
--
Valentin Longchamp, PhD Student, EPFL-STI-LSRO1
valentin.longchamp at epfl.ch, Phone: +41216937827
http://people.epfl.ch/valentin.longchamp
MEA3485, Station 9, CH-1015 Lausanne
next prev parent reply other threads:[~2009-11-04 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1256330323-13300-1-git-send-email-u.kleine-koenig@pengutronix.de>
2009-10-24 8:35 ` [PATCH] [RTC] Add Freescale MC13783 RTC driver Uwe Kleine-König
2009-11-01 20:34 ` Uwe Kleine-König
2009-11-04 18:12 ` Valentin Longchamp [this message]
2009-11-05 15:06 ` Valentin Longchamp
2009-11-03 19:20 ` Uwe Kleine-König
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=4AF1C423.3010407@epfl.ch \
--to=valentin.longchamp@epfl.ch \
--cc=linux-arm-kernel@lists.infradead.org \
/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).