public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: dt64 for v4.8 (#1)
Date: Mon, 04 Jul 2016 22:49:27 +0200	[thread overview]
Message-ID: <87zipxuo14.fsf@free-electrons.com> (raw)

Hi,

Here is the first pull request for dt64 for mvebu for v4.8.

Gregory

The following changes since commit 19b67d5c8b2dbef9a10bc1aeb96a861c57a0bdf8:

  arm64: dts: marvell: add XOR node for Armada 3700 SoC (2016-04-29 15:07:42 +0200)

are available in the git repository at:

  git://git.infradead.org/linux-mvebu.git tags/mvebu-dt64-4.8-1

for you to fetch changes up to 5f4beef6db3c158ed99573d74e93dfe0611352e4:

  arm64: dts: marvell: add peripherals clocks for Armada 37xx (2016-07-04 22:21:13 +0200)

----------------------------------------------------------------
mvebu dt64 for 4.8 (part 1)

- update dt with mv-xor-v2 found in the Armada 7K/8K SoCs
- update dt with the clocks found in the Armada 3700 SoCs

----------------------------------------------------------------
Gregory CLEMENT (3):
      arm64: dts: marvell: Add xtal clock support for Armada 3700
      arm64: dts: marvell: add tbg clocks for Armada 37xx
      arm64: dts: marvell: add peripherals clocks for Armada 37xx

Thomas Petazzoni (2):
      arm64: dts: marvell: adjust to the latest mv-xor-v2 DT binding
      arm64: dts: marvell: add XOR engine description for Armada 7K/8K CP

 arch/arm64/boot/dts/marvell/armada-37xx.dtsi       | 35 ++++++++++++++++++++++
 arch/arm64/boot/dts/marvell/armada-ap806.dtsi      |  8 ++---
 .../boot/dts/marvell/armada-cp110-master.dtsi      | 18 +++++++++++
 3 files changed, 57 insertions(+), 4 deletions(-)

             reply	other threads:[~2016-07-04 20:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-04 20:49 Gregory CLEMENT [this message]
2016-07-07 12:18 ` [GIT PULL] ARM: mvebu: dt64 for v4.8 (#1) Arnd Bergmann

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=87zipxuo14.fsf@free-electrons.com \
    --to=gregory.clement@free-electrons.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