From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: NeilBrown <neilb@suse.de>, Jean Pihet <jean.pihet@newoldbits.com>,
Govindraj <govindraj.ti@gmail.com>, Kevin Hilman <khilman@ti.com>,
t-kristo@ti.com,
linux-omap mailing list <linux-omap@vger.kernel.org>,
Joe Woodward <jw@terrafix.co.uk>
Subject: Re: PM(?) problems on v3.3-rc1 on OMAP3
Date: Mon, 23 Jan 2012 13:06:27 +0200 [thread overview]
Message-ID: <1327316787.1916.38.camel@deskari> (raw)
In-Reply-To: <alpine.DEB.2.00.1201230401170.29673@utopia.booyaka.com>
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
On Mon, 2012-01-23 at 04:02 -0700, Paul Walmsley wrote:
> On Mon, 23 Jan 2012, Tomi Valkeinen wrote:
>
> > On Mon, 2012-01-23 at 02:31 -0700, Paul Walmsley wrote:
> >
> > > Want to spin a quick patch for v3.3-rc1 to add it?
> >
> > I think there are other bits missing also. CLOCKACTIVITY is missing for
> > DISPC. And DSI doesn't have any SYSC flags defined... I'll try to go
> > through them all.
>
> Might be best to do a minimal patch for the 3.3-rc series and stable trees
> that just sets the SYSC_HAS_ENAWAKEUP flag? Then we can queue up a
> larger patch to fix the rest of the bits for the 3.4 merge window...
True. But the patch will be slightly larger than just trivial flag
addition, as OMAP2 doesn't have ENWAKEUP, and the current dispc
hwmod_class is shared between OMAP2 and OMAP3.
So I guess I'll split that and add ENWAKEUP to OMAP3's hwmod data.
And regarding clock activity, it seems a flag HWMOD_SET_DEFAULT_CLOCKACT
is also needed before the clockactivity is set to HW. But there's a XXX
comment above it, and I'm not sure what that's about.
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-01-23 11:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 10:33 PM(?) problems on v3.3-rc1 on OMAP3 Tomi Valkeinen
2012-01-20 10:49 ` Govindraj
2012-01-20 11:07 ` Tomi Valkeinen
2012-01-20 11:21 ` Govindraj
2012-01-20 12:32 ` Jean Pihet
2012-01-20 12:44 ` Govindraj
2012-01-21 7:39 ` Paul Walmsley
2012-01-21 7:38 ` Paul Walmsley
2012-01-20 11:56 ` Govindraj
2012-01-20 12:01 ` Tomi Valkeinen
2012-01-20 12:34 ` Jean Pihet
2012-01-20 12:40 ` Tomi Valkeinen
2012-01-20 13:36 ` Jean Pihet
2012-01-20 15:00 ` Tomi Valkeinen
2012-01-22 11:11 ` NeilBrown
2012-01-23 8:53 ` Tomi Valkeinen
2012-01-23 9:04 ` Paul Walmsley
2012-01-23 9:24 ` Tomi Valkeinen
2012-01-23 9:31 ` Paul Walmsley
2012-01-23 10:48 ` Tomi Valkeinen
2012-01-23 11:02 ` Paul Walmsley
2012-01-23 11:06 ` Tomi Valkeinen [this message]
2012-01-24 10:39 ` Tomi Valkeinen
2012-01-20 12:45 ` Govindraj
2012-01-20 12:47 ` Shubhrajyoti
2012-01-21 7:35 ` Paul Walmsley
2012-01-21 7:47 ` Paul Walmsley
2012-01-21 15:57 ` Tomi Valkeinen
2012-01-21 20:46 ` NeilBrown
2012-01-23 8:25 ` Tomi Valkeinen
2012-01-21 20:47 ` Paul Walmsley
2012-01-22 11:11 ` Valkeinen, Tomi
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=1327316787.1916.38.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=govindraj.ti@gmail.com \
--cc=jean.pihet@newoldbits.com \
--cc=jw@terrafix.co.uk \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=neilb@suse.de \
--cc=paul@pwsan.com \
--cc=t-kristo@ti.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