From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] PandaBoard hangs before starting init while booting v3.12
Date: Tue, 26 Nov 2013 10:20:22 -0800 [thread overview]
Message-ID: <20131126182022.GJ26766@atomide.com> (raw)
In-Reply-To: <CAKZq+rcoC5PLSVVazWcce7V7TcBM8=M2jM56bvk9HO2orKt8fg@mail.gmail.com>
* Chao Xu <caesarxuchao@gmail.com> [131122 19:28]:
> "I wonder if we also have some dependency to some earlier versions of
> u-boot as u-boot now only muxes the essential pins?"
> This is exactly the problem in my case. I added "#define
> CONFIG_SYS_ENABLE_PADS_ALL" in u-boot/include/configs/omap4_common.h
> and now there is output.
>
> I guess the reason that the u-boot worked out-of-box for Ben but not
> for me is that I missed some configurations in v3.12 kernel. I image
> there is a config options that tells the kernel to take care of the
> non-essential pins that used to be the responsibility of u-boot. Could
> you confirm my hypothesis? And if so, could you kindly suggest what's
> the name of the config option?
That would be CONFIG_PINCTRL_SINGLE=y for device tree based omaps.
But if we have the configuration missing for some driver in the
board specific .dts file, that won't help naturally. We do have
PINCTRL_SINGLE enabled in omap2plus_defconfig.
Regards,
Tony
next prev parent reply other threads:[~2013-11-26 18:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 15:14 [BUG] PandaBoard hangs before starting init while booting v3.12 Ben Gamari
2013-11-18 18:57 ` Tony Lindgren
2013-11-18 19:08 ` Ben Gamari
2013-11-19 4:14 ` Lokesh Vutla
2013-11-19 14:37 ` Ben Gamari
2013-11-20 2:42 ` Chao Xu
2013-11-20 3:06 ` Ben Gamari
2013-11-20 18:35 ` Tony Lindgren
2013-11-20 19:17 ` Ben Gamari
2013-11-23 3:27 ` Chao Xu
2013-11-26 18:20 ` Tony Lindgren [this message]
2013-11-26 19:59 ` Chao Xu
2013-11-26 20:26 ` Tony Lindgren
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=20131126182022.GJ26766@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).