From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-sh@vger.kernel.org
Subject: Re: LCDC problem after commit 794d78fea51504bad3880d14f354a9847f318f25
Date: Thu, 11 Aug 2011 19:37:04 +0000 [thread overview]
Message-ID: <201108112137.04394.rjw@sisk.pl> (raw)
In-Reply-To: <201108080125.34329.rjw@sisk.pl>
On Thursday, August 11, 2011, Laurent Pinchart wrote:
> Hi Magnus,
>
> Sorry for the late reply.
>
> On Tuesday 09 August 2011 12:48:44 Magnus Damm wrote:
> > On Mon, Aug 8, 2011 at 10:46 AM, Magnus Damm <magnus.damm@gmail.com> wrote:
> > > On Mon, Aug 8, 2011 at 8:25 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > >> Unfortunately, after commit 794d78fea51504bad3880d14f354a9847f318f25
> > >> (drivers: sh: late disabling of clocks V2) the LCDC screen on my
> > >> Mackerel board goes off (late) during boot and cannot be turned on
> > >> by any way AFAICS (the backlight remains on, though).
> > >>
> > >> It looks like the late disabling of clocks interacts badly with the
> > >> clock management done by PM domains.
> > >
> > > This is most likely showing a so-far-not-handled clock dependency for
> > > the LCDC hardware. I'll have a look.
> >
> > Further investigation shows that this only triggers when the MERAM is
> > enabled in the kernel configuration using CONFIG_FB_SH_MOBILE_MERAM=y.
> > So this seems more related to MERAM power management than LCDC.
> >
> > Digging a bit deeper makes it clear that the sh_mobile_meram.c driver
> > in upstream doesn't seem to include any Runtime PM code. I recall
> > seeing various versions posted to the mailing list.
> >
> > Laurent [CC], can you please provide us with a list of outstanding
> > LCDC/MERAM patches to make this work as expected? I realize there are
> > quite a few outstanding LCDC patches, but if possible please provide a
> > list of the bare minimum to make this work with 3.1-rc.
>
> I've pushed my pending patches to http://git.linuxtv.org/pinchartl/fbdev.git
> in the pm-domains branch. The first 19 patches have been picked from mailing
> lists. Hopefully they're the latest versions that have been posted. The next
> 11 patches shouldn't be required to enable runtime PM with the MERAM, but they
> provide code cleanup and bug fixes.
>
> Are Rafael' and Damian's patches ready for mainline ? If so, when will they be
> pulled ? They're more than one month old, I was expecting them to hit v3.1-
> rc1. The backlog is growing, which makes collaboration more difficult.
Which of my patches are you referring to in particular?
Rafael
next prev parent reply other threads:[~2011-08-11 19:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-07 23:25 LCDC problem after commit 794d78fea51504bad3880d14f354a9847f318f25 Rafael J. Wysocki
2011-08-08 1:46 ` Magnus Damm
2011-08-09 10:48 ` Magnus Damm
2011-08-10 4:58 ` Damian Hobson-Garcia
2011-08-11 0:10 ` Laurent Pinchart
2011-08-11 19:37 ` Rafael J. Wysocki [this message]
2011-08-12 9:59 ` Laurent Pinchart
2011-08-19 6:24 ` Laurent Pinchart
2011-08-22 1:36 ` Damian Hobson-Garcia
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=201108112137.04394.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-sh@vger.kernel.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