All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Gadiyar, Anand" <gadiyar@ti.com>
Cc: "Aguirre, Sergio" <saaguirre@ti.com>,
	"Sripathy, Vishwanath" <vishwanath.bs@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Boot fail on OMAP3430SDP
Date: Wed, 30 Jun 2010 09:06:53 +0300	[thread overview]
Message-ID: <20100630060653.GP2822@atomide.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB03237636F1@dbde02.ent.ti.com>

* Gadiyar, Anand <gadiyar@ti.com> [100629 19:07]:
> Aguirre, Sergio wrote:
> > Sripathy, Vishwanath wrote:
> > > Here is the log from Early printk.
> > > 
> > 
> > <snip>
> > 
> > > Could not get gpios_ick
> > > Could not get gpios_fck
> > 
> > Probably Tony will be the best to answer this, but... This 
> > code shouldn't get executed I think (the one producing above prints)..
> > 
> > Above clocks are declared for omap2 only (in arch/arm/mach-omap2/clock24[20,30]_data.c), and even this 
> > clk_get calls are inside of a supposedly omap2 only execution in arch/arm/plat-omap/gpio.c:
> > 
> > static int __init _omap_gpio_init(void)
> > {
> > ...
> > ...
> > #if defined(CONFIG_ARCH_OMAP2)
> > 	if (cpu_class_is_omap2()) {
> 
> 
> Isn't cpu_class_is_omap2() valid for OMAP3 as well?

Yeah. The above should be just if (cpu_is_omap24xx()) instead.
But that's just a warning and should not matter for the boot
issue.

To me it looks like the early_printk works, but the 8250 serial
console never gets initialized?

Tony

      reply	other threads:[~2010-06-30  6:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29 13:35 Boot fail on OMAP3430SDP Sripathy, Vishwanath
2010-06-29 14:15 ` Sripathy, Vishwanath
2010-06-29 16:06   ` Aguirre, Sergio
2010-06-29 16:11     ` Gadiyar, Anand
2010-06-30  6:06       ` Tony Lindgren [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=20100630060653.GP2822@atomide.com \
    --to=tony@atomide.com \
    --cc=gadiyar@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=saaguirre@ti.com \
    --cc=vishwanath.bs@ti.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.