mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Michael Burkey <mdburkey@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Porting barebox (devicetree) to Variscite iMX6 SOM
Date: Wed, 18 Dec 2013 11:39:57 -0500	[thread overview]
Message-ID: <CAJyuEeejqixPzCez0EZU9hhQkO3f8yvpARLGLwPgQUfGBASZug@mail.gmail.com> (raw)
In-Reply-To: <CAJyuEecPnTHU2rTgJzkvkv3p56f32jqaS1aQykn91TNGvcUawg@mail.gmail.com>

Variscite SOM...the saga continues.

First off, I now have the serial console up (more or less -- more on
this in a second), but it's not accepting input and I have other
issues.

My questions:

1) When using devicetree inside barebox, does a built-in devicetree
get automatically enumerated and probed?
2) At what point in the boot process do devices specified in
devicetree become available? (specifically, the I2C bus support)
3) Is there any voltage regulator support in barebox? I notice on some
of the i.MX6 SOM's that the PF0100 is specified and configured, but
I'm not actually seeing any driver code in barebox itself that
accesses it (unless I'm overlooking it). I assume the voltage
regulator definitions are just for pushing upstream when booting a
kernel?


What I am running into is that the Variscite SOM uses the 3.3V output
of the PF0100 voltage regulator as a "power good" signal that brings
up the 3.3V rail on their development board -- which, among other
things, powers the RS232 transceiver that the debug port connects to
(which is the reason I get output, but no input). It also powers the
USB hub on the board, which is also fairly important.

So, basically, I'm trying to figure out the proper way to configure
I2C devices early in the barebox boot sequence when using devicetree.
I know how to do it the old-fashioned way in the board file (which I
have done before).

Thanks,
Michael Burkey

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2013-12-18 16:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 17:07 Michael Burkey
2013-12-11 23:17 ` Alexander Aring
2013-12-12  8:04 ` Sascha Hauer
2013-12-12 18:49   ` Michael Burkey
2013-12-12 18:56     ` Michael Burkey
2013-12-12 19:12       ` Alexander Aring
2013-12-12 19:24         ` Michael Burkey
2013-12-12 19:58     ` Sascha Hauer
2013-12-12 22:44       ` Michael Burkey
2013-12-18 16:39         ` Michael Burkey [this message]
2013-12-18 21:34           ` Michael Burkey
2013-12-19  8:09             ` Sascha Hauer
2014-01-09  7:20               ` Michael Burkey
2014-01-09 19:59                 ` Michael Burkey
2014-01-10  8:00                   ` Sascha Hauer
2014-01-10  8:13                 ` Sascha Hauer
2014-01-15 18:35                   ` Michael Burkey
2014-01-16 14:13                     ` Sascha Hauer
2014-01-16 21:18                       ` Michael Burkey
2014-01-20  8:00                         ` Sascha Hauer
2014-01-29 21:10                           ` Michael Burkey
2014-01-29 21:53                             ` Michael Burkey
2014-02-01 18:35                             ` Sascha Hauer
2014-02-04 21:44                               ` Michael D. Burkey

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=CAJyuEeejqixPzCez0EZU9hhQkO3f8yvpARLGLwPgQUfGBASZug@mail.gmail.com \
    --to=mdburkey@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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