Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Wick <sebastian.wick@redhat.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Suraj Kandpal <suraj.kandpal@intel.com>,
	intel-gfx@lists.freedesktop.org, uma.shankar@intel.com,
	ankit.k.nautiyal@intel.com
Subject: Re: drm/i915/dp: Enable AUX based backlight for HDR
Date: Mon, 18 Mar 2024 11:46:58 +0100	[thread overview]
Message-ID: <20240318104658.GB1004070@toolbox> (raw)
In-Reply-To: <ZfQ3Y46jdr5QrL_v@intel.com>

On Fri, Mar 15, 2024 at 01:56:19PM +0200, Ville Syrjälä wrote:
> On Fri, Mar 15, 2024 at 12:33:52PM +0100, Sebastian Wick wrote:
> > On Fri, Mar 15, 2024 at 10:35:30AM +0530, Suraj Kandpal wrote:
> <snip>
> > > @@ -318,11 +346,24 @@ intel_dp_aux_hdr_setup_backlight(struct intel_connector *connector, enum pipe pi
> > >  		panel->backlight.min = 0;
> > >  	}
> > >  
> > > +	if (DISPLAY_VER(i915) < 11) {
> > 
> > This should check for INTEL_EDP_HDR_TCON_SDP_COLORIMETRY_CAP instead!
> > There is no reason to bind this to any hardware version if the hardware
> > itself can tell you if it supports SDP signalling or needs to set it via
> > AUX.
> 
> That should be OK for icl+.
> 
> To extend this to pre-icl hardware I think we pretty much need both checks:
> - has_gamut_metadata_dip() -> can we actually transmit the SDP?
> - INTEL_EDP_HDR_TCON_SDP_COLORIMETRY_CAP -> can the tcon extract the data from the SDP?
> and if either is false then we fall back to AUX.

Right, that's something my patch is missing as well.

> We should also change intel_dp_add_properties() to check
> the tcon caps instead of relying on has_gamut_metadata_dip(),
> 	for eDP.
> 
> -- 
> Ville Syrjälä
> Intel
> 


  reply	other threads:[~2024-03-18 10:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 10:37 [PATCH] drm/i915/dp: Enable AUX based backlight for HDR Suraj Kandpal
2024-03-05 13:58 ` Jani Nikula
2024-03-05 23:00 ` ✗ Fi.CI.BAT: failure for " Patchwork
2024-03-06  8:59 ` [PATCH] " Suraj Kandpal
2024-03-06 12:26   ` Ville Syrjälä
2024-03-07  5:27     ` Kandpal, Suraj
2024-03-07 11:32       ` Ville Syrjälä
2024-03-07 10:29   ` Suraj Kandpal
2024-03-08 14:45     ` Borah, Chaitanya Kumar
2024-03-11  5:32     ` Suraj Kandpal
2024-03-15  5:05       ` Suraj Kandpal
2024-03-15 11:33         ` Sebastian Wick
2024-03-15 11:56           ` Ville Syrjälä
2024-03-18 10:46             ` Sebastian Wick [this message]
2024-03-06 19:07 ` ✓ Fi.CI.BAT: success for drm/i915/dp: Enable AUX based backlight for HDR (rev2) Patchwork
2024-03-07 12:20 ` ✓ Fi.CI.BAT: success for drm/i915/dp: Enable AUX based backlight for HDR (rev3) Patchwork
2024-03-07 14:59 ` ✗ Fi.CI.IGT: failure for drm/i915/dp: Enable AUX based backlight for HDR (rev2) Patchwork
2024-03-07 19:29 ` ✗ Fi.CI.IGT: failure for drm/i915/dp: Enable AUX based backlight for HDR (rev3) Patchwork
2024-03-12  0:06 ` ✓ Fi.CI.BAT: success for drm/i915/dp: Enable AUX based backlight for HDR (rev4) Patchwork
2024-03-12  8:06 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-03-15  7:52 ` ✗ Fi.CI.BAT: failure for drm/i915/dp: Enable AUX based backlight for HDR (rev5) Patchwork

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=20240318104658.GB1004070@toolbox \
    --to=sebastian.wick@redhat.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=suraj.kandpal@intel.com \
    --cc=uma.shankar@intel.com \
    --cc=ville.syrjala@linux.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