From: mohun106@gmail.com (mohun106 at gmail.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/1] arm64: Add support for Cavium Thunder ARMv8 platform
Date: Mon, 3 Mar 2014 12:49:01 +0530 [thread overview]
Message-ID: <1393831142-27952-1-git-send-email-mohun106@gmail.com> (raw)
From: Radha Mohan Chintakuntla <rchintakuntla@cavium.com>
This patch adds preliminary support for Cavium's Thunder SoC which is
based on ARMv8 core.
The Thunder platform is full GICv3 compliant and uses 48-bit Physical
Addresses.
This patch depends on the following submitted patches
1) GICv3 driver from Marc Zyngier
[PATCH 01/18] arm64: initial support for GICv3
http://www.spinics.net/lists/arm-kernel/msg305027.html
2) GICv3 devicetree bindings
[PATCH 02/18] arm64: GICv3 device tree binding documentation
http://www.spinics.net/lists/arm-kernel/msg305023.html
3) Boot time configuration of Intermediate Physical Address size
[RFC PATCH 1/1] arm64: Add boot time configuration of
Intermediate Physical Address size
http://www.spinics.net/lists/arm-kernel/msg312370.html
Changes from v1:
- Removed Kconfig option for Thunder.
Radha Mohan Chintakuntla (1):
arm64: Add initial dts for Cavium Thunder SoC
arch/arm64/boot/dts/Makefile | 1 +
arch/arm64/boot/dts/thunder.dts | 158 +++++++++++++++++++++++++++++++++++++++
2 files changed, 159 insertions(+), 0 deletions(-)
create mode 100644 arch/arm64/boot/dts/thunder.dts
next reply other threads:[~2014-03-03 7:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 7:19 mohun106 at gmail.com [this message]
2014-03-03 7:19 ` [PATCH v2 1/1] arm64: Add initial dts for Cavium Thunder SoC mohun106 at gmail.com
2014-03-03 16:07 ` Kumar Gala
2014-03-03 16:26 ` Radha Mohan
2014-03-03 22:56 ` Rob Herring
2014-03-05 8:46 ` Radha Mohan
2014-03-05 9:45 ` Kumar Gala
2014-03-05 10:48 ` Radha Mohan
2014-03-06 2:38 ` Rob Herring
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=1393831142-27952-1-git-send-email-mohun106@gmail.com \
--to=mohun106@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).