All of lore.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Matt Turner <mattst88@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: select() to /dev/rtc0 to wait for clock tick timed out
Date: Fri, 19 Aug 2011 11:07:22 -0700	[thread overview]
Message-ID: <1313777242.2970.131.camel@work-vm> (raw)
In-Reply-To: <CAEdQ38HGfd9YWE+WLuirE4Km6UE6N26toTj=-1BuXAQUux6t5g@mail.gmail.com>

On Fri, 2011-08-19 at 00:16 -0400, Matt Turner wrote:
> Hi John,
> 
> I just sent a patch series to linux-mips@ that enables the RTC on a
> particular Broadcom MIPS motherboard (BCM91250A SWARM). The RTC is an
> M41T80.
> 
> When I first found the patchset (it was originally sent a a few years
> ago) and applied it to 2.6.37, it worked perfectly.
> 
> Applied to 3.x (and I think even 2.6.38) I get the following when I run hwclock:
> 
> # hwclock --systohc
> select() to /dev/rtc0 to wait for clock tick timed out

So do alarm interrupts actually work on the hardware? 

The rtc-m41t80.c driver looks like it should support them ok.

Does the test program at the end of Documentation/rtc.txt do much?

thanks
-john

  parent reply	other threads:[~2011-08-19 18:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19  4:16 select() to /dev/rtc0 to wait for clock tick timed out Matt Turner
2011-08-19 17:23 ` john stultz
2011-08-19 18:07 ` john stultz [this message]
2011-08-19 19:41   ` Matt Turner
2011-08-19 19:59     ` john stultz
2011-08-19 20:06       ` Matt Turner
2011-08-19 20:34         ` john stultz
2011-08-19 20:34           ` john stultz
2011-08-19 20:56           ` Matt Turner
2011-08-19 21:21             ` john stultz
2011-08-19 21:48               ` Matt Turner
2011-08-25 17:30                 ` Matt Turner
2011-08-26 16:05                   ` Atsushi Nemoto
2011-12-30  8:31       ` Xiangfu Liu
2012-03-16  8:53         ` Xiangfu Liu
2012-03-17  1:10         ` John Stultz
2012-03-18  7:03           ` Xiangfu Liu

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=1313777242.2970.131.camel@work-vm \
    --to=johnstul@us.ibm.com \
    --cc=linux-mips@linux-mips.org \
    --cc=mattst88@gmail.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.