From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/7] Broadcom devicetree changes for 4.13 (v2)
Date: Thu, 22 Jun 2017 15:42:29 -0700 [thread overview]
Message-ID: <8f830522-45fb-c86e-0b0e-6af95d793828@gmail.com> (raw)
In-Reply-To: <20170613201044.9808-2-f.fainelli@gmail.com>
On 06/13/2017 01:10 PM, Florian Fainelli wrote:
> The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
>
> Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)
>
> are available in the git repository at:
>
> http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.13/devicetree
>
> for you to fetch changes up to 4a579ecf3d4f964bd6b39605610201cd4d5a7e8e:
>
> Merge tag 'bcm2835-dt-next-2017-06-12' into devicetree/next (2017-06-13 12:38:48 -0700)
>
> ----------------------------------------------------------------
> This pull request contains Broadcom ARM-based Device Tree changes for 4.13.
>
> Note that Baruch's changes are fixes that are currently included in v4.12-rc2,
> but they are also included here in order to keep this tag based off v4.12-rc1.
>
> Please pull the following:
>
> - Rafal adds CPU and thermal zones to the Northstar (BCM5301X) Device Tree and he
> also adds the MDIO controller nodes for later use by USB PHYs
>
> - Eric adds support for the V3D engine and Ethernet switch on the Cygnus
> platforms, he also adds a set of Device Tree sources and include files for the
> Raspberry Pi 3 (BCM2837) to be used with the ARM/Linux kernel,
>
> - Jon adds CPU and thermal zones to the Northstar Plus Device Tree files
>
> - Stefan updates the Raspberry Pi DTS files with thermal trip points and zones,
> adds support for the USB OTG on the Raspberry Pi Zero which includes the
> proper dwc2 configuration, a generic USB PHY and finally the enabling of the
> OTG controller by including the proper DTS include file
>
> - Gerd switches the Raspberry Pi DTS files to use the SDHOST controller (faster
> than the SDHCI)
>
> ----------------------------------------------------------------
Same here:
https://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git/log/?h=brcm/dt
--
Florian
next prev parent reply other threads:[~2017-06-22 22:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 20:10 [GIT PULL 1/7] Broadcom soc changes for 4.13 (v2) Florian Fainelli
2017-06-13 20:10 ` [GIT PULL 2/7] Broadcom devicetree " Florian Fainelli
2017-06-22 22:42 ` Florian Fainelli [this message]
2017-06-13 20:10 ` [GIT PULL 3/7] Broadcom devicetree-arm64 " Florian Fainelli
2017-06-22 22:43 ` Florian Fainelli
2017-06-13 20:10 ` [GIT PULL 4/7] Broadcom maintainers " Florian Fainelli
2017-06-19 3:29 ` Olof Johansson
2017-06-19 7:52 ` Lee Jones
2017-06-13 20:10 ` [GIT PULL 5/7] Broadcom defconfig " Florian Fainelli
2017-06-19 3:29 ` Olof Johansson
2017-06-13 20:10 ` [GIT PULL 6/7] Broadcom defconfig-arm64 " Florian Fainelli
2017-06-19 3:30 ` Olof Johansson
2017-06-13 20:10 ` [GIT PULL 7/7] Broadcom drivers " Florian Fainelli
2017-06-19 3:31 ` Olof Johansson
2017-06-22 22:39 ` [GIT PULL 1/7] 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=8f830522-45fb-c86e-0b0e-6af95d793828@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).