From: Omar Ramirez Luna <omar.luna@linaro.org> To: Benoit Cousson <b-cousson@ti.com>, Paul Walmsley <paul@pwsan.com>, Kevin Hilman <khilman@ti.com> Cc: Tony Lindgren <tony@atomide.com>, Russell King <linux@arm.linux.org.uk>, Ohad Ben-Cohen <ohad@wizery.com>, Tomi Valkeinen <tomi.valkeinen@ti.com>, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Omar Ramirez Luna <omar.luna@linaro.org> Subject: [PATCH 0/3] OMAP: hwmod: reset API proposal Date: Fri, 15 Jun 2012 20:54:38 -0500 [thread overview] Message-ID: <1339811681-5256-1-git-send-email-omar.luna@linaro.org> (raw) 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
WARNING: multiple messages have this Message-ID (diff)
From: omar.luna@linaro.org (Omar Ramirez Luna) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 0/3] OMAP: hwmod: reset API proposal Date: Fri, 15 Jun 2012 20:54:38 -0500 [thread overview] Message-ID: <1339811681-5256-1-git-send-email-omar.luna@linaro.org> (raw) 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
next reply other threads:[~2012-06-16 1:54 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-16 1:54 Omar Ramirez Luna [this message] 2012-06-16 1:54 ` [PATCH 0/3] OMAP: hwmod: reset API proposal Omar Ramirez Luna 2012-06-16 1:54 ` [PATCH 1/3] ARM: OMAP: hwmod: partially un-reset hwmods might not be properly enabled Omar Ramirez Luna 2012-06-16 1:54 ` Omar Ramirez Luna 2012-06-16 1:54 ` [PATCH 2/3] ARM: OMAP: hwmod: revise deassert sequence Omar Ramirez Luna 2012-06-16 1:54 ` Omar Ramirez Luna 2012-06-16 1:54 ` [PATCH 3/3] ARM: OMAP: omap_device: expose hwmod assert/deassert to omap devices Omar Ramirez Luna 2012-06-16 1:54 ` Omar Ramirez Luna 2012-06-28 1:23 ` [PATCH 0/3] OMAP: hwmod: reset API proposal Omar Ramirez Luna 2012-06-28 1:23 ` Omar Ramirez Luna 2012-07-16 19:21 Omar Ramirez Luna 2012-07-16 19:21 ` Omar Ramirez Luna
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=1339811681-5256-1-git-send-email-omar.luna@linaro.org \ --to=omar.luna@linaro.org \ --cc=b-cousson@ti.com \ --cc=khilman@ti.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=linux@arm.linux.org.uk \ --cc=ohad@wizery.com \ --cc=paul@pwsan.com \ --cc=tomi.valkeinen@ti.com \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.