linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kenchappa.demakkanavar@intel.com
To: will@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, robh+dt@kernel.org,
	devicetree@vger.kernel.org, dinguyen@kernel.org
Cc: furong.zhou@intel.com, kris.pan@linux.intel.com,
	kris.pan@intel.com, mgross@linux.intel.com, mark.gross@intel.com,
	"Kenchappa, Demakkanavar" <kenchappa.demakkanavar@intel.com>
Subject: [PATCH v3 0/3] Add initial Thunder Bay SoC / Board support
Date: Thu, 16 Sep 2021 11:28:15 +0530	[thread overview]
Message-ID: <1631771898-18702-1-git-send-email-kenchappa.demakkanavar@intel.com> (raw)

From: "Kenchappa, Demakkanavar" <kenchappa.demakkanavar@intel.com>

Hi,

This patch-set adds initial support for a new Intel Movidius SoC
code-named Thunder 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 Thunder Bay full or prime configuration boards
boot into initramfs.

Thunder Bay full configuration board has 4 clusters of 4 ARM
Cortex A53 CPUs per cluster, 4 VPU processors and
(8GB + 8GB + 4GB + 4GB) DDR memory.

Thunder Bay prime configuration board has 4 clusters of 4 ARM
Cortex A53 CPUs per cluster, 2 VPU processors and
(8GB + 4GB) DDR memory.

Changes since v2:
* Add compatibility strings for all supported boards in dt-binding yaml
* Email id format corrected. (First name, Last name)
* $nodename schema added for the root node
* Fixed 'make dtbs_check' warnings/errors
* Removed alias name for disabled serial1 node
* Corrected lowercase hex on unit-addresses

Changes since v1:
* Commit message updated for patch 3/3
* UART0 enabled by default for all Thunder Bay boards

Regards,
Kenchappa S. D.

Kenchappa, Demakkanavar (3):
  arm64: Add config for Thunder Bay SoC
  dt-bindings: arm: Add Thunder Bay bindings
  arm64: dts: add initial device tree for Thunder Bay SoC

 .../devicetree/bindings/arm/intel,thunderbay.yaml  |  27 +++
 MAINTAINERS                                        |   7 +
 arch/arm64/Kconfig.platforms                       |   5 +
 arch/arm64/boot/dts/intel/Makefile                 |   6 +
 arch/arm64/boot/dts/intel/hddl_hybrid_2s_02.dts    |  42 ++++
 arch/arm64/boot/dts/intel/hddl_hybrid_2s_03.dts    |  42 ++++
 arch/arm64/boot/dts/intel/hddl_hybrid_2s_12.dts    |  42 ++++
 arch/arm64/boot/dts/intel/hddl_hybrid_2s_13.dts    |  42 ++++
 arch/arm64/boot/dts/intel/hddl_hybrid_4s.dts       |  53 +++++
 arch/arm64/boot/dts/intel/thunderbay-soc.dtsi      | 242 +++++++++++++++++++++
 10 files changed, 508 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/arm/intel,thunderbay.yaml
 create mode 100644 arch/arm64/boot/dts/intel/hddl_hybrid_2s_02.dts
 create mode 100644 arch/arm64/boot/dts/intel/hddl_hybrid_2s_03.dts
 create mode 100644 arch/arm64/boot/dts/intel/hddl_hybrid_2s_12.dts
 create mode 100644 arch/arm64/boot/dts/intel/hddl_hybrid_2s_13.dts
 create mode 100644 arch/arm64/boot/dts/intel/hddl_hybrid_4s.dts
 create mode 100644 arch/arm64/boot/dts/intel/thunderbay-soc.dtsi

-- 
2.7.4


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2021-09-16  6:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16  5:58 kenchappa.demakkanavar [this message]
2021-09-16  5:58 ` [PATCH v3 1/3] arm64: Add config for Thunder Bay SoC kenchappa.demakkanavar
2021-09-16  5:58 ` [PATCH v3 2/3] dt-bindings: arm: Add Thunder Bay bindings kenchappa.demakkanavar
2021-09-21 22:05   ` Rob Herring
2021-09-16  5:58 ` [PATCH v3 3/3] arm64: dts: add initial device tree for Thunder Bay SoC kenchappa.demakkanavar

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=1631771898-18702-1-git-send-email-kenchappa.demakkanavar@intel.com \
    --to=kenchappa.demakkanavar@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=furong.zhou@intel.com \
    --cc=kris.pan@intel.com \
    --cc=kris.pan@linux.intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.gross@intel.com \
    --cc=mgross@linux.intel.com \
    --cc=robh+dt@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).