[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1352860489-19960-1-git-send-email-omar.luna@linaro.org>
Date: Tue, 13 Nov 2012 20:34:47 -0600
From: Omar Ramirez Luna <omar.luna@...aro.org>
To: Tony Lindgren <tony@...mide.com>, Joerg Roedel <joro@...tes.org>
Cc: Russell King <linux@....linux.org.uk>,
Ohad Ben-Cohen <ohad@...ery.com>,
Omar Ramirez Luna <omar.luna@...aro.org>,
Ido Yariv <ido@...ery.com>,
Mauro Carvalho Chehab <mchehab@...hat.com>,
Paul Walmsley <paul@...an.com>, linux-omap@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
iommu@...ts.linux-foundation.org
Subject: [PATCH v4 0/2] OMAP: iommu: hwmod, reset handling and runtime PM
These patches are needed for remoteproc to work on OMAP4.
Introduced iommu hwmod support for OMAP3 (iva, isp) and
OMAP4 (ipu, dsp), along with the corresponding runtime PM
and routines to deassert reset lines, enable/disable clocks
and configure sysc registers.
For this series I dropped the patches already included in
mainline, along with cleanup and refactoring patches for save and
restore of mmu context, and DT bindings.
Due to single Image support, I rebased these on top of k3.7-rc5 and
DEPEND on:
[PATCH v5 0/6] Move rest of omap-iommu to live in drivers/iommu
http://thread.gmane.org/gmane.linux.kernel/1387788
Minor rebasing might be needed if these are included on top of
linux-omap, since they are affected by changes on headers being
moved to include/linux/platform_data and arch/arm/mach-omap2.
Omar Ramirez Luna (2):
ARM: OMAP3/4: iommu: migrate to hwmod framework
ARM: OMAP3/4: iommu: adapt to runtime pm
arch/arm/mach-omap2/devices.c | 2 +-
arch/arm/mach-omap2/omap-iommu.c | 167 +++++++-----------------------
drivers/iommu/omap-iommu.c | 68 +++++++------
drivers/iommu/omap-iommu.h | 3 -
drivers/iommu/omap-iommu2.c | 36 -------
include/linux/platform_data/iommu-omap.h | 9 ++-
6 files changed, 82 insertions(+), 203 deletions(-)
--
1.7.4.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists