From: Daniele Alessandrelli <daniele.alessandrelli@linux.intel.com>
To: linux-arm-kernel@lists.infradead.org, SoC Team <soc@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Jassi Brar <jassisinghbrar@gmail.com>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Cc: devicetree@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org, Dinh Nguyen <dinguyen@kernel.org>,
Paul Murphy <paul.j.murphy@intel.com>,
Will Deacon <will@kernel.org>,
Daniele Alessandrelli <daniele.alessandrelli@intel.com>
Subject: [PATCH v2 0/5] Add initial Keem Bay SoC / Board support
Date: Wed, 8 Jul 2020 18:50:15 +0100 [thread overview]
Message-ID: <20200708175020.194436-1-daniele.alessandrelli@linux.intel.com> (raw)
Hi,
This patch-set adds initial support for a new Intel Movidius SoC code-named
Keem Bay. The SoC couples an ARM Cortex A53 CPU with an Intel Movidius VPU.
This initial patch-set enables only the minimal set of components required
to make the Keem Bay EVM board boot into initramfs.
Changes from v1 to v2:
* Moved keembay-scmi-mailbox driver to a separate patchset
* Removed Keem Bay SCMI mailbox and SCMI node from Keem Bay SoC device tree
Regards,
Daniele
Daniele Alessandrelli (5):
arm64: Add config for Keem Bay SoC
dt-bindings: arm: Add Keem Bay bindings
MAINTAINERS: Add maintainers for Keem Bay SoC
arm64: dts: keembay: Add device tree for Keem Bay SoC
arm64: dts: keembay: Add device tree for Keem Bay EVM board
.../devicetree/bindings/arm/keembay.yaml | 19 ++
MAINTAINERS | 10 +
arch/arm64/Kconfig.platforms | 5 +
arch/arm64/boot/dts/intel/Makefile | 1 +
arch/arm64/boot/dts/intel/keembay-evm.dts | 39 ++++
arch/arm64/boot/dts/intel/keembay-soc.dtsi | 125 ++++++++++++
include/dt-bindings/clock/keembay-clocks.h | 188 ++++++++++++++++++
include/dt-bindings/power/keembay-power.h | 19 ++
8 files changed, 406 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/keembay.yaml
create mode 100644 arch/arm64/boot/dts/intel/keembay-evm.dts
create mode 100644 arch/arm64/boot/dts/intel/keembay-soc.dtsi
create mode 100644 include/dt-bindings/clock/keembay-clocks.h
create mode 100644 include/dt-bindings/power/keembay-power.h
--
2.26.2
next reply other threads:[~2020-07-08 17:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 17:50 Daniele Alessandrelli [this message]
2020-07-08 17:50 ` [PATCH v2 1/5] arm64: Add config for Keem Bay SoC Daniele Alessandrelli
2020-07-08 17:50 ` [PATCH v2 2/5] dt-bindings: arm: Add Keem Bay bindings Daniele Alessandrelli
2020-07-14 3:12 ` Rob Herring
2020-07-14 13:29 ` Daniele Alessandrelli
2020-07-08 17:50 ` [PATCH v2 3/5] MAINTAINERS: Add maintainers for Keem Bay SoC Daniele Alessandrelli
2020-07-08 17:50 ` [PATCH v2 4/5] arm64: dts: keembay: Add device tree " Daniele Alessandrelli
2020-07-08 17:50 ` [PATCH v2 5/5] arm64: dts: keembay: Add device tree for Keem Bay EVM board Daniele Alessandrelli
2020-07-14 12:40 ` [PATCH v2 0/5] Add initial Keem Bay SoC / Board support Arnd Bergmann
2020-07-14 13:33 ` Daniele Alessandrelli
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=20200708175020.194436-1-daniele.alessandrelli@linux.intel.com \
--to=daniele.alessandrelli@linux.intel.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=daniele.alessandrelli@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=paul.j.murphy@intel.com \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.org \
--cc=will@kernel.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).