From: Daniel Kurtz <djkurtz@chromium.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5] pwm-backlight: Avoid backlight flicker when probed from DT
Date: Mon, 07 Dec 2015 04:20:26 +0000 [thread overview]
Message-ID: <CAGS+omCD3MLB+hf4R1aD+YZuB4SV8nu71oAm6V_bkfoE2im49A@mail.gmail.com> (raw)
In-Reply-To: <20151124162658.GJ807@x1>
Hi Lee,
On Wed, Nov 25, 2015 at 12:26 AM, Lee Jones <lee.jones@linaro.org> wrote:
> On Wed, 18 Nov 2015, Philipp Zabel wrote:
>
>> If the driver is probed from the device tree, and there is a phandle
>> property set on it, and the enable GPIO is already configured as output,
>> and the backlight is currently disabled, keep it disabled.
>> If all these conditions are met, assume there will be some other driver
>> that can enable the backlight at the appropriate time.
>>
>> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
>> Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
>> Tested-by: Heiko Stuebner <heiko@sntech.de>
>> ---
>> - Rebased onto v4.4-rc1
>> - Added Heiko's Tested-by
>> ---
>> drivers/video/backlight/pwm_bl.c | 23 ++++++++++++++++++++++-
>> 1 file changed, 22 insertions(+), 1 deletion(-)
>
> Applied, thanks.
Hmm, where was this applied? I do not see it in:
* v4.4-rc4
* linux-next next-20151203 (dcccebc - Add linux-next specific files
for 20151203)
Nor do I see it in any branch in:
* git://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight
Is this the right git?
By the way this repository has a git tag called "HEAD", which is a bit
annoying since every time I "git remote update" from here, git gets
confused until I manually delete it (git tag -d HEAD).
Thanks,
-Dan
next prev parent reply other threads:[~2015-12-07 4:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 17:12 [PATCH v5] pwm-backlight: Avoid backlight flicker when probed from DT Philipp Zabel
2015-11-24 16:26 ` Lee Jones
2015-12-07 4:20 ` Daniel Kurtz [this message]
2015-12-07 9:35 ` Lee Jones
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=CAGS+omCD3MLB+hf4R1aD+YZuB4SV8nu71oAm6V_bkfoE2im49A@mail.gmail.com \
--to=djkurtz@chromium.org \
--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).