public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: torvalds@linux-foundation.org
Cc: linux-arm-kernel@lists.infradead.org, arm@kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL 7/7] ARM64: SoC changes for 3.18
Date: Wed, 08 Oct 2014 22:36:15 +0200	[thread overview]
Message-ID: <2440106.3HoFFHSvh9@wuerfel> (raw)
In-Reply-To: <1922034.HH2lvbiFi0@wuerfel>

The following changes since commit 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9:

  Linux 3.17-rc1 (2014-08-16 10:40:26 -0600)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/arm64-for-linus

for you to fetch changes up to 18ef9fefd3ef73279cd144bdb24cfd2683ff0492:

  arm64, defconfig: Enable Cavium Thunder SoC in defconfig (2014-10-02 17:38:55 +0200)

----------------------------------------------------------------
ARM64: SoC changes for 3.18

Starting with 3.18, we are merging SoC-specific changes for arm64 through
the arm-soc tree, like we have been doing for arm32.

This time, there is only one set of changes, adding support for the
Cavium "Thunder" Soc family. Since the changes are relatively small,
this includes Kconfig, defconfig and DT changes.

If all goes well, we will never require adding actual C source code
for platform support in arm64, given that the architecture is more
clearly defined and we have moved out a lot of the platform specifics
into device drivers for arm32 already.

----------------------------------------------------------------
Radha Mohan Chintakuntla (3):
      arm64, thunder: Add initial dts for Cavium Thunder SoC
      arm64, thunder: Document devicetree bindings for Cavium Thunder SoC
      arm64, thunder: Add Kconfig option for Cavium Thunder SoC Family

Robert Richter (1):
      arm64, defconfig: Enable Cavium Thunder SoC in defconfig

 .../devicetree/bindings/arm/cavium-thunder.txt     |  10 +
 Documentation/devicetree/bindings/arm/cpus.txt     |   1 +
 arch/arm64/Kconfig                                 |   5 +
 arch/arm64/boot/dts/Makefile                       |   1 +
 arch/arm64/boot/dts/thunder-88xx.dts               |  67 ++++
 arch/arm64/boot/dts/thunder-88xx.dtsi              | 401 +++++++++++++++++++++
 arch/arm64/configs/defconfig                       |   1 +
 7 files changed, 486 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/arm/cavium-thunder.txt
 create mode 100644 arch/arm64/boot/dts/thunder-88xx.dts
 create mode 100644 arch/arm64/boot/dts/thunder-88xx.dtsi


      parent reply	other threads:[~2014-10-08 20:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08 20:23 [GIT PULL 0/7] ARM: SoC changes for 3.18 Arnd Bergmann
2014-10-08 20:25 ` [GIT PULL 1/7] ARM: SoC non-critical bug fixes " Arnd Bergmann
2014-10-08 20:26 ` [GIT PULL 2/7] ARM: SoC cleanups " Arnd Bergmann
2014-10-08 20:28 ` [GIT PULL 3/7] ARM: SoC platform changes " Arnd Bergmann
2014-10-08 20:30 ` [GIT PULL 4/7] ARM: SoC DT updates " Arnd Bergmann
2014-10-08 20:33 ` [GIT PULL 5/7] ARM: SoC driver " Arnd Bergmann
2014-10-08 20:34 ` [GIT PULL 0/7] ARM: SoC defconfig changes " Arnd Bergmann
2014-10-08 20:35   ` Arnd Bergmann
2014-10-08 20:36 ` Arnd Bergmann [this message]

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=2440106.3HoFFHSvh9@wuerfel \
    --to=arnd@arndb.de \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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