Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2013.08.1, Linaro 2013.04 as toolchain, kernel 3.0.101, wakeup from standby issue
Date: Sun, 10 Nov 2013 09:48:02 +0100	[thread overview]
Message-ID: <20131110094802.029c72fe@skate> (raw)
In-Reply-To: <CADYw_JJOEj-uO2yPF3BXo4wzUopvVha+wbH5=dNLHBU0CkBPEQ@mail.gmail.com>

Dear Stanislav Vlasic,

On Sun, 10 Nov 2013 05:17:28 +0100, Stanislav Vlasic wrote:

> Here are my steps I perform to suspend ARM based device:
> 
> - close all running apps (eg. XBMC)
> - sync command to save all cached data
> - issue mem to /sys/power/state sysfs node
> - after that power indicator led turns off
> 
> That all works just fine.
> 
> After interrupt (IR remote in my case handled by uboot and ARC), kernel
> wakes up, resumes all drivers, puts power led in ON state and ends up with
> unknown_wakeups message.
> 
> Any help or hint would be appreciated :) Android JellyBean 4.2.2 on same
> platform works way it should (it wakes up).

What makes you think this is a Buildroot problem? It seems like a
kernel problem, so I would suggest to contact the people who did the
kernel support for your hardware platform (which you forgot to mention,
BTW).

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2013-11-10  8:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-10  4:17 [Buildroot] Buildroot 2013.08.1, Linaro 2013.04 as toolchain, kernel 3.0.101, wakeup from standby issue Stanislav Vlasic
2013-11-10  8:48 ` Thomas Petazzoni [this message]
2013-11-10 12:13   ` Stanislav Vlasic

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=20131110094802.029c72fe@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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