From: Ben Dooks <ben-linux@fluff.org>
To: Yauhen Kharuzhy <yauhen.kharuzhy@promwad.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Vladimir Semyonov <vladimir.semyonov@promwad.com>,
linux-samsung-soc@vger.kernel.org,
Ben Dooks <ben-linux@fluff.org>,
Vladimir Davydov <vladimir.davydov@promwad.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: S3C6410 power management support status
Date: Tue, 4 May 2010 01:29:15 +0100 [thread overview]
Message-ID: <20100504002915.GS6684@trinity.fluff.org> (raw)
In-Reply-To: <20100429145257.GA9592@jeknote.loshitsa1.net>
On Thu, Apr 29, 2010 at 05:52:57PM +0300, Yauhen Kharuzhy wrote:
> On Thu, Apr 29, 2010 at 03:00:51PM +0100, Mark Brown wrote:
> > On Thu, Apr 29, 2010 at 03:45:09PM +0300, Yauhen Kharuzhy wrote:
> >
> > > Can anybody explain current status of S3C6410 power management support
> > > in mainline? Suspend-to-RAM looks completely broken in the current
> > > Linus's git tree.
> >
> > What problems are you experiencing?
>
> 1. I enabled RTC driver for S3C6410 (it is cannot be enabled without
> modification of Kconfig) and CONFIG_SUSPEND.
> 2. echo +10 > /sys/class/rtc0/wakealarm && echo mem > /sys/power/state.
>
> System didn't go to sleep with messages:
>
> ---
> s3c_pm_enter(3)
> s3c_pm_enter: No wake-up sources!
> s3c_pm_enter: Aborting sleep
> ---
Ok, this is interesting, the system shouldn't have allowed the RTC as a
wakeup soruce as the core currently doesn't deal with 64XX non-EINT
sources. However, at-least the core code did the right thing and refused
to go to sleep.
I will look into the RTC/non-EINT wakeup sources for these SoCs today
and see if the changes are easy enough to make.
> This is caused by following code:
> ---
> #define any_allowed(mask, allow) (((mask) & (allow)) != (allow))
>
> if (!any_allowed(s3c_irqwake_intmask, s3c_irqwake_intallow) &&
> !any_allowed(s3c_irqwake_eintmask, s3c_irqwake_eintallow)) {
> printk(KERN_ERR "%s: No wake-up sources!\n", __func__);
> printk(KERN_ERR "%s: Aborting sleep\n", __func__);
> return -EINVAL;
> }
> ---
>
> But s3c_irqwake_intallow is defined in arch/arm/mach-s3c64xx/include/mach/pm-core.h
>
> ---
> /* make these defines, we currently do not have any need to change
> * the IRQ wake controls depending on the CPU we are running on */
>
> #define s3c_irqwake_eintallow ((1 << 28) - 1)
> #define s3c_irqwake_intallow (0)
> ---
They'll get changed once we have support for the non-eint sources.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
WARNING: multiple messages have this Message-ID (diff)
From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: S3C6410 power management support status
Date: Tue, 4 May 2010 01:29:15 +0100 [thread overview]
Message-ID: <20100504002915.GS6684@trinity.fluff.org> (raw)
In-Reply-To: <20100429145257.GA9592@jeknote.loshitsa1.net>
On Thu, Apr 29, 2010 at 05:52:57PM +0300, Yauhen Kharuzhy wrote:
> On Thu, Apr 29, 2010 at 03:00:51PM +0100, Mark Brown wrote:
> > On Thu, Apr 29, 2010 at 03:45:09PM +0300, Yauhen Kharuzhy wrote:
> >
> > > Can anybody explain current status of S3C6410 power management support
> > > in mainline? Suspend-to-RAM looks completely broken in the current
> > > Linus's git tree.
> >
> > What problems are you experiencing?
>
> 1. I enabled RTC driver for S3C6410 (it is cannot be enabled without
> modification of Kconfig) and CONFIG_SUSPEND.
> 2. echo +10 > /sys/class/rtc0/wakealarm && echo mem > /sys/power/state.
>
> System didn't go to sleep with messages:
>
> ---
> s3c_pm_enter(3)
> s3c_pm_enter: No wake-up sources!
> s3c_pm_enter: Aborting sleep
> ---
Ok, this is interesting, the system shouldn't have allowed the RTC as a
wakeup soruce as the core currently doesn't deal with 64XX non-EINT
sources. However, at-least the core code did the right thing and refused
to go to sleep.
I will look into the RTC/non-EINT wakeup sources for these SoCs today
and see if the changes are easy enough to make.
> This is caused by following code:
> ---
> #define any_allowed(mask, allow) (((mask) & (allow)) != (allow))
>
> if (!any_allowed(s3c_irqwake_intmask, s3c_irqwake_intallow) &&
> !any_allowed(s3c_irqwake_eintmask, s3c_irqwake_eintallow)) {
> printk(KERN_ERR "%s: No wake-up sources!\n", __func__);
> printk(KERN_ERR "%s: Aborting sleep\n", __func__);
> return -EINVAL;
> }
> ---
>
> But s3c_irqwake_intallow is defined in arch/arm/mach-s3c64xx/include/mach/pm-core.h
>
> ---
> /* make these defines, we currently do not have any need to change
> * the IRQ wake controls depending on the CPU we are running on */
>
> #define s3c_irqwake_eintallow ((1 << 28) - 1)
> #define s3c_irqwake_intallow (0)
> ---
They'll get changed once we have support for the non-eint sources.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2010-05-04 0:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 12:45 S3C6410 power management support status Yauhen Kharuzhy
2010-04-29 12:45 ` Yauhen Kharuzhy
2010-04-29 12:58 ` tommy.hong
2010-05-04 0:26 ` Ben Dooks
2010-04-29 14:00 ` Mark Brown
2010-04-29 14:00 ` Mark Brown
2010-04-29 14:52 ` Yauhen Kharuzhy
2010-04-29 14:52 ` Yauhen Kharuzhy
2010-05-04 0:29 ` Ben Dooks [this message]
2010-05-04 0:29 ` Ben Dooks
2010-05-04 0:24 ` Ben Dooks
2010-05-04 0:24 ` Ben Dooks
2010-05-06 14:49 ` Yauhen Kharuzhy
2010-05-06 14:49 ` Yauhen Kharuzhy
2010-05-10 0:58 ` Ben Dooks
2010-05-10 0:58 ` Ben Dooks
2010-05-10 2:35 ` Ben Dooks
2010-05-10 2:35 ` Ben Dooks
2010-05-10 14:27 ` Yauhen Kharuzhy
2010-05-10 14:27 ` Yauhen Kharuzhy
2010-05-11 0:20 ` Ben Dooks
2010-05-11 0:20 ` Ben Dooks
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=20100504002915.GS6684@trinity.fluff.org \
--to=ben-linux@fluff.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=vladimir.davydov@promwad.com \
--cc=vladimir.semyonov@promwad.com \
--cc=yauhen.kharuzhy@promwad.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.