[U-Boot] OMAP4/Panda: u-boot upgrade v2012.04.01 -> v2012.10 breaks RTC wakeups
Hello,
I just noticed that the kernel wakeup from suspend using RTC is broken after I upgraded u-boot from v2012.04.01 to v2012.10 on my OMAP4430/Panda and OMAP4460/Panda-ES.
I haven't isolated the cause yet, but am hoping someone might have a pointer about where to start digging.
Kevin
+ Sricharan,
On Tuesday 06 November 2012 06:46 PM, Kevin Hilman wrote:
Hello,
I just noticed that the kernel wakeup from suspend using RTC is broken after I upgraded u-boot from v2012.04.01 to v2012.10 on my OMAP4430/Panda and OMAP4460/Panda-ES.
I haven't isolated the cause yet, but am hoping someone might have a pointer about where to start digging.
Kevin
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Kevin, In the latest, pad mux and clocks for all non-essential modules at U-BOOT were removed.
This might also cause the problem. We can bring this back in u-boot by adding the following macros and check if it works fine again.
include/configs/omap4_common.h ------------------------------ #define CONFIG_SYS_ENABLE_PADS_ALL #define CONFIG_SYS_CLOCKS_ENABLE_ALL
Regards, Sricharan
On Wednesday 07 November 2012 06:23 AM, Santosh Shilimkar wrote:
- Sricharan,
On Tuesday 06 November 2012 06:46 PM, Kevin Hilman wrote:
Hello,
I just noticed that the kernel wakeup from suspend using RTC is broken after I upgraded u-boot from v2012.04.01 to v2012.10 on my OMAP4430/Panda and OMAP4460/Panda-ES.
I haven't isolated the cause yet, but am hoping someone might have a pointer about where to start digging.
Kevin
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Sricharan,
R Sricharan r.sricharan@ti.com writes:
In the latest, pad mux and clocks for all non-essential modules at U-BOOT were removed.
This might also cause the problem. We can bring this back in u-boot by adding the following macros and check if it works fine again.
include/configs/omap4_common.h
#define CONFIG_SYS_ENABLE_PADS_ALL #define CONFIG_SYS_CLOCKS_ENABLE_ALL
Thanks for the pointer, that got things working again. It's actually CONFIG_SYS_ENABLE_PADS_ALL alone which got things working again.
I'm glad to see u-boot going in this direction. In the kernel, we've also been trying to get rid of bootloader dependencies also, but it's clear we haven't got all of them yet.
I'll keep digging to see what's missing in the kernel pads setup to get RTC working again.
Kevin
participants (3)
-
Kevin Hilman -
R Sricharan -
Santosh Shilimkar