From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] bcm2835 DT changes for 4.6
Date: Fri, 12 Feb 2016 20:00:23 -0800 [thread overview]
Message-ID: <56BEAA57.3050600@gmail.com> (raw)
In-Reply-To: <877fi92zxb.fsf@eliezer.anholt.net>
On 12/02/2016 16:53, Eric Anholt wrote:
> Florian Fainelli <f.fainelli@gmail.com> writes:
>
>> On 10/02/2016 10:51, Eric Anholt wrote:
>>> Martin Sperl <martin@sperl.org> writes:
>>>
>>>>> On 09.02.2016, at 01:32, Eric Anholt <eric@anholt.net> wrote:
>>>>>
>>>>> Hi Florian. Here's the first set of patches for bcm2835 for 4.6.
>>>>> We've got more DT patches that are going to happen for new boards,
>>>>> too, but they're still getting polished.
>>>>>
>>>>> The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d:
>>>>>
>>>>> Linux 4.5-rc1 (2016-01-24 13:06:47 -0800)
>>>>>
>>>>> are available in the git repository at:
>>>>>
>>>>> git at github.com:anholt/linux.git tags/bcm2835-dt-next-2016-02-04
>>>>>
>>>>> for you to fetch changes up to 5ec6f2cd8ec4bcd38ba199ea8711a5ec906d85e7:
>>>>>
>>>>> ARM: bcm2835: Add the Raspberry Pi power domain driver to the DT. (2016-02-02 20:02:45 -0800)
>>>>>
>>>>> ----------------------------------------------------------------
>>>>> This pull request covers mostly DT changes that didn't make it into
>>>>> 4.5 because required header files went through other trees.
>>>>>
>>>>> ----------------------------------------------------------------
>>>>> Alexander Aring (1):
>>>>> ARM: bcm2835: Add the Raspberry Pi power domain driver to the DT.
>>>>>
>>>>> Lubomir Rintel (1):
>>>>> ARM: bcm2835: dt: Add Raspberry Pi Model A
>>>>>
>>>>> Martin Sperl (2):
>>>>> ARM: bcm2835: add the auxiliary spi1 and spi2 to the device tree
>>>>> ARM: bcm2835: follow dt uart node-naming convention
>>>>
>>>> Do you want me to resend a rebased version of:
>>>> ARM: bcm2835: add bcm2835-aux-uart support to default DT
>>>>
>>>> The corresponding driver has been added to tty/tty-next.
>>>
>>> It hadn't landed last time I checked. A rebased version that you've
>>> tested would be great!
>>
>> OK, please submit this in the next week or so at most, so we can get
>> this pull request merged, thanks!
>>
>> Eric, do you have other changes outside of Device Tree?
>
> We've got bcm2835_defconfig changes that I need to test and tag.
Ok, so that one needs to be a pull request.
>
> There are also the multi_v7_defconfig updates to enable bcm2835. Would
> I be pulling those, or someone above me?
This one could too, or it could be an individual patch that the arm-soc
maintainers take directly, either way is fine AFAIR.
--
Florian
next prev parent reply other threads:[~2016-02-13 4:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 0:32 [GIT PULL] bcm2835 DT changes for 4.6 Eric Anholt
2016-02-10 16:39 ` Martin Sperl
2016-02-10 18:51 ` Eric Anholt
2016-02-12 3:46 ` Florian Fainelli
2016-02-13 0:53 ` Eric Anholt
2016-02-13 4:00 ` Florian Fainelli [this message]
2016-02-18 2:57 ` Eric Anholt
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=56BEAA57.3050600@gmail.com \
--to=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).