From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Joe Woodward <jw@terrafix.co.uk>
Cc: Jean Pihet <jean.pihet@newoldbits.com>,
Paul Walmsley <paul@pwsan.com>,
khilman@ti.com, Archit Taneja <a0393947@ti.com>,
linux-omap@vger.kernel.org
Subject: Re: v3.4-rc4 DSS PM problem (Was: Re: Problems with 3.4-rc5)
Date: Tue, 12 Jun 2012 14:05:14 +0300 [thread overview]
Message-ID: <1339499114.2392.35.camel@deskari> (raw)
In-Reply-To: <WC20120612105024.5601BD@terrafix.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]
On Tue, 2012-06-12 at 11:50 +0100, Joe Woodward wrote:
> -----Original Message-----
> From: Tomi Valkeinen <tomi.valkeinen@ti.com>
> To: Joe Woodward <jw@terrafix.co.uk>
> Cc: Jean Pihet <jean.pihet@newoldbits.com>, Paul Walmsley <paul@pwsan.com>, khilman@ti.com, Archit Taneja <a0393947@ti.com>, linux-
> omap@vger.kernel.org
> Date: Tue, 12 Jun 2012 13:37:04 +0300
> Subject: Re: v3.4-rc4 DSS PM problem (Was: Re: Problems with 3.4-rc5)
>
> > On Tue, 2012-06-12 at 11:15 +0100, Joe Woodward wrote:
> > > Was there ever a conclussion to this discussion?
> > >
> > > I'm assuming this is unlikely to be fixed in 3.5?
> >
> > If by conclusion you mean full understanding and a proper fix, then no.
> >
> > But the patch 3568f2a46f2a73bab18c914df06afd98a97e0e0e (OMAPDSS: use
> > DSI_FIFO_BUG workaround only for manual update displays) has been
> > merged, and that should circumvent the problem.
> >
> > Are you still seeing problems?
>
> I haven't tested any kernels since 3.4, I normally wait till a later rc and had missed that patch...
>
> If I have any problems I'll report them, but assume it's fixed otherwise.
If the problem is visible on plain 3.4 series (i.e. without any extras,
like PM patch series or such), and the commit fixes the problem, perhaps
I should the patch for 3.4 stable series? The commit applies cleanly to
v3.4.2.
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-06-12 11:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 11:52 Problems with 3.4-rc5 Joe Woodward
2012-05-02 12:24 ` Archit Taneja
2012-05-02 12:46 ` Joe Woodward
2012-05-03 8:28 ` Tomi Valkeinen
2012-05-03 8:49 ` Joe Woodward
2012-05-03 10:02 ` Archit Taneja
2012-05-03 13:07 ` Tomi Valkeinen
2012-05-04 9:19 ` Joe Woodward
2012-05-04 13:50 ` Tomi Valkeinen
2012-05-04 14:01 ` Tomi Valkeinen
2012-05-04 14:09 ` Joe Woodward
2012-05-04 14:54 ` v3.4-rc4 DSS PM problem (Was: Re: Problems with 3.4-rc5) Tomi Valkeinen
2012-05-04 14:58 ` Tomi Valkeinen
2012-05-08 13:26 ` Tomi Valkeinen
2012-05-14 7:36 ` Joe Woodward
2012-05-14 7:55 ` Tomi Valkeinen
2012-05-14 22:48 ` Kevin Hilman
2012-05-15 7:28 ` Tomi Valkeinen
2012-05-15 17:29 ` Kevin Hilman
2012-05-15 17:55 ` Paul Walmsley
2012-05-16 9:08 ` Tomi Valkeinen
2012-05-16 9:20 ` Tomi Valkeinen
2012-05-24 16:19 ` Paul Walmsley
2012-05-16 10:09 ` Cousson, Benoit
2012-05-24 12:35 ` Tomi Valkeinen
2012-05-25 0:39 ` Paul Walmsley
2012-05-25 8:24 ` Tomi Valkeinen
2012-05-25 12:55 ` Jean Pihet
2012-06-12 10:15 ` Joe Woodward
2012-06-12 10:37 ` Tomi Valkeinen
2012-06-12 10:50 ` Joe Woodward
2012-06-12 11:05 ` Tomi Valkeinen [this message]
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=1339499114.2392.35.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=a0393947@ti.com \
--cc=jean.pihet@newoldbits.com \
--cc=jw@terrafix.co.uk \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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