All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Rob Clark <robdclark@gmail.com>
Cc: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Vinay Simha <simhavcs@gmail.com>,
	Archit Taneja <archit.taneja@gmail.com>
Subject: Re: [nexus7-flo] backlight brightness
Date: Mon, 2 May 2016 09:26:38 +0200	[thread overview]
Message-ID: <20160502072638.GD27465@ulmo.ba.sec> (raw)
In-Reply-To: <CAF6AEGs5xTmncDon5oDDEZg8nWkQw+_i5BKGjTfUgCqZ9W3F6Q@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1538 bytes --]

On Fri, Apr 29, 2016 at 08:04:09AM -0400, Rob Clark wrote:
> On Fri, Apr 29, 2016 at 1:32 AM, Vinay Simha <simhavcs@gmail.com> wrote:
> > hi,
> >
> > In nx7, backlight brightness control is controlled by dcs commands of
> > MIPI_DCS_SET_DISPLAY_BRIGHTNESS.
> > there is no PWM going to panel interface directly as we have in ifc6410/nx5
> 
> afaiu it is not uncommon to need to control backlight via panel (ie, I
> think basically all adaptive-backlight panels).  I think the answer is
> for these panels, the panel driver would register it's own backlight
> driver, rather than get a (pwm, etc) backlight via dt bindings.

Yes, that'd be my recommendation as well.

> Possibly if the backlight commands are standardized enough then we
> could implement a single drm_panel_dsi_backlight helper which could be
> created by any of the dsi adaptive-backlight panels (ie. pass in a
> 'struct mipi_dsi_device *').. something like:
> 
> struct drm_panel_dsi_backlight {
>     struct mipi_panel_dsi_device *link;
>     ...
> }
> 
> struct backlight_device *drm_panel_create_dsi_backlight(struct
> mipi_panel_dsi_device *link)
> {
>     struct drm_panel_dsi_backlight *dsi_bl;
>     ...
>     return devm_backlight_device_register(&link->dev, ..., dsi_bl,
> dsi_bl_ops, props);
> }

I agree it would make sense to have a DCS specific helper for backlight.
I'm somewhat sceptical about the standardization, even though these seem
to be part of DCS 1.3. But perhaps we can start by being optimistic.

Thierry

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-05-02  7:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGWqDJ6agcOZQWXPn9JGyh-pMfWk1cr4=poRaP7B5DymjNPOBA@mail.gmail.com>
2016-04-29 12:04 ` [nexus7-flo] backlight brightness Rob Clark
2016-05-02  7:26   ` Thierry Reding [this message]
2016-05-03  4:56     ` Vinay Simha
2016-05-13  1:04       ` John Stultz

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=20160502072638.GD27465@ulmo.ba.sec \
    --to=thierry.reding@gmail.com \
    --cc=archit.taneja@gmail.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=robdclark@gmail.com \
    --cc=simhavcs@gmail.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.