Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "José Relvas" <josemonsantorelvas@gmail.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [REQUEST] Add support for Intel DPST (Display Power Saving Technology)
Date: Tue, 16 Apr 2024 15:41:50 +0300	[thread overview]
Message-ID: <87edb5zdgx.fsf@intel.com> (raw)
In-Reply-To: <Zh5HtM6vG2xYsrT5@aquecedor-3-0>

On Tue, 16 Apr 2024, José Relvas <josemonsantorelvas@gmail.com> wrote:
> One more question. Some documentation refers to 
> "OPST (OLED power saving technology)". It's my understanding that this
> uses the same hardware blocks and APIs as DPST - only the algorithm
> in software is different. Userspace would need a way to distinguish
> OLED panels from LCD panels so it can use the right algorithm. Is
> there a reliable way of doing this? 
> On my Thinkpad P1 gen 6, the OLED exposes a standard intel_backlight,
> which actually controls the PWM. Afaik, there's no other way of
> telling OLED and LCD apart in userspace.

The intel_backlight interface can actually control the brightness of the
OLED panel using the DPCD interface, not only backlight PWM. It depends
on the panel. See intel_dp_aux_backlight.c. (And yes, backlight can be a
misnomer here, since OLED does not have a backlight.)

I don't actually know the details of OPST, but some OLED panels I've
worked with in the past have CABC, or content adaptive brightness
control, where all of it is handled internally in the panel. You just
tune the aggressiveness or some other mode.

BR,
Jani.



-- 
Jani Nikula, Intel

      reply	other threads:[~2024-04-16 12:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 13:58 [REQUEST] Add support for Intel DPST (Display Power Saving Technology) José Relvas
2024-04-16  8:00 ` Jani Nikula
2024-04-16  9:41   ` José Relvas
2024-04-16 12:41     ` Jani Nikula [this message]

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=87edb5zdgx.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=josemonsantorelvas@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox