mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arun KS <getarunks@gmail.com>
To: Eric Miao <eric.y.miao@gmail.com>
Cc: Haojian Zhuang <haojian.zhuang@gmail.com>,
	linux-kernel@vger.kernel.org, rpurdie@rpsys.net,
	eric.miao@marvell.com, mike@compulab.co.il
Subject: Re: [PATCH] Adding LED1 & LED2 control for DA9034 backlight driver
Date: Mon, 21 Sep 2009 11:07:58 -0700	[thread overview]
Message-ID: <dfeb90390909211107m1c61f8a9h5606059b6aabb7ee@mail.gmail.com> (raw)
In-Reply-To: <f17812d70909211008j62967af7qdf3456be722a9e13@mail.gmail.com>

On Mon, Sep 21, 2009 at 10:08 AM, Eric Miao <eric.y.miao@gmail.com> wrote:
>
> > Apparently there is a bug in the hardware design on my custom board. We are
> > using LED1 for backlight control.
> > Thanks Haojian for clarification.
> >
>
> Now you know that :-)
>
> Either let your hardware engineer change the design, or there are still
> workarounds, you can control the LED1/2 through the sysfs entries.

If I apply the patch which I send, backlight driver is working well
through the da093x_bl.c driver.
Because LED1 driver is same as the WLED driver apart from current
level it can provide. WLED can provide max of 32mA but LED can only
provide current <500uA.

Thanks for your concern.

Arun

>
> - eric

  reply	other threads:[~2009-09-21 18:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 19:27 getarunks
2009-09-18  9:10 ` Eric Miao
     [not found]   ` <771cded00909210049g6c7c8075pe4ca331184e39415@mail.gmail.com>
     [not found]     ` <dfeb90390909211003h3b16e984q1fdf94450bdb39@mail.gmail.com>
2009-09-21 17:08       ` Eric Miao
2009-09-21 18:07         ` Arun KS [this message]
2009-09-21 21:10   ` Richard Purdie
  -- strict thread matches above, loose matches on Subject: below --
2009-09-17 19:30 getarunks
2009-09-17 18:56 getarunks

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=dfeb90390909211107m1c61f8a9h5606059b6aabb7ee@mail.gmail.com \
    --to=getarunks@gmail.com \
    --cc=eric.miao@marvell.com \
    --cc=eric.y.miao@gmail.com \
    --cc=haojian.zhuang@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@compulab.co.il \
    --cc=rpurdie@rpsys.net \
    /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
all inboxes | Powered by JetHome®