From: Carlos Chinea <carlos.chinea@nokia.com>
To: linux-kernel@vger.kernel.org
Cc: linux-omap@vger.kernel.org
Subject: [RFC PATCHv4 3/7] HSI: omap_ssi: Add OMAP SSI to the kernel configuration
Date: Tue, 14 Dec 2010 12:09:39 +0200 [thread overview]
Message-ID: <1292321383-30200-4-git-send-email-carlos.chinea@nokia.com> (raw)
In-Reply-To: <1292321383-30200-1-git-send-email-carlos.chinea@nokia.com>
Add OMAP SSI device and driver to the kernel configuration
Signed-off-by: Carlos Chinea <carlos.chinea@nokia.com>
---
arch/arm/mach-omap2/Makefile | 2 ++
drivers/hsi/Kconfig | 2 ++
drivers/hsi/Makefile | 1 +
drivers/hsi/controllers/Kconfig | 23 +++++++++++++++++++++++
drivers/hsi/controllers/Makefile | 5 +++++
5 files changed, 33 insertions(+), 0 deletions(-)
create mode 100644 drivers/hsi/controllers/Kconfig
create mode 100644 drivers/hsi/controllers/Makefile
diff --git a/arch/arm/mach-omap2/Makefile b/arch/arm/mach-omap2/Makefile
index b0810b9..1a1c0d9 100644
--- a/arch/arm/mach-omap2/Makefile
+++ b/arch/arm/mach-omap2/Makefile
@@ -111,6 +111,8 @@ obj-y += $(i2c-omap-m) $(i2c-omap-y)
ifneq ($(CONFIG_TIDSPBRIDGE),)
obj-y += dsp.o
endif
+omap-ssi-$(CONFIG_OMAP_SSI) := ssi.o
+obj-y += $(omap-ssi-m) $(omap-ssi-y)
# Specific board support
obj-$(CONFIG_MACH_OMAP_GENERIC) += board-generic.o
diff --git a/drivers/hsi/Kconfig b/drivers/hsi/Kconfig
index 937062e..bba73ea 100644
--- a/drivers/hsi/Kconfig
+++ b/drivers/hsi/Kconfig
@@ -14,4 +14,6 @@ config HSI_BOARDINFO
bool
default y
+source "drivers/hsi/controllers/Kconfig"
+
endif # HSI
diff --git a/drivers/hsi/Makefile b/drivers/hsi/Makefile
index ed94a3a..0de87bd 100644
--- a/drivers/hsi/Makefile
+++ b/drivers/hsi/Makefile
@@ -3,3 +3,4 @@
#
obj-$(CONFIG_HSI_BOARDINFO) += hsi_boardinfo.o
obj-$(CONFIG_HSI) += hsi.o
+obj-y += controllers/
diff --git a/drivers/hsi/controllers/Kconfig b/drivers/hsi/controllers/Kconfig
new file mode 100644
index 0000000..3efe0f0
--- /dev/null
+++ b/drivers/hsi/controllers/Kconfig
@@ -0,0 +1,23 @@
+#
+# HSI controllers configuration
+#
+comment "HSI controllers"
+
+config OMAP_SSI
+ tristate "OMAP SSI hardware driver"
+ depends on ARCH_OMAP && HSI
+ default n
+ ---help---
+ SSI is a legacy version of HSI. It is usually used to connect
+ an application engine with a cellular modem.
+ If you say Y here, you will enable the OMAP SSI hardware driver.
+
+ If unsure, say N.
+
+if OMAP_SSI
+
+config OMAP_SSI_CONFIG
+ boolean
+ default y
+
+endif # OMAP_SSI
diff --git a/drivers/hsi/controllers/Makefile b/drivers/hsi/controllers/Makefile
new file mode 100644
index 0000000..c4ba2c2
--- /dev/null
+++ b/drivers/hsi/controllers/Makefile
@@ -0,0 +1,5 @@
+#
+# Makefile for HSI controllers drivers
+#
+
+obj-$(CONFIG_OMAP_SSI) += omap_ssi.o
--
1.7.1
next prev parent reply other threads:[~2010-12-14 10:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 10:09 [RFC PATCHv4 0/7] HSI framework and drivers Carlos Chinea
2010-12-14 10:09 ` [RFC PATCHv4 1/7] HSI: hsi: Introducing HSI framework Carlos Chinea
2010-12-14 10:09 ` [RFC PATCHv4 2/7] HSI: omap_ssi: Introducing OMAP SSI driver Carlos Chinea
2010-12-18 0:30 ` Tony Lindgren
2010-12-20 16:38 ` Carlos Chinea
2010-12-14 10:09 ` Carlos Chinea [this message]
2010-12-14 10:09 ` [RFC PATCHv4 4/7] HSI: hsi_char: Add HSI char device driver Carlos Chinea
2010-12-14 11:56 ` Alan Cox
2010-12-14 17:24 ` Carlos Chinea
2010-12-14 10:09 ` [RFC PATCHv4 5/7] HSI: hsi_char: Add HSI char device kernel configuration Carlos Chinea
2010-12-14 10:09 ` [RFC PATCHv4 6/7] HSI: Add HSI API documentation Carlos Chinea
2010-12-14 10:09 ` [RFC PATCHv4 7/7] HSI: hsi_char: Update ioctl-number.txt Carlos Chinea
2011-03-21 8:16 ` [RFC PATCHv4 0/7] HSI framework and drivers Linus Walleij
2011-03-22 9:50 ` Carlos Chinea
2011-05-12 12:17 ` Govindraj
2011-05-16 12:04 ` Linus Walleij
2011-05-17 8:39 ` Carlos Chinea
2011-06-07 15:09 ` Sebastian Reichel
2011-06-08 7:12 ` Carlos Chinea
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=1292321383-30200-4-git-send-email-carlos.chinea@nokia.com \
--to=carlos.chinea@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.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).