From mboxrd@z Thu Jan 1 00:00:00 1970 From: Omar Ramirez Luna Subject: [PATCH 0/3] OMAP: hwmod: reset API proposal Date: Fri, 15 Jun 2012 20:54:38 -0500 Message-ID: <1339811681-5256-1-git-send-email-omar.luna@linaro.org> Return-path: Received: from mail-ob0-f174.google.com ([209.85.214.174]:37831 "EHLO mail-ob0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750923Ab2FPByz (ORCPT ); Fri, 15 Jun 2012 21:54:55 -0400 Received: by obbtb18 with SMTP id tb18so4800188obb.19 for ; Fri, 15 Jun 2012 18:54:54 -0700 (PDT) Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Benoit Cousson , Paul Walmsley , Kevin Hilman Cc: Tony Lindgren , Russell King , Ohad Ben-Cohen , Tomi Valkeinen , linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Omar Ramirez Luna Recent changes in omap_hwmod framework have reworked the behaviour towards hardreset handling, commit 747834a (ARM: OMAP2+: hwmod: revise hardreset behavior) recommends for drivers to implement their own reset sequences until code out-of-tree hits mainline and then their needs and code can be reviewed. Since it is not clear when this will occur for all drivers and hwmod code was not deleted (presumably because at some point it will handle the resets once again), this series exports functions to handle hardreset lines in an attempt to reduce code duplication for those who have a common reset sequence. These APIs are intended to be used by iommu for now, but were tested with IPU and remoteproc on Pandaboard. Omar Ramirez Luna (3): ARM: OMAP: hwmod: partially un-reset hwmods might not be properly enabled ARM: OMAP: hwmod: revise deassert sequence ARM: OMAP: omap_device: expose hwmod assert/deassert to omap devices arch/arm/mach-omap2/omap_hwmod.c | 70 +++++++++++++++++++------ arch/arm/plat-omap/include/plat/omap_device.h | 4 ++ arch/arm/plat-omap/omap_device.c | 45 ++++++++++++++++ 3 files changed, 103 insertions(+), 16 deletions(-) -- 1.7.4.1