linux-kernel - Re: [patch 2.6.18-rc1-git] rtc-acpi, with wakeup support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200607241244.36574.david-b@pacbell.net>
Date:	Mon, 24 Jul 2006 12:44:35 -0700
From:	David Brownell <david-b@...bell.net>
To:	Linux Kernel list <linux-kernel@...r.kernel.org>
Cc:	Alessandro Zummo <alessandro.zummo@...ertech.it>,
	len.brown@...el.com
Subject: Re: [patch 2.6.18-rc1-git] rtc-acpi, with wakeup support

Hmm, so -- any comments?  This applies just fine to RC2 of course
(it came out minutes before RC2 "shipped").  Seems to me this would
be appropriate for the next MM release.

Also, given some mechanism to tell whether this alarm woke the system,
this would seem to be the kind of infrastructure needed to make the
"deepening suspend" work correctly.  That is, idle system enters the
light weight "standby" powersave mode, then if it stays idle for long
enough for the timer to wake it could enter suspend-to-RAM (or that
new "suspend-to-both" mode).  There's certainly enough idle time on
most laptops for such mechanisms to help save significant amounts of
battery power, and it's best if such things don't explicitly depend
on features like ACPI.

- Dave

On Saturday 15 July 2006 12:40 pm, David Brownell wrote:
> The new RTC framework hasn't been very usable on most x86 desktop
> PCs ... so here's a driver using the ACPI RTC and PNPACPI.  AFAICT
> it could mostly replace drivers/char/rtc.c on ACPI systems.
> 
> One of the goals here was to expose this RTC as a normal wakeup
> event source ... no /proc/acpi/alarm thing, just the same userspace
> interfaces as on non-ACPI RTCs, and non-RTC devices.  That works
> somewhat ... for the very first time, I've seen ACPI wakeup behave!
> 
> But ACPI doesn't always behave after hardware wakeup events, so
> 
> 	echo disabled > /sys/class/rtc/rtc0/device/power/wakeup
> 
> may be appropriate on the systems where it doesn't yet work.
> 
> - Dave
> 
> p.s. A followup message will include a userspace program which
>      makes it easier to try the RTC wakeup mechanism.
> 
> 
> 
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/