From: jg1.han@samsung.com (Jingoo Han)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv4] video: backlight: gpio-backlight: Add DT support.
Date: Mon, 04 Nov 2013 09:20:08 +0900 [thread overview]
Message-ID: <004101ced8f3$9e4e7ec0$daeb7c40$%han@samsung.com> (raw)
In-Reply-To: <20131101095754.GJ27864@ulmo.nvidia.com>
On Friday, November 01, 2013 6:58 PM, Thierry Reding wrote:
> On Fri, Nov 01, 2013 at 08:44:48AM +0900, Jingoo Han wrote:
>> On Friday, October 25, 2013 10:58 PM, Laurent Pinchart wrote:
>>> On Thursday 24 October 2013 13:05:25 Thierry Reding wrote:
[....]
>>>> Or is there still a reason to have more than a single bit for backlight
>>>> state? I don't know any hardware that actually makes a difference
>>>> between FB_BLANK_NORMAL, FB_BLANK_VSYNC_SUSPEND, FB_BLANK_HSYNC_SUSPEND
>>>> or FB_BLANK_POWERDOWN.
>>
>> On Exynos side, I have never seen that FB_BLANK_VSYNC_SUSPEND,
>> FB_BLANK_HSYNC_SUSPEND are used for controlling display panels or
>> Display controllers.
>>
>> However, I heard that FB_BLANK_VSYNC_SUSPEND, FB_BLANK_HSYNC_SUSPEND are
>> used for some monitors.
>
> I think that those may make sense in the context of fbdev, and looking
> at some fbdev drivers seems to substantiate that.
>
> However, I don't think backlights have any such capability. I mean they
> are either on or off, right? There's no such thing as partially off, or
> partially on. How would a backlight behave differently if the panel was
> in HSYNC suspend mode or VSYNC suspend mode?
Hi Thierry Reding.
I agree with you.
In the case of backlight, there is no need that a backlight behaves
differently in HSYNC suspend mode or VSYNC suspend mode.
Best regards,
Jingoo Han
next prev parent reply other threads:[~2013-11-04 0:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 15:04 [PATCH 01/11] of: add vendor prefix for Eukréa Electromatique Denis Carikli
2013-10-18 15:04 ` [PATCH 02/11] video: imxfb: Introduce regulator support Denis Carikli
2013-10-19 10:45 ` Jean-Christophe PLAGNIOL-VILLARD
2013-10-21 9:13 ` [PATCHv4] video: backlight: gpio-backlight: Add DT support Denis Carikli
2013-10-21 22:48 ` Laurent Pinchart
2013-10-22 5:11 ` Jean-Christophe PLAGNIOL-VILLARD
2013-10-22 4:58 ` Jean-Christophe PLAGNIOL-VILLARD
2013-10-22 7:23 ` Thierry Reding
2013-10-22 15:34 ` Jean-Christophe PLAGNIOL-VILLARD
2013-10-22 20:01 ` Thierry Reding
2013-10-23 13:42 ` Jean-Christophe PLAGNIOL-VILLARD
2013-10-23 16:49 ` Stephen Warren
2013-10-23 20:08 ` Thierry Reding
2013-10-23 16:51 ` Stephen Warren
2013-10-23 20:20 ` Thierry Reding
2013-10-23 22:38 ` Laurent Pinchart
2013-10-24 11:05 ` Thierry Reding
2013-10-25 13:57 ` Laurent Pinchart
2013-10-31 23:44 ` Jingoo Han
2013-11-01 9:57 ` Thierry Reding
2013-11-04 0:20 ` Jingoo Han [this message]
2013-10-31 23:37 ` Jingoo Han
2013-11-01 10:13 ` Thierry Reding
2013-11-06 0:08 ` Laurent Pinchart
2013-10-25 20:10 ` Grant Likely
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='004101ced8f3$9e4e7ec0$daeb7c40$%han@samsung.com' \
--to=jg1.han@samsung.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).