linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/6] Broadcom devicetree changes for 4.10
Date: Wed, 30 Nov 2016 17:55:00 +0100	[thread overview]
Message-ID: <6352823.Z1eXLgpRkV@wuerfel> (raw)
In-Reply-To: <20161122054824.16974-2-f.fainelli@gmail.com>

On Monday, November 21, 2016 9:48:20 PM CET Florian Fainelli wrote:
> This pull request contains Broadcom ARM-based SoC Device Tree changes for 4.10,
> please pull the following:
> 
> - Rafal adds support for the Netgear R8500 routers, adds basic support
>   for the Tenda AC9 router which uses the new BCM53573 SoC (single core Cortex
>   A7). He also enables the UART on the Netgear R8000 and restructures the
>   include files a bit for the BCM47094 SoC, finally he adds USB 3.0 PHY nodes
>   which enables USB 3.0 on BCM5301X devices that support it. Finally he adds
>   support for the TP-LINK Archer C9 V1 router.
> 
> - Kamal adds support for the QSPI controller on the Northstar Plus SoCs and updates
>   the bcm958625k reference board to have it enabled
> 
> - Dan adds support for the Luxul XAP-1510 (using a BCM4708) and XWR-3100 (using
>   a BCM47094)
> 
> - Scott fixes the pinctrl names in the Cygnus DTS files
> 
> - Jonathan enables the Broadcom iProc mailbox controller for Broadcom Cygnus/iProc
>   SoCs, he adds interrupt support for the GPIO CRMU hardware block and finally adds
>   the node for the OTP controller found on Cygnus SoCs
> 
> - Dhananjay enables the GPIO B controller on Norstarh Plus SoCs
> 
> - Eric defines standard pinctrl groups in the BCM2835 GPIO node
> 
> - Gerd adds definitions for the pinctrl groups and updates the PWM, I2C and SDHCI nodes
>   to use their appropriate pinctrl functions
> 
> - Linus adds names for the Raspberry Pi GPIO lines based on the datasheet
> 
> - Martin adds the DT binding and nodes for the Raspberry Pi firmware thermal block
> 
> - Stefan fixes a few typos with respect to the BCM2835 mailbox binding example and
>   Device Tree nodes he also fixes the Raspberry Pi GPIO lines names and finally
>   adds names for the Raspberry Zero GPIO lines
> 

Pulled into next/dt, thanks!

	Arnd

  reply	other threads:[~2016-11-30 16:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22  5:48 [GIT PULL 1/6] Broadcom soc changes for 4.10 Florian Fainelli
2016-11-22  5:48 ` [GIT PULL 2/6] Broadcom devicetree " Florian Fainelli
2016-11-30 16:55   ` Arnd Bergmann [this message]
2016-11-30 21:27   ` Arnd Bergmann
2016-11-30 21:44     ` Florian Fainelli
2016-11-22  5:48 ` [GIT PULL 3/6] Broadcom devicetree-arm64 " Florian Fainelli
2016-11-30 17:00   ` Arnd Bergmann
2016-11-22  5:48 ` [GIT PULL 4/6] Broadcom maintainers-arm64 " Florian Fainelli
2016-11-30 21:20   ` Arnd Bergmann
2016-11-22  5:48 ` [GIT PULL 5/6] Broadcom defconfig " Florian Fainelli
2016-11-30 21:22   ` Arnd Bergmann
2016-11-22  5:48 ` [GIT PULL 6/6] Broadcom defconfig-arm64 " Florian Fainelli
2016-11-30 21:23   ` Arnd Bergmann
2016-11-30 16:52 ` [GIT PULL 1/6] Broadcom soc " Arnd Bergmann
2016-12-01 11:18   ` Rafał Miłecki
2016-12-01 11:35     ` Arnd Bergmann

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=6352823.Z1eXLgpRkV@wuerfel \
    --to=arnd@arndb.de \
    --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).