public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Tino Keitel <tino.keitel@gmx.de>
Cc: Alessandro Zummo <alessandro.zummo@towertech.it>,
	rtc-linux@googlegroups.com,
	Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>,
	linux-kernel@vger.kernel.org
Subject: Re: [rtc-linux] Re: rtc_cmos: error after first write to wakealarm
Date: Fri, 22 Jun 2007 20:18:53 -0700	[thread overview]
Message-ID: <200706222018.54196.david-b@pacbell.net> (raw)
In-Reply-To: <200706221145.53157.david-b@pacbell.net>

[ please don't edit folk off the cc list unless you *know* they
are getting duplicates ... ]

> > It's got as much documentation in the kernel tree as that
> > old /proc/acpi/alarm thing.  More, in fact, since the GIT
> > comment for the putback creating /sys/rtc/.../wakealarm
> > files has lots of info about how to use it.
> 
> What GIT comment are you referring to?

What "git log drivers/rtc/rtc-sysfs.c" shows ... date Feb 12.
The web interface shows it too.


> > One theory:  it's an RTC that doesn't support all the fields,
> > so its driver is returning "-1" in fields like "year" or "month".
>
> With the old /proc/acpi/alarm, the year 2007 became 0007. Maybe this is
> the culprit?

That's essentially the same issue.  It needs some sort
of generic fix at the rtc_read_alarm() level.



      parent reply	other threads:[~2007-06-23  3:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-15  6:33 rtc_cmos: error after first write to wakealarm Tino Keitel
2007-06-15  6:59 ` Yoichi Yuasa
2007-06-15  7:03   ` Tino Keitel
2007-06-19 12:24     ` [rtc-linux] " Alessandro Zummo
2007-06-19 17:24       ` Tino Keitel
2007-06-22 17:34         ` Alessandro Zummo
2007-06-22 18:45           ` David Brownell
2007-06-22 19:44             ` Tino Keitel
2007-06-23  3:18             ` David Brownell [this message]

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=200706222018.54196.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=alessandro.zummo@towertech.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtc-linux@googlegroups.com \
    --cc=tino.keitel@gmx.de \
    --cc=yoichi_yuasa@tripeaks.co.jp \
    /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