From: "Jouni Högander" <jouni.hogander@intel.com>
To: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
amd-gfx@lists.freedesktop.org
Cc: "Jani Nikula" <jani.nikula@intel.com>,
"Rodrigo Siqueira" <Rodrigo.Siqueira@amd.com>,
"Roman Li" <roman.li@amd.com>,
"Manasi Navare" <manasi.d.navare@intel.com>,
"Mika Kahola" <mika.kahola@intel.com>,
"Jouni Högander" <jouni.hogander@intel.com>
Subject: [PATCH v3 0/3] HDR aux backlight range calculation
Date: Tue, 19 Jul 2022 12:56:57 +0300 [thread overview]
Message-ID: <20220719095700.14923-1-jouni.hogander@intel.com> (raw)
This patch set splits out static hdr metadata backlight range parsing
from gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c into gpu/drm/drm-edid.c
as a new function. This new function is then used during edid parsing
when HDR static metadata block parsing.
Calculated values are stored in a new struct drm_luminance_range
introduced into display_info. Amdgpu_dm.c and intel_dp_aux_backlight.c
are using this new data.
v3: Some clean-ups suggested by Jani Nikula
v2: Calculate the range during edid parsing and store into display_info
Cc: Roman Li <roman.li@amd.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
Cc: Harry Wentland <harry.wentland@amd.com>
Cc: Lyude Paul <lyude@redhat.com>
Cc: Mika Kahola <mika.kahola@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>
Cc: Manasi Navare <manasi.d.navare@intel.com>
Jouni Högander (3):
drm: New function to get luminance range based on static hdr metadata
drm/amdgpu_dm: Rely on split out luminance calculation function
drm/i915: Use luminance range calculated during edid parsing
.../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 35 ++-----------
drivers/gpu/drm/drm_edid.c | 52 ++++++++++++++++++-
.../drm/i915/display/intel_dp_aux_backlight.c | 15 +++++-
include/drm/drm_connector.h | 21 ++++++++
4 files changed, 89 insertions(+), 34 deletions(-)
--
2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: "Jouni Högander" <jouni.hogander@intel.com>
To: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
amd-gfx@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@intel.com>,
Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
Roman Li <roman.li@amd.com>,
Harry Wentland <harry.wentland@amd.com>
Subject: [Intel-gfx] [PATCH v3 0/3] HDR aux backlight range calculation
Date: Tue, 19 Jul 2022 12:56:57 +0300 [thread overview]
Message-ID: <20220719095700.14923-1-jouni.hogander@intel.com> (raw)
This patch set splits out static hdr metadata backlight range parsing
from gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c into gpu/drm/drm-edid.c
as a new function. This new function is then used during edid parsing
when HDR static metadata block parsing.
Calculated values are stored in a new struct drm_luminance_range
introduced into display_info. Amdgpu_dm.c and intel_dp_aux_backlight.c
are using this new data.
v3: Some clean-ups suggested by Jani Nikula
v2: Calculate the range during edid parsing and store into display_info
Cc: Roman Li <roman.li@amd.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
Cc: Harry Wentland <harry.wentland@amd.com>
Cc: Lyude Paul <lyude@redhat.com>
Cc: Mika Kahola <mika.kahola@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>
Cc: Manasi Navare <manasi.d.navare@intel.com>
Jouni Högander (3):
drm: New function to get luminance range based on static hdr metadata
drm/amdgpu_dm: Rely on split out luminance calculation function
drm/i915: Use luminance range calculated during edid parsing
.../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 35 ++-----------
drivers/gpu/drm/drm_edid.c | 52 ++++++++++++++++++-
.../drm/i915/display/intel_dp_aux_backlight.c | 15 +++++-
include/drm/drm_connector.h | 21 ++++++++
4 files changed, 89 insertions(+), 34 deletions(-)
--
2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: "Jouni Högander" <jouni.hogander@intel.com>
To: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
amd-gfx@lists.freedesktop.org
Cc: "Jani Nikula" <jani.nikula@intel.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Rodrigo Siqueira" <Rodrigo.Siqueira@amd.com>,
"Roman Li" <roman.li@amd.com>,
"Manasi Navare" <manasi.d.navare@intel.com>,
"Mika Kahola" <mika.kahola@intel.com>,
"Jouni Högander" <jouni.hogander@intel.com>,
"Harry Wentland" <harry.wentland@amd.com>
Subject: [PATCH v3 0/3] HDR aux backlight range calculation
Date: Tue, 19 Jul 2022 12:56:57 +0300 [thread overview]
Message-ID: <20220719095700.14923-1-jouni.hogander@intel.com> (raw)
This patch set splits out static hdr metadata backlight range parsing
from gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c into gpu/drm/drm-edid.c
as a new function. This new function is then used during edid parsing
when HDR static metadata block parsing.
Calculated values are stored in a new struct drm_luminance_range
introduced into display_info. Amdgpu_dm.c and intel_dp_aux_backlight.c
are using this new data.
v3: Some clean-ups suggested by Jani Nikula
v2: Calculate the range during edid parsing and store into display_info
Cc: Roman Li <roman.li@amd.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
Cc: Harry Wentland <harry.wentland@amd.com>
Cc: Lyude Paul <lyude@redhat.com>
Cc: Mika Kahola <mika.kahola@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>
Cc: Manasi Navare <manasi.d.navare@intel.com>
Jouni Högander (3):
drm: New function to get luminance range based on static hdr metadata
drm/amdgpu_dm: Rely on split out luminance calculation function
drm/i915: Use luminance range calculated during edid parsing
.../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 35 ++-----------
drivers/gpu/drm/drm_edid.c | 52 ++++++++++++++++++-
.../drm/i915/display/intel_dp_aux_backlight.c | 15 +++++-
include/drm/drm_connector.h | 21 ++++++++
4 files changed, 89 insertions(+), 34 deletions(-)
--
2.25.1
next reply other threads:[~2022-07-19 9:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 9:56 Jouni Högander [this message]
2022-07-19 9:56 ` [PATCH v3 0/3] HDR aux backlight range calculation Jouni Högander
2022-07-19 9:56 ` [Intel-gfx] " Jouni Högander
2022-07-19 9:56 ` [PATCH v3 1/3] drm: New function to get luminance range based on static hdr metadata Jouni Högander
2022-07-19 9:56 ` Jouni Högander
2022-07-19 9:56 ` [Intel-gfx] " Jouni Högander
2022-07-19 9:56 ` [PATCH v3 2/3] drm/amdgpu_dm: Rely on split out luminance calculation function Jouni Högander
2022-07-19 9:56 ` Jouni Högander
2022-07-19 9:56 ` [Intel-gfx] " Jouni Högander
2022-08-04 9:54 ` Jani Nikula
2022-08-04 9:54 ` Jani Nikula
2022-08-04 9:54 ` Jani Nikula
2022-08-11 17:43 ` [Intel-gfx] " Deucher, Alexander
2022-08-11 17:43 ` Deucher, Alexander
2022-08-11 17:43 ` Deucher, Alexander
2022-08-12 7:04 ` Jani Nikula
2022-08-12 7:04 ` Jani Nikula
2022-08-12 7:04 ` [Intel-gfx] " Jani Nikula
2022-07-19 9:57 ` [PATCH v3 3/3] drm/i915: Use luminance range calculated during edid parsing Jouni Högander
2022-07-19 9:57 ` [Intel-gfx] " Jouni Högander
2022-07-19 14:47 ` [Intel-gfx] ✓ Fi.CI.BAT: success for HDR aux backlight range calculation Patchwork
2022-07-19 23:07 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=20220719095700.14923-1-jouni.hogander@intel.com \
--to=jouni.hogander@intel.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=manasi.d.navare@intel.com \
--cc=mika.kahola@intel.com \
--cc=roman.li@amd.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.