From: Mark Brown <broonie@kernel.org>
To: Frank Rowand <frowand.list@gmail.com>
Cc: Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Rob Herring <robh+dt@kernel.org>,
david@gibson.dropbear.id.au, stephen.boyd@linaro.org,
grant.likely@secretlab.ca, Mark Rutland <mark.rutland@arm.com>,
mporter@konsulko.com, Koen Kooi <koen@dominion.thruhere.net>,
Guenter Roeck <linux@roeck-us.net>,
marex@denx.de, Wolfram Sang <wsa@the-dreams.de>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org, panto@antoniou-consulting.com
Subject: Re: portable device tree connector -- problem statement
Date: Tue, 5 Jul 2016 10:31:52 +0200 [thread overview]
Message-ID: <20160705083152.GM6247@sirena.org.uk> (raw)
In-Reply-To: <577ACE0D.9050700@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-07-05 8:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 20:58 Frank Rowand
2016-07-05 8:31 ` Mark Brown [this message]
2016-07-05 14:24 ` Frank Rowand
2016-07-05 18:07 ` Pantelis Antoniou
2016-07-05 18:04 ` Pantelis Antoniou
2016-07-18 14:20 ` DT connectors, thoughts David Gibson
2016-07-20 20:59 ` Pantelis Antoniou
2016-07-21 13:42 ` David Gibson
2016-07-21 14:14 ` Pantelis Antoniou
2016-07-21 19:09 ` Rob Herring
2016-07-21 19:15 ` Pantelis Antoniou
2016-07-21 19:21 ` Rob Herring
2016-07-22 4:16 ` David Gibson
2016-07-22 3:47 ` David Gibson
2016-07-22 3:46 ` David Gibson
2016-07-20 20:59 ` Pantelis Antoniou
2016-07-21 19:15 ` Rob Herring
2016-07-22 4:25 ` David Gibson
2016-08-26 1:38 ` Stephen Boyd
2016-08-29 13:45 ` David Gibson
[not found] ` <147252286938.20899.1763773530822329216@sboyd-linaro>
2016-08-30 23:55 ` David Gibson
[not found] ` <147329189889.27412.12053595745294007737@sboyd-linaro>
2016-09-08 0:26 ` David Gibson
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=20160705083152.GM6247@sirena.org.uk \
--to=broonie@kernel.org \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=koen@dominion.thruhere.net \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=marex@denx.de \
--cc=mark.rutland@arm.com \
--cc=mporter@konsulko.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=panto@antoniou-consulting.com \
--cc=robh+dt@kernel.org \
--cc=stephen.boyd@linaro.org \
--cc=wsa@the-dreams.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
all inboxes | Powered by JetHome®