From: Stephen Warren <swarren@wwwdotorg.org>
To: Matthias Klein <matthias.klein@linux.com>
Cc: linux-rpi-kernel@lists.infradead.org, lee@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ARM: bcm2835: add device tree for Raspberry Pi model B+
Date: Wed, 05 Nov 2014 22:29:02 -0700 [thread overview]
Message-ID: <545B071E.7090007@wwwdotorg.org> (raw)
In-Reply-To: <1415231123-920-1-git-send-email-matthias.klein@linux.com>
On 11/05/2014 04:45 PM, Matthias Klein wrote:
> The model B and B+ differ in the GPIO lines for ACT and PWR leds, and the
> I2S interface.
BTW, according to:
http://raspberryalphaomega.org.uk/2013/02/06/automatic-raspberry-pi-board-revision-detection-model-a-b1-and-b2/
... there are actually 2 different HW configurations we care about for
the pre-plus Pis:
B rev 1
A, or B rev 2
I guess we should have separate device trees for those, since there are
some differences in the GPIO and I2C channel usage. That'd leave us with:
bcm2835-rpi-b.dts (Pin3=GPIO0, Pin5=GPIO1, Pin13=GPIO21, I2C-0)
bcm2835-rpi-b-rev2.dts (Pin3=GPIO1, Pin5=GPIO2, Pin13=GPIO27, 12C-1)
bcm2835-rpi-b-plus.dts (TBD pending schematic or equivalent info)
... and probably another for the compute board.
We can ignore RAM size differences, since these are automatically filled
into the /memory node in DT. I'm not sure if A-vs-B-rev-1 is
interesting. Perhaps we should have separate DTs just in case, since we
may need to represent the LAN_RUN GPIO in DT at some point, and that
only applies to the B.
Presumably, the boot loader would automatically query the VC firmware
for the board revision data, and dynamically load the appropriate DT
filename.
Any thoughts or objections?
next prev parent reply other threads:[~2014-11-06 5:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 23:45 [PATCH v2] ARM: bcm2835: add device tree for Raspberry Pi model B+ Matthias Klein
2014-11-06 5:11 ` Stephen Warren
2014-11-06 5:29 ` Stephen Warren [this message]
2014-11-06 18:15 ` Matthias Klein
2014-11-06 19:01 ` Stephen Warren
2014-11-06 19:36 ` Noralf Tronnes
2014-11-07 4:22 ` Stephen Warren
2014-11-07 16:20 ` Noralf Tronnes
[not found] ` <CAE8Q9tBDxq9W=Vh0LRCRNR+Dj+5PrWyzK+GBdMDM=1kq84mFTA@mail.gmail.com>
2014-11-07 17:12 ` Gordon Hollingworth
2014-11-08 6:17 ` Stephen Warren
2014-11-08 8:03 ` Gordon Hollingworth
2014-11-08 6:12 ` Stephen Warren
2014-11-19 15:29 ` Lee Jones
2014-11-19 17:08 ` Stephen Warren
2014-11-19 17:29 ` Lee Jones
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=545B071E.7090007@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=matthias.klein@linux.com \
/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;
as well as URLs for NNTP newsgroup(s).