From: omar.ramirez@ti.com (Omar Ramirez Luna)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/4] OMAP: iommu: hwmod support and runtime PM
Date: Wed, 14 Dec 2011 22:18:25 -0600 [thread overview]
Message-ID: <1323922709-6986-1-git-send-email-omar.ramirez@ti.com> (raw)
Introduced hwmod support for OMAP3 (iva, isp) and OMAP4 (ipu, dsp),
along with the corresponding runtime PM routines to deassert reset
lines, enable/disable clocks and configure sysc registers.
v4:
- Rebased to 3.2-rc5 LO.
- Added missing clkdm field for OMAP4 hwmod data.
- Moved pm runtime enable/disable to probe/remove functions as
suggested by MyungJoo Ham.
- Removed HWMOD_INIT_NO_RESET as it is not needed and because of
Kevin Hilman's comments, the failure I was seeing without
HWMOD_INIT_NO_RESET might have been related to local changes as
it couldn't be reproduced anymore.
- Removed iommu latency as it is the same as the default omap latency.
- Tested on OMAP3 (zoom3 + tidspbridge) and OMAP4 (Panda + rpmsg).
v3:
- Rebased to 3.1-rc10 lo rebuilt, added structure terminators, and
removed .omap_chip field.
v2:
- Added oh reset info to assert/deassert mmu reset lines.
- Addressed previous comments on v1
http://www.spinics.net/lists/arm-kernel/msg103271.html
Due to compatibility an ifdef needs to be propagated (previously on
iommu resource info) to hwmod data in OMAP3, so users of iommu and
tidspbridge can avoid issues of two modules managing mmu data/irqs/resets;
this until tidspbridge can be safely migrated to iommu framework.
Omar Ramirez Luna (4):
OMAP3: hwmod data: add mmu data for iva and isp
OMAP4: hwmod data: add mmu hwmod for ipu and dsp
OMAP3/4: iommu: migrate to hwmod framework
OMAP3/4: iommu: adapt to runtime pm
arch/arm/mach-omap2/iommu2.c | 36 -------
arch/arm/mach-omap2/omap-iommu.c | 156 +++++-----------------------
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 135 ++++++++++++++++++++++++
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 154 +++++++++++++++++++++++++--
arch/arm/plat-omap/include/plat/iommu.h | 17 +++-
arch/arm/plat-omap/include/plat/iommu2.h | 2 -
drivers/iommu/omap-iommu.c | 47 +++-----
7 files changed, 334 insertions(+), 213 deletions(-)
--
1.7.4.1
next reply other threads:[~2011-12-15 4:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 4:18 Omar Ramirez Luna [this message]
2011-12-15 4:18 ` [PATCH v4 1/4] OMAP3: hwmod data: add mmu data for iva and isp Omar Ramirez Luna
2011-12-16 0:39 ` Felipe Contreras
2011-12-16 2:01 ` Ramirez Luna, Omar
2011-12-19 16:11 ` Felipe Contreras
2011-12-23 15:53 ` Ramirez Luna, Omar
2011-12-25 21:08 ` Laurent Pinchart
2012-01-05 19:24 ` Ramirez Luna, Omar
2012-01-07 16:12 ` Laurent Pinchart
2011-12-15 4:18 ` [PATCH v4 2/4] OMAP4: hwmod data: add mmu hwmod for ipu and dsp Omar Ramirez Luna
2011-12-15 4:18 ` [PATCH v4 3/4] OMAP3/4: iommu: migrate to hwmod framework Omar Ramirez Luna
2011-12-16 0:47 ` Felipe Contreras
2011-12-15 4:18 ` [PATCH v4 4/4] OMAP3/4: iommu: adapt to runtime pm Omar Ramirez Luna
2011-12-16 0:33 ` Felipe Contreras
2011-12-16 2:59 ` Ramirez Luna, Omar
2011-12-16 0:53 ` Felipe Contreras
2011-12-16 3:18 ` Ramirez Luna, Omar
2011-12-19 16:27 ` Felipe Contreras
2011-12-23 16:30 ` Ramirez Luna, Omar
2011-12-23 17:04 ` Felipe Contreras
2011-12-25 0:03 ` Ramirez Luna, Omar
2011-12-27 9:41 ` Felipe Contreras
2012-01-05 18:26 ` Ramirez Luna, Omar
2011-12-17 1:39 ` Tony Lindgren
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=1323922709-6986-1-git-send-email-omar.ramirez@ti.com \
--to=omar.ramirez@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).