From: Omar Ramirez Luna <omar.luna@linaro.org>
To: Paul Walmsley <paul@pwsan.com>
Cc: Benoit Cousson <b-cousson@ti.com>,
Tony Lindgren <tony@atomide.com>,
Russell King <linux@arm.linux.org.uk>,
Kevin Hilman <khilman@ti.com>, Ohad Ben-Cohen <ohad@wizery.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Omar Ramirez Luna <omar.ramirez@copitl.com>
Subject: [PATCH 0/3] OMAP: hwmod: reset API proposal
Date: Mon, 16 Jul 2012 14:21:22 -0500 [thread overview]
Message-ID: <1342466485-1050-1-git-send-email-omar.luna@linaro.org> (raw)
From: Omar Ramirez Luna <omar.ramirez@copitl.com>
***
RESEND: http://bit.ly/PZDbcc
Needed for ipu, dsp and their mmu reset lines.
***
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, 104 insertions(+), 15 deletions(-)
--
1.7.4.1
next reply other threads:[~2012-07-16 19:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 19:21 Omar Ramirez Luna [this message]
2012-07-16 19:21 ` [PATCH 1/3] ARM: OMAP: hwmod: partially un-reset hwmods might not be properly enabled Omar Ramirez Luna
2012-08-20 14:49 ` Benoit Cousson
2012-08-21 1:13 ` Omar Ramirez Luna
2012-08-21 17:48 ` Omar Ramirez Luna
2012-07-16 19:21 ` [PATCH 2/3] ARM: OMAP: hwmod: revise deassert sequence Omar Ramirez Luna
2012-08-02 7:52 ` Paul Walmsley
2012-08-02 22:20 ` Omar Ramirez Luna
2012-08-03 5:24 ` Vaibhav Hiremath
2012-08-03 15:52 ` Omar Ramirez Luna
2012-08-20 10:21 ` Benoit Cousson
2012-08-21 1:15 ` Omar Ramirez Luna
2012-07-16 19:21 ` [PATCH 3/3] ARM: OMAP: omap_device: expose hwmod assert/deassert to omap devices Omar Ramirez Luna
2012-08-02 7:43 ` Paul Walmsley
2012-08-02 17:56 ` Omar Ramirez Luna
-- strict thread matches above, loose matches on Subject: below --
2012-06-16 1:54 [PATCH 0/3] OMAP: hwmod: reset API proposal Omar Ramirez Luna
2012-06-28 1:23 ` 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=1342466485-1050-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-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=ohad@wizery.com \
--cc=omar.ramirez@copitl.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: 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).