From: Jani Nikula <jani.nikula@linux.intel.com>
To: Aurélien <aurelien.intel@ap2c.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Hans de Goede" <hdegoede@redhat.com>, Lyude <lyude@redhat.com>,
dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] Developing a new backlight driver for specific OLED screen
Date: Mon, 12 Sep 2022 11:44:37 +0300 [thread overview]
Message-ID: <87zgf556dm.fsf@intel.com> (raw)
In-Reply-To: <115b5a5ebddcd268ee5f7688400448a2@ap2c.com>
On Fri, 09 Sep 2022, "Aurélien" <aurelien.intel@ap2c.com> wrote:
> But since this display is independent from the GPU i didn't want to
> link both code.
If it's eDP and uses some proprietary DPCD brightness control mechanism,
I think in practice it usually is somewhat dependent on the GPU.
(OTOH I realize you don't mention eDP. If it's not eDP, DDC/CI is the
more likely way to control brightness than DPCD.)
> For sure. It's an OLED display. Thus there is no backlight. It uses
> specific registers to control the brightness of the screen.
As Lyude said, we have a bunch of "backlight" terminology for historical
reasons, but basically the DP aux, or DPCD, brightness control is mostly
agnostic to the display technology.
> Unfortunately I guess the mechanism is not shared with many OLED
> displays...
Do you have a spec for it? How does it differ from the VESA eDP DPCD
brightness control?
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-09-12 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 9:35 [Intel-gfx] Developing a new backlight driver for specific OLED screen Aurélien
2022-09-09 9:50 ` Rodrigo Vivi
2022-09-09 15:26 ` Jani Nikula
2022-09-09 15:49 ` Aurélien
2022-09-09 18:20 ` Lyude Paul
2022-09-12 8:44 ` Jani Nikula [this message]
2022-10-28 15:53 ` Aurélien
2022-10-31 8:40 ` Jani Nikula
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=87zgf556dm.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=aurelien.intel@ap2c.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lyude@redhat.com \
--cc=rodrigo.vivi@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox