From: Florian Fainelli <f.fainelli@gmail.com>
To: arm@kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
arnd@arndb.de, Scott Branden <scott.branden@broadcom.com>,
Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>,
khilman@kernel.org, Pramod Kumar <pramod.kumar@broadcom.com>,
Srinath Mannam <srinath.mannam@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com, olof@lixom.net,
Ray Jui <ray.jui@broadcom.com>,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/6] Broadcom devicetree-arm64 changes for 5.3
Date: Tue, 11 Jun 2019 19:50:24 -0700 [thread overview]
Message-ID: <20190612025028.13118-2-f.fainelli@gmail.com> (raw)
In-Reply-To: <20190612025028.13118-1-f.fainelli@gmail.com>
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the Git repository at:
https://github.com/Broadcom/stblinux.git tags/arm-soc/for-5.3/devicetree-arm64
for you to fetch changes up to f8526c2d99ca87ccbc0a3da00555d6d08e25d058:
arm64: dts: Stingray: Add NIC i2c device node (2019-05-20 09:31:35 -0700)
----------------------------------------------------------------
This pull request contains Broadcom ARM64-based SoCs Device Tree changes
for 5.3, please pull the following:
- Pramod adds the Device Tree nodes for thermal support on Stingray
- Srinath adds the Device Tree nodes for both XHCI (host) and BDC
(device) modes
- Rayagonda adds the Device Tree node for slave I2C operation when
Stingray operates as a SmartNIC
----------------------------------------------------------------
Pramod Kumar (1):
arm64: dts: stingray: Add Stingray Thermal DT support.
Rayagonda Kokatanur (1):
arm64: dts: Stingray: Add NIC i2c device node
Srinath Mannam (1):
arm64: dts: Add USB DT nodes for Stingray SoC
.../boot/dts/broadcom/stingray/stingray-usb.dtsi | 72 ++++++++++++++
.../arm64/boot/dts/broadcom/stingray/stingray.dtsi | 108 +++++++++++++++++++++
2 files changed, 180 insertions(+)
create mode 100644 arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-12 2:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 2:50 [GIT PULL 1/6] Broadcom devicetree changes for 5.3 Florian Fainelli
2019-06-12 2:50 ` Florian Fainelli [this message]
2019-06-19 13:25 ` [GIT PULL 2/6] Broadcom devicetree-arm64 " Olof Johansson
2019-06-12 2:50 ` [GIT PULL 3/6] Broadcom drivers " Florian Fainelli
2019-06-17 11:53 ` Olof Johansson
2019-06-12 2:50 ` [GIT PULL 4/6] Broadcom maintainers " Florian Fainelli
2019-06-19 16:10 ` Olof Johansson
2019-06-12 2:50 ` [GIT PULL 5/6] Broadcom soc " Florian Fainelli
2019-06-12 2:50 ` [GIT PULL 6/6] Broadcom soc-arm64 " Florian Fainelli
2019-06-17 12:16 ` Olof Johansson
2019-06-19 13:35 ` [GIT PULL 1/6] Broadcom devicetree " Olof Johansson
2019-06-23 2:22 ` Florian Fainelli
2019-06-25 11:17 ` Olof Johansson
2019-06-23 3:29 ` [GIT PULL 1/6 v2] Broadcom devicetree changes for 5.2 Florian Fainelli
2019-06-25 11:16 ` Olof Johansson
2019-06-25 12:56 ` Olof Johansson
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=20190612025028.13118-2-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
--cc=pramod.kumar@broadcom.com \
--cc=ray.jui@broadcom.com \
--cc=rayagonda.kokatanur@broadcom.com \
--cc=scott.branden@broadcom.com \
--cc=srinath.mannam@broadcom.com \
/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).