From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/6 v2] Broadcom devicetree-arm64 changes for 4.19
Date: Fri, 13 Jul 2018 07:38:19 -0700 [thread overview]
Message-ID: <20180713143821.1514-4-f.fainelli@gmail.com> (raw)
In-Reply-To: <20180713143821.1514-1-f.fainelli@gmail.com>
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the git repository at:
https://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.19/devicetree-arm64
for you to fetch changes up to e28e681630079204d6d2cb3da1e2c067d21eff64:
arm64: dts: stingray: add bcm958802a802x dts (2018-07-13 07:24:26 -0700)
----------------------------------------------------------------
This pull request contains Broadcom ARM64-based SoCs Device Tree changes
for 4.19, please pull the following:
- Scott does a bunch of updates to the Stingray DTS and DTS include
files to better support the addition of new boards. Scott also adds
the Stingray OTP Device Tree node
- Pramod updates the Stingray clocks such that they match the latest
revision of the ASIC and datasheets
- Ray sets the Stingray initial watchdog timeout to 60 seconds to give
sufficient time for the kernel to boot and then adds PAXC (internal
PCIe) support to the Stingray base DTS files
- Vladimir adds support for the Stingray smart NIC PS225 boards variants
----------------------------------------------------------------
Pramod Kumar (1):
arm64: dts: Update Stingray clock DT nodes
Ray Jui (2):
arm64: dts: set initial SR watchdog timeout to 60 seconds
arm64: dts: stingray: add PAXC support
Scott Branden (2):
arm64: dts: stingray: move common board components to stingray-board-base
arm64: dts: stingray: Add OTP device node
Vladimir Olovyannikov (1):
arm64: dts: stingray: add bcm958802a802x dts
arch/arm64/boot/dts/broadcom/stingray/Makefile | 2 +
.../boot/dts/broadcom/stingray/bcm958742-base.dtsi | 35 +-------------
.../boot/dts/broadcom/stingray/bcm958802a802x.dts | 26 +++++++++++
.../dts/broadcom/stingray/stingray-board-base.dtsi | 51 ++++++++++++++++++++
.../boot/dts/broadcom/stingray/stingray-clock.dtsi | 26 ++++++++---
.../boot/dts/broadcom/stingray/stingray-pcie.dtsi | 54 ++++++++++++++++++++++
.../arm64/boot/dts/broadcom/stingray/stingray.dtsi | 19 ++++++++
7 files changed, 172 insertions(+), 41 deletions(-)
create mode 100644 arch/arm64/boot/dts/broadcom/stingray/bcm958802a802x.dts
create mode 100644 arch/arm64/boot/dts/broadcom/stingray/stingray-board-base.dtsi
create mode 100644 arch/arm64/boot/dts/broadcom/stingray/stingray-pcie.dtsi
next prev parent reply other threads:[~2018-07-13 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 14:38 [GIT PULL 1/6 v2] Broadcom defconfig changes for 4.19 Florian Fainelli
2018-07-13 14:38 ` [GIT PULL 2/6 v2] Broadcom defconfig-arm64 " Florian Fainelli
2018-07-13 14:38 ` [GIT PULL 3/6 v2] Broadcom devicetree " Florian Fainelli
2018-07-13 14:38 ` Florian Fainelli [this message]
2018-07-13 14:38 ` [GIT PULL 5/6 v2] Broadcom drivers " Florian Fainelli
2018-07-13 14:38 ` [GIT PULL 6/6 v2] Broadcom soc " Florian Fainelli
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=20180713143821.1514-4-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).