linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: Booting mx31 on linux-next-20120517
Date: Fri, 18 May 2012 10:59:22 +0200	[thread overview]
Message-ID: <20120518085922.GQ30400@pengutronix.de> (raw)
In-Reply-To: <CAOMZO5BUBAcx9ESLau9b4osE3jQNnh1CXW7FgkmbQ1aS57bOCg@mail.gmail.com>

On Fri, May 18, 2012 at 01:07:07AM -0300, Fabio Estevam wrote:
> On Fri, May 18, 2012 at 12:48 AM, Fabio Estevam <festevam@gmail.com> wrote:
> > Hi Sascha,
> >
> > Are you able to boot any mx31 system on linux-next-20120517?
> >
> > Just wanted to check with you first before start debugging this issue.
> 
> Adding earlyprintk shows me the following:

Looks familiar. Check the pinctrl support. The i.MX UART driver (and
also the FEC driver) do a devm_pinctrl_get_select_default which does
not seem to be complete. Either the pinctrl dummy providers did not make
it to -next yet or they are simply not activated.


Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  parent reply	other threads:[~2012-05-18  8:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-18  3:48 Booting mx31 on linux-next-20120517 Fabio Estevam
2012-05-18  4:07 ` Fabio Estevam
2012-05-18  6:00   ` Uwe Kleine-König
2012-05-18  6:16     ` Dirk Behme
2012-05-18  8:59   ` Sascha Hauer [this message]
2012-05-21 13:20     ` Fabio Estevam
2012-05-21 13:33       ` Philippe Rétornaz
2012-05-21 13:35         ` Fabio Estevam
2012-05-23 15:49           ` Shawn Guo
2012-05-23 15:59             ` Fabio Estevam
2012-05-18 14:02 ` Philippe Rétornaz

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=20120518085922.GQ30400@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --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).