From: Thierry Reding <treding@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] Add support the Avionic Design Meerkat COM and Kein Baseboard
Date: Wed, 2 Mar 2016 15:40:04 +0100 [thread overview]
Message-ID: <20160302144003.GA2316@ulmo.nvidia.com> (raw)
In-Reply-To: <56D47655.5030806@wwwdotorg.org>
On Mon, Feb 29, 2016 at 09:48:21AM -0700, Stephen Warren wrote:
> On 02/29/2016 03:20 AM, Julian Scheel wrote:
> >Hi Stephen,
> >
> >On 23.02.2016 19:03, Stephen Warren wrote:
> >>On 02/23/2016 05:59 AM, Julian Scheel wrote:
> >>>Add support for platforms based on the Meerkat COM module. Includes
> >>>support
> >>>for the minimal reference platform called Kein Baseboard, which in
> >>>fact is
> >>>sufficient to run most existing Meerkat carriers.
> >>
> >>>diff --git a/arch/arm/dts/tegra124-meerkat.dtsi
> >>>b/arch/arm/dts/tegra124-meerkat.dtsi
> >>
> >>>+ aliases {
> >>>+ i2c0 = "/i2c at 7000c000";
> >>>+ i2c1 = "/i2c at 7000c400";
> >>>+ i2c2 = "/i2c at 7000c500";
> >>>+ i2c3 = "/i2c at 7000c700";
> >>>+ i2c4 = "/i2c at 7000d000";
> >>>+ i2c5 = "/i2c at 7000d100";
> >>
> >>/i2c at 7000d000 is alias i2c0 on all other Tegra boards that have I2C
> >>aliases.
> >
> >we just had a quick discussion about this and actually we explicitly
> >changed it in our tree to a linear mapping of the controller addresses
> >to be in sync with what we have in the l4t kernel.
> >If it won't hurt you too much we'd like to keep it that way. Though if
> >you feel really bad about it, we can change it to use the same mapping
> >as Jetson uses.
>
> That's probably fine; hopefully it won't be too confusing since aliases are
> supposed to be board-specific.
>
> Let's make sure that the Linux kernel patches for this board have matching
> aliases and get Ack'd soon to make sure they don't diverge.
I don't mind having the mapping like this for Meerkat. For anything in
kernel space this should be completely irrelevant since the association
is done via parent-child relationships in DT anyway.
The only place where the numbering matters is if you want to use the I2C
busses from userspace (using i2c-dev) and in that case you're probably
better off if you use some sort of lookup mechanism to find the correct
I2C bus based on the MMIO address, instead of relying on hardcoded bus
numbers.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160302/00f3a3fd/attachment.sig>
next prev parent reply other threads:[~2016-03-02 14: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 [this message]
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
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=20160302144003.GA2316@ulmo.nvidia.com \
--to=treding@nvidia.com \
--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