From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: "ext stanley.miao" <stanley.miao@windriver.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"lwalkera@ieee.org" <lwalkera@ieee.org>,
"lwalkera@gmail.com" <lwalkera@gmail.com>,
"bryan.wu@canonical.com" <bryan.wu@canonical.com>,
Mathieu Poirier <mathieu.poirier@canonical.com>
Subject: Re: [PATCH V2] OMAP: DSS2: don't power off a panel twice
Date: Thu, 21 Oct 2010 16:42:00 +0300 [thread overview]
Message-ID: <1287668520.2142.52.camel@tubuntu> (raw)
In-Reply-To: <4C8062FE.9090004@windriver.com>
Hi,
On Fri, 2010-09-03 at 04:52 +0200, ext stanley.miao wrote:
> Hi, Tomi,
>
> Tomi Valkeinen wrote:
> > <snip>
> >
> > Otherwise this looks fine, except that panel-taal.c does not need
> > modifications, as it already handles this case.
> >
>
> I will send a V3 to remove the panel-taal.c part.
>
> > Also, at some point I (or somebody else =) should think how to do proper
> > locking for the panel drivers. Currently it's rather broken, and, for
> > example, enabling and disabling a panel at the same time will cause
> > problems. Except for panel-taal, which uses its own lock.
> >
>
> First, I don't think there is any occasion where you need to enable and
> disable a panel at the same time.
No, but that doesn't mean that enable and disable won't be called at the
same time.
> If so, what kind of result do you want ? enabled or disabled ?
Enabled or disabled, but not crashing or bugging display.
> Second, now the dssdev->state can do the lock job properly. It can
> ensure only one function can run if both disable()
> and enable are called at the same time.
It doesn't do any kind of locking, it just checks the variable. enable
and disable can still be run at the same time.
Tomi
prev parent reply other threads:[~2010-10-21 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 3:19 [PATCH V2] OMAP: DSS2: don't power off a panel twice Stanley.Miao
2010-08-11 6:50 ` Bryan Wu
2010-08-17 9:01 ` Bryan Wu
2010-08-17 9:27 ` stanley.miao
2010-08-17 9:48 ` Bryan Wu
2010-08-17 10:34 ` Tomi Valkeinen
2010-09-03 2:52 ` stanley.miao
2010-10-21 13:42 ` 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=1287668520.2142.52.camel@tubuntu \
--to=tomi.valkeinen@nokia.com \
--cc=bryan.wu@canonical.com \
--cc=linux-omap@vger.kernel.org \
--cc=lwalkera@gmail.com \
--cc=lwalkera@ieee.org \
--cc=mathieu.poirier@canonical.com \
--cc=stanley.miao@windriver.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