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,
"Demakkanavar, Kenchappa" <kenchappa.demakkanavar@intel.com>
Subject: [PATCH V2 1/3] arm64: Add config for Thunder Bay SoC
Date: Tue, 20 Jul 2021 10:52:47 +0530 [thread overview]
Message-ID: <1626758569-27176-2-git-send-email-kenchappa.demakkanavar@intel.com> (raw)
In-Reply-To: <1626758569-27176-1-git-send-email-kenchappa.demakkanavar@intel.com>
From: "Demakkanavar, Kenchappa" <kenchappa.demakkanavar@intel.com>
Add ARCH_THUNDERBAY configuration option to support Intel Movidius SoC
code-named Thunder Bay
Signed-off-by: Demakkanavar, Kenchappa <kenchappa.demakkanavar@intel.com>
---
arch/arm64/Kconfig.platforms | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
index 6409b47..8a043e2 100644
--- a/arch/arm64/Kconfig.platforms
+++ b/arch/arm64/Kconfig.platforms
@@ -154,6 +154,11 @@ config ARCH_KEEMBAY
help
This enables support for Intel Movidius SoC code-named Keem Bay.
+config ARCH_THUNDERBAY
+ bool "Thunder Bay SoC"
+ help
+ This enables support for Intel Movidius SoC code-named Thunder Bay.
+
config ARCH_MEDIATEK
bool "MediaTek SoC Family"
select ARM_GIC
--
2.7.4
next prev parent reply other threads:[~2021-07-20 5:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 5:22 [PATCH V2 0/3] Add initial Thunder Bay SoC / Board support kenchappa.demakkanavar
2021-07-20 5:22 ` kenchappa.demakkanavar [this message]
2021-07-20 5:22 ` [PATCH V2 2/3] dt-bindings: arm: Add Thunder Bay bindings kenchappa.demakkanavar
2021-07-29 19:40 ` Rob Herring
2021-07-20 5:22 ` [PATCH V2 3/3] arm64: dts: add initial device tree for Thunder Bay SoC kenchappa.demakkanavar
2021-07-29 19:53 ` Rob Herring
2021-08-27 7:55 ` Demakkanavar, Kenchappa
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=1626758569-27176-2-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).