From: Julian Scheel <julian@jusst.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/2] tegra124: Add support for Avionic Design platform
Date: Tue, 23 Feb 2016 20:40:47 +0100 [thread overview]
Message-ID: <56CCB5BF.50503@jusst.de> (raw)
In-Reply-To: <56CC9BAE.4050207@wwwdotorg.org>
On 23.02.16 18:49, Stephen Warren wrote:
> On 02/23/2016 05:59 AM, Julian Scheel wrote:
>> This adds support for the Avionic Design Tegra124 platform. It
>> consists of the
>> Meerkat SOM and a minimal baseboard Kein Baseboard.
>
>> The as3722 is placed on a different bus as compared to nvidia Jetson,
>> which
>> makes the as3722 required.
>
> This doesn't appear to be quite true. It looks like the AS3722 is on the
> same physical bus, it's just that the I2C aliases in DT assign this bus
> a different number. Typically, all Tegra boards have the PMIC I2C bus as
> U-Boot I2C bus 0. Is there a good reason not to do that here?
You are indeed right. I was so sure about it being a different bus that
I did not check it at all...
In fact I don't see a real reason not do reorder the i2c to match the
other platforms. But let me discuss it with Alban before changing.
prev parent reply other threads:[~2016-02-23 19:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 12:59 [U-Boot] [PATCH 0/2] tegra124: Add support for Avionic Design platform Julian Scheel
2016-02-23 12:59 ` [U-Boot] [PATCH 1/2] power: as3722: Allow using on any i2c bus with any address Julian Scheel
2016-02-23 17:51 ` Stephen Warren
2016-02-23 12:59 ` [U-Boot] [PATCH 2/2] Add support the Avionic Design Meerkat COM and Kein Baseboard Julian Scheel
2016-02-23 18:03 ` Stephen Warren
2016-02-23 19:47 ` Julian Scheel
2016-02-29 10:20 ` Julian Scheel
2016-02-29 16:48 ` Stephen Warren
2016-03-02 14:40 ` Thierry Reding
2016-02-23 17:49 ` [U-Boot] [PATCH 0/2] tegra124: Add support for Avionic Design platform Stephen Warren
2016-02-23 19:40 ` Julian Scheel [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=56CCB5BF.50503@jusst.de \
--to=julian@jusst.de \
--cc=u-boot@lists.denx.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