From: Stephen Warren <swarren@wwwdotorg.org>
To: Lee Jones <lee@kernel.org>, Matthias Klein <matthias.klein@linux.com>
Cc: linux-rpi-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ARM: bcm2835: add device tree for Raspberry Pi model B+
Date: Wed, 19 Nov 2014 10:08:03 -0700 [thread overview]
Message-ID: <546CCE73.4020708@wwwdotorg.org> (raw)
In-Reply-To: <20141119152951.GA1875@x1>
On 11/19/2014 08:29 AM, Lee Jones wrote:
>> The model B and B+ differ in the GPIO lines for ACT and PWR leds, and the
>> I2S interface.
>>
>> Signed-off-by: Matthias Klein <matthias.klein@linux.com>
>> ---
>> Changes in v2:
>> - move the common parts between the B and B+ model into the new bcm2835-rpi.dtsi file
>>
>> - add the I2S signals to the B+ file which fix the problem that USB is not working
>> with the current bcm2835-rpi-b.dts file on the B+.
>> ---
>> arch/arm/boot/dts/Makefile | 1 +
>> arch/arm/boot/dts/bcm2835-rpi-b-plus.dts | 30 +++++++++++++++++++
>> arch/arm/boot/dts/bcm2835-rpi-b.dts | 46 ++--------------------------
>> arch/arm/boot/dts/bcm2835-rpi.dtsi | 51 ++++++++++++++++++++++++++++++++
>> 4 files changed, 85 insertions(+), 43 deletions(-)
>> create mode 100644 arch/arm/boot/dts/bcm2835-rpi-b-plus.dts
>> create mode 100644 arch/arm/boot/dts/bcm2835-rpi.dtsi
>
> Sorry for the delay. I thought RPi world was exceptionally quiet, but
> in fact I had issues with my newly setup mailbox and filters. All
> rectified now in any case.
>
> It might be worth noting that this will not likely land in v3.19, as
> we are one step removed from Linus (i.e. via ARM SoC) and they usually
> like to have pull-requests in by -rc5. Unless anyone stamps their
> feet, I'll be sending this no sooner than v3.20.
-rc6 is the usual cut-off, and the arm-soc maintainers have said that's
not always a very strict cut-off; it depends on how invasive the patch
is (which this isn't) and whether the patch has been in linux-next
already before getting into arm-soc (and linux-rpi.git's for-next branch
is in linux-next).
next prev parent reply other threads:[~2014-11-19 17:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 23:45 Matthias Klein
2014-11-06 5:11 ` Stephen Warren
2014-11-06 5:29 ` Stephen Warren
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 [this message]
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=546CCE73.4020708@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
Powered by JetHome