[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160705083152.GM6247@sirena.org.uk>
Date: Tue, 5 Jul 2016 10:31:52 +0200
From: Mark Brown <broonie@...nel.org>
To: Frank Rowand <frowand.list@...il.com>
Cc: Pantelis Antoniou <pantelis.antoniou@...sulko.com>,
Rob Herring <robh+dt@...nel.org>, david@...son.dropbear.id.au,
stephen.boyd@...aro.org, grant.likely@...retlab.ca,
Mark Rutland <mark.rutland@....com>, mporter@...sulko.com,
Koen Kooi <koen@...inion.thruhere.net>,
Guenter Roeck <linux@...ck-us.net>, marex@...x.de,
Wolfram Sang <wsa@...-dreams.de>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-i2c@...r.kernel.org,
panto@...oniou-consulting.com
Subject: Re: portable device tree connector -- problem statement
On Mon, Jul 04, 2016 at 01:58:53PM -0700, Frank Rowand wrote:
> On the other hand, I have no previous detailed knowledge of the beagle
> family.
This is in no way specific to the BeagleBones, there's plenty of other
boards out there with similar setups like the Raspberry Pi and its
derivatives.
> - for bones with the same pinout:
> - the pins are routed to different function blocks on the
> SOC because different bones may have different SOCs?
> - the different functional blocks are compatible or not?
This is the general case, there will be a substantial level of
compatibility between different base boards by virtue of the pinouts
being the same but obviously there will be some variation in the
specifics (and even where that exists it may not be enough to be visible
at the DT level for the most part). That said there will doubtless be
some plug in modules that want to rely on the specifics of a given base
board rather than remain compatible with general users of the interface.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists