linux-mips
[Top] [All Lists]

Re: select() to /dev/rtc0 to wait for clock tick timed out

To: mattst88@gmail.com
Subject: Re: select() to /dev/rtc0 to wait for clock tick timed out
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Date: Sat, 27 Aug 2011 01:05:06 +0900 (JST)
Cc: johnstul@us.ibm.com, linux-mips@linux-mips.org, rtc-linux@googlegroups.com, a.zummo@towertech.it
In-reply-to: <CAEdQ38G7csFL61Ye1h-3Jszh2nDHytm1ms0rS4nGBC1E0QEfzQ@mail.gmail.com>
References: <1313788912.2970.152.camel@work-vm> <CAEdQ38Gg2FWJNacoa51+=eu8JQRr2mSA7jCjosOGbv8FKPFDpw@mail.gmail.com> <CAEdQ38G7csFL61Ye1h-3Jszh2nDHytm1ms0rS4nGBC1E0QEfzQ@mail.gmail.com>
Sender: linux-mips-bounce@linux-mips.org
On Thu, 25 Aug 2011 13:30:02 -0400, Matt Turner <mattst88@gmail.com> wrote:
> I looked through the datasheet and tried to find a place where we're
> doing something wrong in the driver, but I didn't see anything.
> 
> http://www.datasheetcatalog.com/datasheets_pdf/M/4/1/T/M41T80.shtml

Excuse me for slow response.

As you and John discovered, this driver do not support alarm
completely.  This driver just can set/read alarm date/time, but RTC
interrupt is not implemented yet.

So possible solutions would be:

* Implement RTC irq handler. (Now we have threaded-irq so it would be
easier than the past)
* Drop .set_alarm function. (i.e. drop whole alarm codes)

I cannot test this driver by myself, but I will take a look if you had
any fix.  Thank you.

---
Atsushi Nemoto

<Prev in Thread] Current Thread [Next in Thread>