From: Sebastian Reichel <sre@debian.org>
To: Sebastian Reichel <sre@ring0.de>,
Linus Walleij <linus.walleij@linaro.org>,
Shubhrajyoti Datta <omaplinuxkernel@gmail.com>,
Carlos Chinea <cch.devel@gmail.com>,
Paul Walmsley <paul@pwsan.com>
Cc: "Kevin Hilman" <khilman@deeprootsystems.com>,
"Tony Lindgren" <tony@atomide.com>,
"Russell King" <linux@arm.linux.org.uk>,
"Grant Likely" <grant.likely@linaro.org>,
"Rob Herring" <rob.herring@calxeda.com>,
"Pawel Moll" <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Stephen Warren" <swarren@wwwdotorg.org>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Rob Landley" <rob@landley.net>,
"'Benoît Cousson'" <bcousson@baylibre.com>,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
"Sebastian Reichel" <sre@debian.org>
Subject: [RFCv2 0/3] OMAP SSI driver
Date: Sun, 15 Sep 2013 22:44:13 +0200 [thread overview]
Message-ID: <1379277856-24571-1-git-send-email-sre@debian.org> (raw)
Hi,
Here is the second round of the OMAP SSI driver patches.
In this round I added/fixed:
- Usage of runtime PM
Previously runtime PM was only used to enable/disable the involved
clocks. Now the driver makes use of resume/suspend callbacks, which
simplified its code (the driver did its own reference counting).
- Removal of deprecated IRQF_DISABLED flag from irq requests
- HWMOD: set SSI parent to L4-Core instead of L3
I checked the public OMAP3 TRM, which assigns the address space used
by the driver as reserved L4-Core address space.
- HWMOD: removed data, which will be specified via Device Tree
- Change omap_ssi_port.wktest and omap_ssi_port.wkin_cken from
"unsigned int" to "bool"
- Change omap_ssi_port.wk_refcount from "int" to "unsigned int"
- Convert __raw_read* to read*_relaxed / write*_relaxed
- Removal of involved platform and board code
- Split driver into omap_ssi.c and omap_ssi_port.c
This changes helps in making the DT interface cleaner.
- Creation & Documentation of DT bindings
TODO:
- Central Message Queue
I did not yet implement a central message queue in the HSI framework.
I would prefer to do this after SSI is working in the mainline kernel,
since that makes testing easier.
- HSI client registration via DT
This needs changes in the HSI framework, which currently assumes,
that clients are registered via board support code. This is more
or less independent of the controller and should be added in an
independent patchset IMHO.
Version 1 (*) of the patchset: https://lkml.org/lkml/2013/8/11/67
(*) There have been patchsets send out by Carlos before my RFCv1,
see RFCv1 for details.
-- Sebastian
Sebastian Reichel (3):
ARM: OMAP2+: hwmod-data: Add SSI information
ARM: OMAP2+: HSI: Introduce OMAP SSI driver
ARM: dts: N900: Add SSI information
Documentation/devicetree/bindings/hsi/omap_ssi.txt | 73 ++
arch/arm/boot/dts/omap3-n900.dts | 8 +
arch/arm/boot/dts/omap34xx.dtsi | 49 +
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 48 +
drivers/hsi/Kconfig | 1 +
drivers/hsi/Makefile | 1 +
drivers/hsi/controllers/Kconfig | 20 +
drivers/hsi/controllers/Makefile | 6 +
drivers/hsi/controllers/omap_ssi.c | 585 +++++++++
drivers/hsi/controllers/omap_ssi.h | 167 +++
drivers/hsi/controllers/omap_ssi_port.c | 1346 ++++++++++++++++++++
drivers/hsi/controllers/omap_ssi_regs.h | 172 +++
12 files changed, 2476 insertions(+)
create mode 100644 Documentation/devicetree/bindings/hsi/omap_ssi.txt
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 drivers/hsi/controllers/omap_ssi.h
create mode 100644 drivers/hsi/controllers/omap_ssi_port.c
create mode 100644 drivers/hsi/controllers/omap_ssi_regs.h
--
1.8.4.rc3
next reply other threads:[~2013-09-15 20:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-15 20:44 Sebastian Reichel [this message]
2013-09-15 20:44 ` [RFCv2 1/3] ARM: OMAP2+: hwmod-data: Add SSI information Sebastian Reichel
2013-09-15 20:44 ` [RFCv2 2/3] ARM: OMAP2+: HSI: Introduce OMAP SSI driver Sebastian Reichel
2013-09-18 19:23 ` Tony Lindgren
2013-09-15 20:44 ` [RFCv2 3/3] ARM: dts: N900: Add SSI information Sebastian Reichel
2013-09-16 13:05 ` Javier Martinez Canillas
2013-09-16 15:01 ` Sebastian Reichel
2013-09-16 17:25 ` Javier Martinez Canillas
2013-09-16 18:10 ` Aaro Koskinen
2013-09-16 19:27 ` Sebastian Reichel
2013-09-16 13:11 ` Nishanth Menon
2013-09-23 20:35 ` Stephen Warren
2013-09-23 23:46 ` Sebastian Reichel
2013-09-24 19:55 ` Stephen Warren
2013-09-24 20:10 ` Tony Lindgren
2013-11-21 1:38 ` Tony Lindgren
2013-11-21 2:21 ` Sebastian Reichel
2013-11-21 20:46 ` Tony Lindgren
2013-11-21 23:38 ` Sebastian Reichel
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=1379277856-24571-1-git-send-email-sre@debian.org \
--to=sre@debian.org \
--cc=bcousson@baylibre.com \
--cc=cch.devel@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=khilman@deeprootsystems.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=omaplinuxkernel@gmail.com \
--cc=paul@pwsan.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=sre@ring0.de \
--cc=swarren@wwwdotorg.org \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®