From: Sebastian Reichel <sre@debian.org>
To: linux-kernel@vger.kernel.org
Cc: Sebastian Reichel <sre@debian.org>,
linux-omap@vger.kernel.org, linus.walleij@linaro.org,
Kevin Hilman <khilman@deeprootsystems.com>,
Shubhrajyoti Datta <omaplinuxkernel@gmail.com>,
Carlos Chinea <cch.devel@gmail.com>
Subject: [RFC PATCH 0/3] OMAP SSI driver
Date: Sun, 11 Aug 2013 18:13:45 +0200 [thread overview]
Message-ID: <1376237628-1077-1-git-send-email-sre@debian.org> (raw)
Hi !
This patchset adds an OMAP SSI driver to the HSI framework.
After leaving Nokia Carlos Chinea had no more time to work on this patchset;
Thus I tried updating the driver to fix the mentioned issues.
I applied the following changes to the last patch from Carlos:
* convert driver to use hwmod and add SSI information to hwmod database
* convert driver to use runtime_pm
* change platform data, so that it forwards the wake_gpio to avoid irq_to_gpio
* move the ssi.h and rename to hsi-omap-ssi.h (multiplatform support)
The code compiles and is initialized on the RX51. I also verified, that it
does not break the boot on my Pandaboard.
The driver has been written by Carlos Chinea and has already been sent for
public review as part of the HSI framework RFC before:
https://lkml.org/lkml/2011/6/10/280
-- Sebastian
Sebastian Reichel (3):
ARM: OMAP2+: hwmod-data: Add SSI information
ARM: OMAP2+: HSI: Introduce OMAP SSI driver
ARM: OMAP2+: Add SSI driver configuration
arch/arm/mach-omap2/Makefile | 4 +
arch/arm/mach-omap2/board-rx51-peripherals.c | 10 +-
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 104 ++
arch/arm/mach-omap2/ssi.c | 82 ++
drivers/hsi/Kconfig | 1 +
drivers/hsi/Makefile | 1 +
drivers/hsi/controllers/Kconfig | 23 +
drivers/hsi/controllers/Makefile | 5 +
drivers/hsi/controllers/omap_ssi.c | 1879 ++++++++++++++++++++++++++
include/linux/platform_data/hsi-omap-ssi.h | 202 +++
10 files changed, 2310 insertions(+), 1 deletion(-)
create mode 100644 arch/arm/mach-omap2/ssi.c
create mode 100644 drivers/hsi/controllers/Kconfig
create mode 100644 drivers/hsi/controllers/Makefile
create mode 100644 drivers/hsi/controllers/omap_ssi.c
create mode 100644 include/linux/platform_data/hsi-omap-ssi.h
--
1.7.10.4
next reply other threads:[~2013-08-11 16:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 16:13 Sebastian Reichel [this message]
2013-08-11 16:17 ` [PATCH 1/3] ARM: OMAP2+: hwmod-data: Add SSI information Sebastian Reichel
2013-08-11 16:17 ` [PATCH 2/3] ARM: OMAP2+: HSI: Introduce OMAP SSI driver Sebastian Reichel
2013-08-12 8:28 ` Tony Lindgren
2013-08-23 13:57 ` Linus Walleij
2013-08-23 18:17 ` Sebastian Reichel
2013-08-11 16:17 ` [PATCH 3/3] ARM: OMAP2+: Add SSI driver configuration Sebastian Reichel
2013-08-12 8:30 ` Tony Lindgren
2013-08-23 13:58 ` Linus Walleij
2013-08-23 18:20 ` Sebastian Reichel
2013-08-26 8:52 ` Tony Lindgren
2013-08-12 8:26 ` [PATCH 1/3] ARM: OMAP2+: hwmod-data: Add SSI information Tony Lindgren
2013-08-21 1:22 ` Paul Walmsley
2013-08-23 18:29 ` Sebastian Reichel
2013-08-23 18:53 ` Paul Walmsley
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=1376237628-1077-1-git-send-email-sre@debian.org \
--to=sre@debian.org \
--cc=cch.devel@gmail.com \
--cc=khilman@deeprootsystems.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=omaplinuxkernel@gmail.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).