From: tomi.valkeinen@ti.com (Tomi Valkeinen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 2/2] OMAP: add omap_device_reset()
Date: Mon, 30 May 2011 09:00:04 +0300 [thread overview]
Message-ID: <1306735204.2117.12.camel@deskari> (raw)
In-Reply-To: <alpine.DEB.2.00.1105292006330.8973@utopia.booyaka.com>
On Sun, 2011-05-29 at 20:15 -0600, Paul Walmsley wrote:
> On Fri, 27 May 2011, Tomi Valkeinen wrote:
>
> > However, VENC doesn't use the standard syscontrol mechanism, so that
> > cannot be done via omap_device interface anyway.
>
> struct omap_hwmod_class has a .reset function pointer for this purpose.
> It's already been necessary to deal with the I2C IP block:
>
> https://patchwork.kernel.org/patch/804072/
>
> If all that's needed are the steps in 4430 TRM Rev. T Section 10.6.5.1.2.3
> "Subsequence--Video Encoder Software Reset", then it should be possible to
> handle this internal reset with hwmod code.
Yes, that should be enough. However, the VENC_F_CONTROL register also
contains bits that need to be programmed by the driver. I hope that
doesn't cause any problems. Probably not, as hwmod code should use that
register only at reset time.
Tomi
next prev parent reply other threads:[~2011-05-30 6:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 7:38 [PATCHv2 0/2] Some omap_device/hwmod/pwrdomain patches Tomi Valkeinen
2011-05-27 7:38 ` [PATCHv2 1/2] OMAP: change get_context_loss_count ret value to int Tomi Valkeinen
2011-05-27 7:38 ` [PATCHv2 2/2] OMAP: add omap_device_reset() Tomi Valkeinen
2011-05-27 12:38 ` Cousson, Benoit
2011-05-27 12:46 ` Tomi Valkeinen
2011-05-27 14:43 ` Cousson, Benoit
2011-05-27 14:51 ` Santosh Shilimkar
2011-05-27 15:00 ` Cousson, Benoit
2011-05-27 15:06 ` Santosh Shilimkar
2011-05-27 16:40 ` Tomi Valkeinen
2011-05-30 2:15 ` Paul Walmsley
2011-05-30 6:00 ` Tomi Valkeinen [this message]
2011-05-30 8:49 ` Cousson, Benoit
2011-05-30 2:24 ` Paul Walmsley
2011-05-30 5:55 ` Tomi Valkeinen
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=1306735204.2117.12.camel@deskari \
--to=tomi.valkeinen@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).