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

On Monday, November 21, 2016 9:48:21 PM CET Florian Fainelli wrote:
> This pull request contains Broadcom ARM64 based SoC Device Tree changes for
> 4.10, please pull the following:
> 
> - Robin updates the Northstart 2 DTS to use the generic IOMMU binding
> 
> - Scott renames the Broadcom Northstar 2 binding document to use a standard name
>   including the brcm vendor prefix
> 
> - Kamal adds the QSPI Device Tree node to the Northstar 2 SoC and updates the
>   Northstar 2 SVK reference board DTS file with it enabled.
> 
> - Rob adds the Device Tree node for the Broadcom PDC (mailbox) hardware to the
>   Northstar 2 SoC
> 
> - Jon enables the SDIO1 block and adds proper PCIe PHYs Device Tree nodes to the
>   Northstar 2 SoC
> 
> - Ray adds required properties NAND controller properties to make NAND work on
>   the Northstar 2 SVK board, this was submitted as a 4.9 fixes and is included
>   here to resolve DTS file merges
> 
> - Andrea removes an incorrect power LED from the Raspberry Pi 3 DTS
> 
> - Andreas fixes the compatible string for the BCM2837 (Raspberry Pi 3)
> 
> - 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 uses the proper DTSI file to define the USB host mode
>   for the USB Device Tree nodes
> 
> 

Pulled into next/dt64, thanks!

	Arnd

  reply	other threads:[~2016-11-30 17:00 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
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 [this message]
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=6243216.EMKdABgK8f@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.