From: <ying.zhang22455@nxp.com>
To: <linux-kernel@vger.kernel.org>
Cc: <jiafei.pan@nxp.com>, Stuart Yoder <stuart.yoder@nxp.com>,
Zhang Ying-22455 <ying.zhang22455@nxp.com>
Subject: [PATCH 1/5] soc: fsl: add support for arm64/Layerscape SOC specific drivers
Date: Fri, 21 Apr 2017 15:42:43 +0800 [thread overview]
Message-ID: <1492760567-27894-1-git-send-email-ying.zhang22455@nxp.com> (raw)
From: Stuart Yoder <stuart.yoder@nxp.com>
Signed-off-by: Zhang Ying-22455 <ying.zhang22455@nxp.com>
---
drivers/soc/Kconfig | 13 +++++++++++++
drivers/soc/fsl/Kconfig | 3 +++
drivers/soc/fsl/Kconfig.arm | 16 ++++++++++++++++
drivers/soc/fsl/Makefile | 1 +
4 files changed, 33 insertions(+)
create mode 100644 drivers/soc/fsl/Kconfig.arm
diff --git a/drivers/soc/Kconfig b/drivers/soc/Kconfig
index f09023f..157992b 100644
--- a/drivers/soc/Kconfig
+++ b/drivers/soc/Kconfig
@@ -13,4 +13,17 @@ source "drivers/soc/ux500/Kconfig"
source "drivers/soc/versatile/Kconfig"
source "drivers/soc/zte/Kconfig"
+config FSL_SOC_DRIVERS
+ bool "Freescale Soc Drivers"
+ depends on FSL_SOC || ARCH_MXC
+ default n
+ help
+ Say y here to enable Freescale Soc Device Drivers support.
+ The Soc Drivers provides the device driver that is a specific block
+ or feature on Freescale platform.
+
+if FSL_SOC_DRIVERS
+ source "drivers/soc/fsl/Kconfig"
+endif
+
endmenu
diff --git a/drivers/soc/fsl/Kconfig b/drivers/soc/fsl/Kconfig
index 7a9fb9b..333ecfb 100644
--- a/drivers/soc/fsl/Kconfig
+++ b/drivers/soc/fsl/Kconfig
@@ -16,3 +16,6 @@ config FSL_GUTS
Initially only reading SVR and registering soc device are supported.
Other guts accesses, such as reading RCW, should eventually be moved
into this driver as well.
+if ARM || ARM64
+source "drivers/soc/fsl/Kconfig.arm"
+endif
diff --git a/drivers/soc/fsl/Kconfig.arm b/drivers/soc/fsl/Kconfig.arm
new file mode 100644
index 0000000..47ec165
--- /dev/null
+++ b/drivers/soc/fsl/Kconfig.arm
@@ -0,0 +1,16 @@
+#
+# Freescale ARM SOC Drivers
+#
+
+config LS_SOC_DRIVERS
+ bool "Layerscape Soc Drivers"
+ depends on ARCH_LAYERSCAPE
+ default n
+ help
+ Say y here to enable Freescale Layerscape Soc Device Drivers support.
+ The Soc Drivers provides the device driver that is a specific block
+ or feature on Layerscape platform.
+
+if LS_SOC_DRIVERS
+ source "drivers/soc/fsl/layerscape/Kconfig"
+endif
diff --git a/drivers/soc/fsl/Makefile b/drivers/soc/fsl/Makefile
index 44b3beb..2b61dad 100644
--- a/drivers/soc/fsl/Makefile
+++ b/drivers/soc/fsl/Makefile
@@ -6,3 +6,4 @@ obj-$(CONFIG_FSL_DPAA) += qbman/
obj-$(CONFIG_QUICC_ENGINE) += qe/
obj-$(CONFIG_CPM) += qe/
obj-$(CONFIG_FSL_GUTS) += guts.o
+obj-$(CONFIG_LS_SOC_DRIVERS) += layerscape/
--
2.1.0.27.g96db324
next reply other threads:[~2017-04-21 7:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 7:42 ying.zhang22455 [this message]
2017-04-21 7:42 ` [PATCH 2/5] soc: fsl: add flextimer module alarm driver for Layerscape ying.zhang22455
2017-04-21 12:51 ` kbuild test robot
2017-04-21 17:01 ` kbuild test robot
2017-04-21 7:42 ` [PATCH 3/5] arm64: ls1021a: dts: add ftm0 nodes ying.zhang22455
2017-04-21 7:42 ` [PATCH 4/5] arm64: ls1043a: dts: add rcpm and " ying.zhang22455
2017-04-21 7:42 ` [PATCH 5/5] Fix errata A-007728 for flextimer ying.zhang22455
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=1492760567-27894-1-git-send-email-ying.zhang22455@nxp.com \
--to=ying.zhang22455@nxp.com \
--cc=jiafei.pan@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stuart.yoder@nxp.com \
/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).