From: Mario Limonciello <mario.limonciello@amd.com>
To: <amd-gfx@lists.freedesktop.org>,
Alex Deucher <alexander.deucher@amd.com>,
Harry Wentland <harry.wentland@amd.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Hans de Goede <hdegoede@redhat.com>
Cc: "open list:ACPI" <linux-acpi@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
Melissa Wen <mwen@igalia.com>,
"Mark Pearson" <mpearson-lenovo@squebb.ca>,
Mario Limonciello <mario.limonciello@amd.com>
Subject: [PATCH v2 0/4] Add support for fetching EDID from ACPI _DDC
Date: Tue, 30 Jan 2024 13:26:04 -0600 [thread overview]
Message-ID: <20240130192608.11666-1-mario.limonciello@amd.com> (raw)
Some laptops ship an EDID in the BIOS encoded in the _DDC method that
differs than the EDID directly on the laptop panel for $REASONS.
This is the EDID that is used by the AMD Windows driver, and so sometimes
different results are found in different operating systems.
This series adds a new DRM helper that will use acpi_video to fetch the
EDID.
On amdgpu when an eDP panel is found the BIOS
is checked first for an EDID and that used as a preference if found.
On nouveau it replaces the previous local function doing a similar role.
This does *not* use struct drm_edid as this will require more involved
amdgpu display driver work that will come separately as part of follow-ups
to: https://lore.kernel.org/amd-gfx/20240126163429.56714-1-mwen@igalia.com/
Mario Limonciello (4):
ACPI: video: Handle fetching EDID that is longer than 256 bytes
drm: Add drm_get_acpi_edid() helper
drm/amd: Fetch the EDID from _DDC if available for eDP
drm/nouveau: Use drm_get_acpi_edid() helper
drivers/acpi/acpi_video.c | 25 +++----
drivers/gpu/drm/Kconfig | 4 +
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 1 +
.../gpu/drm/amd/amdgpu/amdgpu_connectors.c | 4 +
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 8 ++
.../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 10 ++-
.../amd/display/amdgpu_dm/amdgpu_dm_helpers.c | 9 ++-
drivers/gpu/drm/drm_edid.c | 73 +++++++++++++++++++
drivers/gpu/drm/nouveau/nouveau_acpi.c | 27 -------
drivers/gpu/drm/nouveau/nouveau_acpi.h | 2 -
drivers/gpu/drm/nouveau/nouveau_connector.c | 2 +-
include/drm/drm_edid.h | 1 +
12 files changed, 115 insertions(+), 51 deletions(-)
--
2.34.1
next reply other threads:[~2024-01-30 19:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 19:26 Mario Limonciello [this message]
2024-01-30 19:26 ` [PATCH v2 1/4] ACPI: video: Handle fetching EDID that is longer than 256 bytes Mario Limonciello
2024-01-30 19:26 ` [PATCH v2 2/4] drm: Add drm_get_acpi_edid() helper Mario Limonciello
2024-01-31 7:53 ` kernel test robot
2024-01-31 9:01 ` kernel test robot
2024-01-31 9:34 ` kernel test robot
2024-01-31 10:37 ` kernel test robot
2024-01-31 15:00 ` kernel test robot
2024-01-30 19:26 ` [PATCH v2 3/4] drm/amd: Fetch the EDID from _DDC if available for eDP Mario Limonciello
2024-01-30 19:26 ` [PATCH v2 4/4] drm/nouveau: Use drm_get_acpi_edid() helper Mario Limonciello
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=20240130192608.11666-1-mario.limonciello@amd.com \
--to=mario.limonciello@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpearson-lenovo@squebb.ca \
--cc=mwen@igalia.com \
--cc=rafael@kernel.org \
/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
all inboxes | Powered by JetHome®