linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/8] Broadcom devicetree-arm64 changes for 4.6
Date: Sat, 20 Feb 2016 11:46:23 -0800	[thread overview]
Message-ID: <1455997587-17564-4-git-send-email-f.fainelli@gmail.com> (raw)
In-Reply-To: <1455997587-17564-1-git-send-email-f.fainelli@gmail.com>

  Linux 4.5-rc1 (2016-01-24 13:06:47 -0800)

are available in the git repository at:

  http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.6/devicetree-arm64

for you to fetch changes up to f008decc4797979bc1d3b8efd18bd5df1e53e9f0:

  dt-bindings: Add documentation for Broadcom Vulcan (2016-02-20 10:42:51 -0800)

----------------------------------------------------------------
This pull request contains Broadcom ARM64-based SoCs device tree changes:

- Anup adds additional nodes to the Broadcom Northstart 2 Device Trees: SDHCI
  (iProc-compatible), ARM SP804 timers, ARM SP805 watchdog

- Anup also adds a binding documentation for the ARM SP805 watchdog since there
  was not one in tree before

- Ray adds PCIE root complex nodes to the Northstar 2 Device Tree nodes, using
  the iProc-compatible binding

- Jayachandran C. adds binding documentation for the Broadcom Vulcan processors and
  reference platforms

----------------------------------------------------------------
Anup Patel (4):
      arm64: dts: Add SDHCI DT node for NS2
      arm64: dts: Add ARM SP804 timer DT nodes for NS2
      dt-bindings: watchdog: Add ARM SP805 DT bindings
      arm64: dts: Add ARM SP805 watchdog DT node for NS2

Jayachandran C (1):
      dt-bindings: Add documentation for Broadcom Vulcan

Ray Jui (1):
      arm64: dts: Add PCIe0 and PCIe4 DT nodes for NS2

 .../bindings/arm/bcm/brcm,vulcan-soc.txt           |  10 ++
 Documentation/devicetree/bindings/arm/cpus.txt     |   1 +
 .../devicetree/bindings/watchdog/arm,sp805.txt     |  17 +++
 arch/arm64/boot/dts/broadcom/ns2-svk.dts           |  12 ++
 arch/arm64/boot/dts/broadcom/ns2.dtsi              | 140 +++++++++++++++++++++
 5 files changed, 180 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,vulcan-soc.txt
 create mode 100644 Documentation/devicetree/bindings/watchdog/arm,sp805.txt

  parent reply	other threads:[~2016-02-20 19:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-20 19:46 [GIT PULL 1/8] Broadcom soc changes for 4.6 Florian Fainelli
2016-02-20 19:46 ` [GIT PULL 2/8] Broadcom soc-arm64 " Florian Fainelli
2016-02-20 19:46 ` [GIT PULL 3/8] Broadcom devicetree " Florian Fainelli
2016-02-20 19:46 ` Florian Fainelli [this message]
2016-02-20 19:46 ` [GIT PULL 5/8] Broadcom maintainers " Florian Fainelli
2016-02-20 19:46 ` [GIT PULL 6/8] Broadcom maintainers-arm64 " Florian Fainelli
2016-02-20 19:46 ` [GIT PULL 7/8] Broadcom defconfig " Florian Fainelli
2016-02-20 19:46 ` [GIT PULL 8/8] Broadcom defconfig-arm64 " Florian Fainelli
2016-02-26 23:00 ` [GIT PULL 1/8] Broadcom soc " 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=1455997587-17564-4-git-send-email-f.fainelli@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).