From: "Bosko Radivojevic" <bosko.radivojevic@gmail.com>
To: "Kim B. Heino" <Kim.Heino@bluegiga.com>
Cc: rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org,
a.zummo@towertech.it
Subject: Re: [PATCH] add support for ST M41T94 SPI RTC (patch rev. 3)
Date: Wed, 1 Oct 2008 14:51:38 +0200 [thread overview]
Message-ID: <d6c8ef150810010551x174fad1mc788e2f6e97b21c5@mail.gmail.com> (raw)
In-Reply-To: <48315FF6.9070909@bluegiga.com>
[ I sent a few private messages to Kim, but I'll sumarize my problem here ]
Hi all,
I have AT91SAM9260-based board, kernel is 2.6.26.3. M41T94 is
connected on SPI channel 1, chip select 0. I've applied Kim's patch
and added SPI device in board-sam9260ek.c:
#if defined(CONFIG_RTC_DRV_M41T94) || defined(CONFIG_RTC_DRV_M41T94_MODULE)
{ /* External RTC */
.modalias = "rtc-m41t94",
.chip_select = 0,
.max_speed_hz = 2 * 1000 * 1000,
.bus_num = 1,
},
#endif
During booting up everything seems fine (M41T94 is found etc), but it
is not working. Here is some output:
rtc-m41t94: dev (254:0)
rtc-m41t94 spi1.0: rtc core: registered rtc-m41t94 as rtc0
rtc-m41t94 spi1.0: read secs=0, mins=0, hours=0, mday=0, mon=-1,
year=100, wday=-1
rtc-m41t94 spi1.0: hctosys: unable to read the hardware clock
[..]
# hwclock -r;dmesg
hwclock: RTC_RD_TIME: Invalid argument
rtc-m41t94 spi1.0: read secs=0, mins=0, hours=0, mday=0, mon=-1,
year=100, wday=-1
#hwclock -w;dmesg
rtc-m41t94 spi1.0: write secs=15, mins=0, hours=0, mday=1, mon=0,
year=70, wday=4
I've tried both SPIMODE0 and SPIMODE3 (according to m41t94 datasheet)
but no improvements.
Thanks
next prev parent reply other threads:[~2008-10-01 12:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 11:09 Kim B. Heino
2008-10-01 12:51 ` Bosko Radivojevic [this message]
2008-10-02 17:33 ` Kim B. Heino
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=d6c8ef150810010551x174fad1mc788e2f6e97b21c5@mail.gmail.com \
--to=bosko.radivojevic@gmail.com \
--cc=Kim.Heino@bluegiga.com \
--cc=a.zummo@towertech.it \
--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
all inboxes | Powered by JetHome®