linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: R Sricharan <r.sricharan@ti.com>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>,
	u-boot@lists.denx.de, linux-omap <linux-omap@vger.kernel.org>,
	trini@ti.com
Subject: Re: OMAP4/Panda: u-boot upgrade v2012.04.01 -> v2012.10 breaks RTC wakeups
Date: Wed, 07 Nov 2012 07:21:20 -0800	[thread overview]
Message-ID: <87390l8mmn.fsf@deeprootsystems.com> (raw)
In-Reply-To: <5099F3BA.6090302@ti.com> (R. Sricharan's message of "Wed, 7 Nov 2012 11:08:02 +0530")

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



      reply	other threads:[~2012-11-07 15:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-07  0:46 OMAP4/Panda: u-boot upgrade v2012.04.01 -> v2012.10 breaks RTC wakeups Kevin Hilman
2012-11-07  0:53 ` Santosh Shilimkar
2012-11-07  5:38   ` R Sricharan
2012-11-07 15:21     ` Kevin Hilman [this message]

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=87390l8mmn.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=r.sricharan@ti.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=trini@ti.com \
    --cc=u-boot@lists.denx.de \
    /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;
as well as URLs for NNTP newsgroup(s).