I discovered that a fix for the rtc-omap driver is missing in the 3.14.x-ti
code. This was preventing alarmtimer and other devices from detecting
rtc-omap as a valid wake-capable RTC... applying this patch fixed the issue
for me.
https://lkml.org/lkml/2014/10/9/425
--
For more options, visit
I have 2 boards that I've been testing on that give the same results. One
is a A5C 2 GB board (?) and the other is a 0C0 4 GB board (Element14). I'm
not using any capes, just the bare board.
I've been comparing 3.14 and 4.x code, but have not found any key
differences other than code moving
Should power management functions (mem/standby) be working with 4.x TI
kernels on the BeagleBone Black for at least some subset of hardware
versions? Or was full support intentionally disabled due to hardware
related issues?
I've been using 3.14 TI kernels with the rtcwake command (both mem
On Thursday, April 21, 2016 at 6:26:19 PM UTC-4, William Hermans wrote:
>
> I can tell you that using kernel 4.1.x
> https://www.linux.com/learn/wake-linux-rtc-alarm-clock works. I'm not
> sure that rtc wake timer is related to the one you're asking. However, I
> can tell you that once the
I am trying to use power management (sleep mode) in a way that is similar
to how Android does it with timerfd and epoll. I want to enable autosleep
and use RTC wake timers (created using timerfd) that wake the system back
up and prevent sleep mode (using epoll mechanism) until the timer event
I was able to get waking from RTC working after installing
the 3.14.55-ti-rt-r78 kernel on the bone-debian-8 image. Did not appear
that waking from UART0 was working though.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to
