linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: haojian.zhuang@gmail.com (Haojian Zhuang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 06/09] backlight: enable backlight in 88pm860x
Date: Mon, 11 Jan 2010 03:32:10 -0500	[thread overview]
Message-ID: <771cded01001110032s7fe62605g72cdb50b73d0d53@mail.gmail.com> (raw)
In-Reply-To: <1262953648.10097.34.camel@dax.rpnet.com>

On Fri, Jan 8, 2010 at 7:27 AM, Richard Purdie <rpurdie@rpsys.net> wrote:
> On Fri, 2010-01-08 at 12:06 +0100, Samuel Ortiz wrote:
>> Hi Haojian, Richard,
>>
>> On Wed, Dec 09, 2009 at 08:15:28AM -0500, Haojian Zhuang wrote:
>> > From 8d2bc9826f758f113fde6f3fd01723111fbf2a91 Mon Sep 17 00:00:00 2001
>> > From: Haojian Zhuang <haojian.zhuang@marvell.com>
>> > Date: Mon, 9 Nov 2009 12:41:07 -0500
>> > Subject: [PATCH] backlight: enable backlight in 88pm860x
>> >
>> > At most, three backlight device can be supported in 88pm860x driver.
>> I applied this patch and the LED one to my for-next branch.
>> Richard, whenever you have time for that, could you please quickly check if
>> they oook ok to you ? They're 2.6.34 material, so no rush here.
>
> I had a look through, they look basically ok.
>
> In the LED patch I'm not sure I like the SET_BRIGHTNESS and SET_BLINK
> sharing of a workqueue though. Its not going to crash, I can just see
> values potentially getting lost as the code has a race condition. It
> would be easier if it just compared led->current_brightness to
> led->brightness acting if needed and something similar for LED blinking.
>
> Cheers,
>
> Richard
>

Excuse me that there's a mutex lock in __led_set(). Both
SET_BRIGHTNESS & SET_BLINK calls __led_set(). There shouldn't be race
condition on set led. What's your opinion?

Best Regards
Haojian

  reply	other threads:[~2010-01-11  8:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09 13:15 [PATCH v2 06/09] backlight: enable backlight in 88pm860x Haojian Zhuang
2010-01-08 11:06 ` Samuel Ortiz
2010-01-08 12:27   ` Richard Purdie
2010-01-11  8:32     ` Haojian Zhuang [this message]
2010-01-12  9:32       ` Richard Purdie

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=771cded01001110032s7fe62605g72cdb50b73d0d53@mail.gmail.com \
    --to=haojian.zhuang@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).