* [Buildroot] Buildroot 2013.08.1, Linaro 2013.04 as toolchain, kernel 3.0.101, wakeup from standby issue @ 2013-11-10 4:17 Stanislav Vlasic 2013-11-10 8:48 ` Thomas Petazzoni 0 siblings, 1 reply; 3+ messages in thread From: Stanislav Vlasic @ 2013-11-10 4:17 UTC (permalink / raw) To: buildroot Hi, little help needed. 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). Thanx -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20131110/ccaa03c2/attachment.html> ^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] Buildroot 2013.08.1, Linaro 2013.04 as toolchain, kernel 3.0.101, wakeup from standby issue 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 2013-11-10 12:13 ` Stanislav Vlasic 0 siblings, 1 reply; 3+ messages in thread From: Thomas Petazzoni @ 2013-11-10 8:48 UTC (permalink / raw) To: buildroot 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] Buildroot 2013.08.1, Linaro 2013.04 as toolchain, kernel 3.0.101, wakeup from standby issue 2013-11-10 8:48 ` Thomas Petazzoni @ 2013-11-10 12:13 ` Stanislav Vlasic 0 siblings, 0 replies; 3+ messages in thread From: Stanislav Vlasic @ 2013-11-10 12:13 UTC (permalink / raw) To: buildroot Hi Thomas, I'm not claiming it's buildroot issue or problem, but some point here / guideance how it should behave because I'm little lost here when it comes to that part. Platform is Amlogic MX, and kernel is.... mixture between latest official Amlogic 3.0.50 kernel patched with various fixes + official kernel patches from kernel.org to bring it to latest 3.0 version which is .101 and in EOL state for some days now. Kernel itself works fine and much better than original one that SoC provides, it works with Android too, so it's not kernel related issue. I'm doing something wrong and was hoping for any help from you guys. Regards On Sun, Nov 10, 2013 at 9:48 AM, Thomas Petazzoni < thomas.petazzoni@free-electrons.com> wrote: > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20131110/5df5217f/attachment.html> ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-11-10 12:13 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 2013-11-10 12:13 ` Stanislav Vlasic
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox