From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Chuansheng Liu <chuansheng.liu@intel.com>
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, zhuangzhi.li@intel.com,
fei.li@intel.com
Subject: Re: [PATCH] ACPI / osl: implement acpi_os_sleep() with msleep()
Date: Wed, 11 Sep 2013 14:36:31 +0200 [thread overview]
Message-ID: <37297227.So9eVdeflb@vostro.rjw.lan> (raw)
In-Reply-To: <1378921377.26153.26.camel@cliu38-desktop-build>
On Thursday, September 12, 2013 01:42:57 AM Chuansheng Liu wrote:
>
> Currently the acpi_os_sleep() is using the schedule_timeout_interruptible(),
> which can be interrupted by signal, which causes the real sleep time is shorter.
>
> According to the ACPI spec:
> The Sleep term is used to implement long-term timing requirements.
> Execution is delayed for at least the required number of milliseconds.
>
> The sleeping time should be at least of the required number msecs, here
> using msleep() to implement it.
>
> Also if the real time is shorter, we meet the device POWER ON issue.
What exactly is the "power on" issue?
Rafael
> CC: lizhuangzhi <zhuangzhi.li@intel.com>
> CC: Li Fei <fei.li@intel.com>
> Signed-off-by: liu chuansheng <chuansheng.liu@intel.com>
> ---
> drivers/acpi/osl.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/acpi/osl.c b/drivers/acpi/osl.c
> index e5f416c..b1629b5 100644
> --- a/drivers/acpi/osl.c
> +++ b/drivers/acpi/osl.c
> @@ -820,7 +820,7 @@ acpi_status acpi_os_remove_interrupt_handler(u32 irq, acpi_osd_handler handler)
>
> void acpi_os_sleep(u64 ms)
> {
> - schedule_timeout_interruptible(msecs_to_jiffies(ms));
> + msleep(ms);
> }
>
> void acpi_os_stall(u32 us)
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-09-11 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 17:42 Chuansheng Liu
2013-09-11 12:36 ` Rafael J. Wysocki [this message]
2013-09-11 23:55 ` Liu, Chuansheng
2013-09-12 0:20 ` Rafael J. Wysocki
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=37297227.So9eVdeflb@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=chuansheng.liu@intel.com \
--cc=fei.li@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhuangzhi.li@intel.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®