From: Zhao Yakui <yakui.zhao@intel.com>
To: "Chen, Huacai" <huacai.chen@intel.com>
Cc: linux-acpi@vger.kernel.org, linux-pm@lists.linux-foundation.org,
rtc-linux@googlegroups.com, lenb@kernel.org,
p_gortmaker@yahoo.com, a.zummo@towertech.it,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RTC: Fix CMOS time error after writing /proc/acpi/alarm
Date: Tue, 24 Jun 2008 14:37:53 +0800 [thread overview]
Message-ID: <1214289473.31069.1.camel@yakui_zhao.sh.intel.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC014E42D5@pdsmsx415.ccr.corp.intel.com>
On Mon, 2008-06-23 at 18:52 +0800, Chen, Huacai wrote:
> From: Huacai Chen <huacai.chen@intel.com>
>
> When writing /proc/acpi/alarm in adjust mode, e.g.
> echo "+0000-00-00 00:00:15" >/proc/acpi/alarm
> The "century" field should be read and added to "year" field before
> writing, otherwise the CMOS time will go back to 2000 years ago, e.g.
> # cat /proc/acpi/alarm
> 0008-06-21 11:38:46
> Then the system time may be reset to the date of manufacture after
> rebooting. This patch fixed this issue.
> Signed-off-by: Huacai Chen <huacai.chen@intel.com>
> Acked-by: Pavel Machek <pavel@suse.cz>
> ---
> diff --git a/drivers/acpi/sleep/proc.c b/drivers/acpi/sleep/proc.c
> index 224c57c..c9fdf7b 100644
> --- a/drivers/acpi/sleep/proc.c
> +++ b/drivers/acpi/sleep/proc.c
> @@ -315,8 +315,11 @@ acpi_system_write_alarm(struct file *file,
> cmos_bcd_write(day, acpi_gbl_FADT.day_alarm,
> rtc_control);
> if (acpi_gbl_FADT.month_alarm)
> cmos_bcd_write(mo, acpi_gbl_FADT.month_alarm,
> rtc_control);
> - if (acpi_gbl_FADT.century)
> + if (acpi_gbl_FADT.century) {
> + if (adjust)
> + yr += cmos_bcd_read(acpi_gbl_FADT.century,
> rtc_control) * 100;
> cmos_bcd_write(yr / 100, acpi_gbl_FADT.century,
> rtc_control);
> + }
this is OK.
> /* enable the rtc alarm interrupt */
> rtc_control |= RTC_AIE;
> CMOS_WRITE(rtc_control, RTC_CONTROL);
> ---
> This is for Linux 2.6.26-rc7.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-06-24 6:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 10:52 Chen, Huacai
2008-06-24 6:37 ` Zhao Yakui [this message]
2008-06-25 8:44 ` Alessandro Zummo
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=1214289473.31069.1.camel@yakui_zhao.sh.intel.com \
--to=yakui.zhao@intel.com \
--cc=a.zummo@towertech.it \
--cc=huacai.chen@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=p_gortmaker@yahoo.com \
--cc=rtc-linux@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®