From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915/bios: Define block 46 chromaticity coordinates properly
Date: Thu, 06 Jun 2024 13:55:55 +0300 [thread overview]
Message-ID: <878qzibaro.fsf@intel.com> (raw)
In-Reply-To: <20240605134756.17099-1-ville.syrjala@linux.intel.com>
On Wed, 05 Jun 2024, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> The VBT spec does a very poor job of defining how the chromaticity
> coordinates in block 46 are laid out. After double checking the
> Windows implementation it turns out these more or less match the
> EDID definition, where the 10bit values are split into 2bit + 8bit
> chunks. Adjust our struct definition to reflect that.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_vbt_defs.h | 27 ++++++++++++-------
> 1 file changed, 17 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_vbt_defs.h b/drivers/gpu/drm/i915/display/intel_vbt_defs.h
> index 862c5923b83d..da8694771f69 100644
> --- a/drivers/gpu/drm/i915/display/intel_vbt_defs.h
> +++ b/drivers/gpu/drm/i915/display/intel_vbt_defs.h
> @@ -1376,16 +1376,23 @@ struct chromaticity {
> u8 chromaticity_from_edid_base_block:1;
> u8 rsvd:6;
>
> - u8 red_green;
> - u8 blue_white;
> - u8 red_x;
> - u8 red_y;
> - u8 green_x;
> - u8 green_y;
> - u8 blue_x;
> - u8 blue_y;
> - u8 white_x;
> - u8 white_y;
> + u8 green_y_lo:2;
> + u8 green_x_lo:2;
> + u8 red_y_lo:2;
> + u8 red_x_lo:2;
> + u8 white_y_lo:2;
> + u8 white_x_lo:2;
> + u8 blue_y_lo:2;
> + u8 blue_x_lo:2;
> +
> + u8 red_x_hi;
> + u8 red_y_hi;
> + u8 green_x_hi;
> + u8 green_y_hi;
> + u8 blue_x_hi;
> + u8 blue_y_hi;
> + u8 white_x_hi;
> + u8 white_y_hi;
> } __packed;
>
> struct bdb_chromaticity {
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-06-06 10:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 13:47 [PATCH 1/2] drm/i915/bios: Define block 46 chromaticity coordinates properly Ville Syrjala
2024-06-05 13:47 ` [PATCH 2/2] drm/i915/bios: Define the "luminance and gamma" sub-struct of block 46 Ville Syrjala
2024-06-06 10:56 ` Jani Nikula
2024-06-05 15:13 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915/bios: Define block 46 chromaticity coordinates properly Patchwork
2024-06-06 12:38 ` Ville Syrjälä
2024-06-06 10:55 ` 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=878qzibaro.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--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 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.