From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Broadcom Cygnus SoC Device Tree changes
Date: Thu, 30 Oct 2014 12:50:10 -0700 [thread overview]
Message-ID: <1414698612-26216-2-git-send-email-f.fainelli@gmail.com> (raw)
In-Reply-To: <1414698612-26216-1-git-send-email-f.fainelli@gmail.com>
The following changes since commit f114040e3ea6e07372334ade75d1ee0775c355e1:
Linux 3.18-rc1 (2014-10-19 18:08:38 -0700)
are available in the git repository at:
http://github.com/brcm/linux.git tags/arm-soc/for-3.18/cygnus-dts-v9
for you to fetch changes up to 8872fc22c2670cde338ab92be4a8e9ebad8e53e6:
ARM: dts: Enable Broadcom Cygnus SoC (2014-10-30 11:05:55 -0700)
----------------------------------------------------------------
This patchset contains initial support for Broadcom's Cygnus SoC based on our
iProc architecture. Initial support is minimal and includes just the mach
platform code, clock driver, and a basic device tree configuration. Peripheral
drivers will be submitted soon, as will device tree configurations for other
Cygnus board variants.
These are the Device Tree changes
----------------------------------------------------------------
Jonathan Richardson (1):
dt-bindings: Document Broadcom Cygnus SoC and clocks
Scott Branden (1):
ARM: dts: Enable Broadcom Cygnus SoC
.../devicetree/bindings/arm/bcm/cygnus.txt | 31 +++++++
.../devicetree/bindings/clock/bcm-cygnus-clock.txt | 34 +++++++
arch/arm/boot/dts/Makefile | 4 +
arch/arm/boot/dts/bcm-cygnus-clock.dtsi | 73 +++++++++++++++
arch/arm/boot/dts/bcm-cygnus.dtsi | 100 +++++++++++++++++++++
arch/arm/boot/dts/bcm911360_entphn.dts | 32 +++++++
arch/arm/boot/dts/bcm911360k.dts | 32 +++++++
arch/arm/boot/dts/bcm958300k.dts | 32 +++++++
8 files changed, 338 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/bcm/cygnus.txt
create mode 100644 Documentation/devicetree/bindings/clock/bcm-cygnus-clock.txt
create mode 100644 arch/arm/boot/dts/bcm-cygnus-clock.dtsi
create mode 100644 arch/arm/boot/dts/bcm-cygnus.dtsi
create mode 100644 arch/arm/boot/dts/bcm911360_entphn.dts
create mode 100644 arch/arm/boot/dts/bcm911360k.dts
create mode 100644 arch/arm/boot/dts/bcm958300k.dts
next prev parent reply other threads:[~2014-10-30 19:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 19:50 [GIT PULL] Broadcom Cygnus SoC defconfig changes Florian Fainelli
2014-10-30 19:50 ` Florian Fainelli [this message]
2014-11-09 0:25 ` [GIT PULL] Broadcom Cygnus SoC Device Tree changes Olof Johansson
2014-11-10 18:36 ` Olof Johansson
2014-10-30 19:50 ` [GIT PULL] Broadcom Cygnus SoC MAINTAINERS changes Florian Fainelli
2014-10-30 19:50 ` [GIT PULL] Broadcom Cygnus SoC platforms changes Florian Fainelli
2014-11-09 0:28 ` Olof Johansson
2014-11-09 0:33 ` Olof Johansson
2014-11-09 0:13 ` [GIT PULL] Broadcom Cygnus SoC defconfig changes Olof Johansson
2014-11-09 5:45 ` Scott Branden
2014-11-09 19:24 ` Florian Fainelli
2014-11-10 5:36 ` Scott Branden
2014-11-10 6:21 ` Olof Johansson
2014-11-12 6:29 ` Florian Fainelli
2014-11-12 17:25 ` 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=1414698612-26216-2-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).