All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Timur Kristóf" <timur.kristof@gmail.com>
To: airlied@gmail.com, alexander.deucher@amd.com, alex.hung@amd.com,
	andrzej.hajda@intel.com, christian.koenig@amd.com,
	harry.wentland@amd.com, jernej.skrabec@gmail.com,
	jonas@kwiboo.se, Laurent.pinchart@ideasonboard.com,
	 maarten.lankhorst@linux.intel.com, mario.limonciello@amd.com,
	mripard@kernel.org, mwen@igalia.com, neil.armstrong@linaro.org,
	rfoss@kernel.org, simona@ffwll.ch, siqueira@igalia.com,
	sunpeng.li@amd.com, tzimmermann@suse.de,
	Melissa Wen <mwen@igalia.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
	Michel Daenzer <michel.daenzer@mailbox.org>,
	amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	kernel-dev@igalia.com
Subject: Re: [PATCH v8 0/8] drm/amd/display: more drm_edid to AMD display driver (partial)
Date: Fri, 27 Feb 2026 09:52:57 +0100	[thread overview]
Message-ID: <3856874.aCxCBeP46V@timur-hyperion> (raw)
In-Reply-To: <20260225121903.236115-1-mwen@igalia.com>

On Wednesday, February 25, 2026 1:04:29 PM Central European Standard Time 
Melissa Wen wrote:
> Hi,
> 
> This is a reduced version of `drm/amd/display: more drm_edid to AMD
> display driver` [1] sent a few months ago only with the less invasive
> changes, i.e., those changes that don't affect DC. This partial focus on
> using more drm_edid helpers instead of raw EDID helpers. Most patches
> here are already reviewed by someone and I think they can be merged
> without major concerns. They can also prevent new initiatives of keeping
> parsing raw EDID as driver specific code, which can make harder for us
> to remove `drm_edid_raw()`. They should focus on moving raw EDID
> handling to the DRM common code instead.
> 
> Regarding code changes from previous version, here I added some r-b tags
> (from Mario and Timur), fixed commit message syntax (Mario) and
> centralized error handling (Timur). I'll follow up the changes in DC to
> accept the Linux/DRM opaque object in a separate series since those look
> more sensitive.
> 
> [1] https://lore.kernel.org/amd-gfx/20251106165536.161662-1-mwen@igalia.com/
> 
> BR,
> 
> Melissa
> 

Nice work, Melissa.

Reviewed-by: Timur Kristóf <timur.kristof@gmail.com>
For this series.



  parent reply	other threads:[~2026-02-27  8:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25 12:04 [PATCH v8 0/8] drm/amd/display: more drm_edid to AMD display driver (partial) Melissa Wen
2026-02-25 12:04 ` [PATCH v8 1/8] drm/amd/display: make sure drm_edid stored in aconnector doesn't leak Melissa Wen
2026-02-25 12:04 ` [PATCH v8 2/8] drm/amd/display: start using drm_edid helpers to parse EDID caps Melissa Wen
2026-02-25 12:04 ` [PATCH v8 3/8] drm/amd/display: use drm_edid_product_id for parsing EDID product info Melissa Wen
2026-02-25 12:04 ` [PATCH v8 4/8] drm/amd/display: use drm_edid helper to set analog EDID caps Melissa Wen
2026-02-25 12:04 ` [PATCH v8 5/8] drm/edid: introduce a helper that gets monitor name from drm_edid Melissa Wen
2026-02-25 12:04 ` [PATCH v8 6/8] drm/amd/display: get panel id with drm_edid helper Melissa Wen
2026-02-25 12:04 ` [PATCH v8 7/8] drm/amd/display: get SAD from drm_eld when parsing EDID caps Melissa Wen
2026-02-25 12:04 ` [PATCH v8 8/8] drm/amd/display: get SADB " Melissa Wen
2026-02-27  8:52 ` Timur Kristóf [this message]
2026-03-31 15:45   ` [PATCH v8 0/8] drm/amd/display: more drm_edid to AMD display driver (partial) Leo Li
2026-04-13 17:51     ` Melissa Wen
2026-04-14 23:17       ` Leo Li
2026-04-15  7:23         ` Jani Nikula
2026-04-16 13:28         ` Melissa Wen

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=3856874.aCxCBeP46V@timur-hyperion \
    --to=timur.kristof@gmail.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=alex.hung@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=andrzej.hajda@intel.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=jani.nikula@linux.intel.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=kernel-dev@igalia.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mario.limonciello@amd.com \
    --cc=michel.daenzer@mailbox.org \
    --cc=mripard@kernel.org \
    --cc=mwen@igalia.com \
    --cc=neil.armstrong@linaro.org \
    --cc=rfoss@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=siqueira@igalia.com \
    --cc=sunpeng.li@amd.com \
    --cc=tzimmermann@suse.de \
    /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.