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: devicetree support for efikasb
Date: Wed, 19 Dec 2012 09:56:43 +0100	[thread overview]
Message-ID: <20121219085643.GW26326@pengutronix.de> (raw)
In-Reply-To: <87fw3364au.fsf@lebrac.rtp-net.org>

On Tue, Dec 18, 2012 at 11:30:17AM +0100, Arnaud Patard wrote:
> Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org> writes:
> Hi,
> 
> 
> >>
> >>> 
> >>> >
> >>> > I'm not posting the patches here since I do not consider them ready, but
> >>> > for everyone interested you can pull the following git tree. I have no
> >>> > idea if the patches work together with the preinstalled U-Boot, I use
> >>> > barebox on the Smartbook.
> >>> 
> >>> I've (very quickly) tested it yesterday and it didn't even boot. I've
> >>> yet to look at the serial port output to check if it's a problem on my
> >>> side or a bug in the kernel.
> >>
> >> Do you mean barebox doesn't boot or the kernel doesn't boot?
> >
> > No idea. All I get is a black screen, so I need to look at the serial
> > output. Oh, it's uboot not barebox btw. Sorry for the confusion.
> 
> After digging a little bit, turns out that someone failed to make sure
> that clocks are enabled before reading/writing some
> registers. imx51_ipu_mipi_setup() is called very early in the boot and
> it's way before the clocks are enabled. So, as the clock is not enabled
> when booting on my sb, it's freezing hard. A quick hack to move the call
> to the end of mx51_clocks_init() allows to boot.

Shawn already noticed this. A fix should appear soon in mainline.

> 
> Then, I'm getting a oops. i2c doesn't seem to work (maybe related to
> Matt and Steev remarks about pinctrl settings) so the edid is not found
> and when the mtl017 driver is trying to fall back, it falls back the the
> edid which may be provided by the dts. As it's not the case, it's
> crashing at the memcmp() call. With a new test to check that, I can boot
> on my mmc.
> 
> PATA is detected too but usb doesn't detect anything on the bus.
> 
> Next steps will probably be something like checking mtl017/lvds,lcd
> gpios/regulators/pinctrl and then look at usb.

This is probably because I'm using barebox. The i2c pinmux is probably
configured in the bootloader correctly. That should be easy to fix.
USB may be more work though...

> 
> Oh, btw, the smartbook have only 512M of ram, not 1G so you need to fix
> that in your dts file.

Will do. The bootloader fixes that for me currently, so I didn't realize
this.

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 |

  reply	other threads:[~2012-12-19  8:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17  7:59 devicetree support for efikasb Sascha Hauer
2012-12-17  8:21 ` Peter Korsgaard
2012-12-17 11:27 ` Arnaud Patard (Rtp)
2012-12-17 11:50   ` Sascha Hauer
2012-12-17 12:04     ` Arnaud Patard (Rtp)
2012-12-18 10:30       ` Arnaud Patard (Rtp)
2012-12-19  8:56         ` Sascha Hauer [this message]
2012-12-20 16:34           ` Steev Klimaszewski
2012-12-25  2:49             ` Matt Sealey
2012-12-18  1:12     ` Matt Sealey
2012-12-17 12:37   ` Peter Korsgaard
2012-12-17 14:07     ` Arnaud Patard (Rtp)
2012-12-17 14:24       ` Peter Korsgaard
2012-12-17 14:30         ` Samuel Thibault
2012-12-17 14:40           ` Peter Korsgaard

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=20121219085643.GW26326@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).