All of lore.kernel.org
 help / color / mirror / Atom feed
From: "stanley.miao" <stanley.miao@windriver.com>
To: Tomi Valkeinen <tomi.valkeinen@nokia.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,
	Mathieu Poirier <mathieu.poirier@canonical.com>
Subject: Re: [PATCH V2] OMAP: DSS2: don't power off a panel twice
Date: Fri, 03 Sep 2010 10:52:46 +0800	[thread overview]
Message-ID: <4C8062FE.9090004@windriver.com> (raw)
In-Reply-To: <1282041251.2348.24.camel@tubuntu.research.nokia.com>

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.
If so, what kind of result do you want ? enabled or disabled ?

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.

Stanley.

>  Tomi
>
>
>
>   


  reply	other threads:[~2010-09-03  2:53 UTC|newest]

Thread overview: 10+ 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:27       ` stanley.miao
2010-08-17  9:48       ` Bryan Wu
2010-08-17  9:48         ` Bryan Wu
2010-08-17 10:34 ` Tomi Valkeinen
2010-09-03  2:52   ` stanley.miao [this message]
2010-10-21 13:42     ` 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=4C8062FE.9090004@windriver.com \
    --to=stanley.miao@windriver.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=tomi.valkeinen@nokia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.