public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tino Keitel <tino.keitel@gmx.de>
To: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>
Cc: linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com
Subject: Re: rtc_cmos: error after first write to wakealarm
Date: Fri, 15 Jun 2007 09:03:19 +0200	[thread overview]
Message-ID: <20070615070319.GA19455@dose.home.local> (raw)
In-Reply-To: <20070615155904.1d1da892.yoichi_yuasa@tripeaks.co.jp>

On Fri, Jun 15, 2007 at 15:59:04 +0900, Yoichi Yuasa wrote:
> On Fri, 15 Jun 2007 08:33:08 +0200
> Tino Keitel <tino.keitel@gmx.de> wrote:
> 
> > Hi,
> > 
> > I have the following strange behaviour with rtc_cmos:
> > 
> > $ echo 1181934240 > /sys/class/rtc/rtc0/wakealarm
> > bash: echo: write error: Device or resource busy
> > $ rmmod rtc_cmos
> > $ modprobe rtc_cmos
> > $ echo 1181934240 > /sys/class/rtc/rtc0/wakealarm
> > $ echo 1181934240 > /sys/class/rtc/rtc0/wakealarm
> > bash: echo: write error: Device or resource busy
> > $
> 
> If the alarm has already been enabled, you cannot set the next alarm. 
> You should disable first.

Ah, ok.
  
Where is the documentation that describes that I have to disable it
first, and how to do this? A migration document for /proc/acpi/alarm   
users would be nice, too.

Regards,
Tino

  reply	other threads:[~2007-06-15  7:03 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 [this message]
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

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=20070615070319.GA19455@dose.home.local \
    --to=tino.keitel@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtc-linux@googlegroups.com \
    --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