AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Melissa Wen <mwen@igalia.com>, Alex Hung <alex.hung@amd.com>,
	Mario Limonciello <mario.limonciello@amd.com>,
	Rodrigo Siqueira <siqueira@igalia.com>,
	harry.wentland@amd.com, sunpeng.li@amd.com,
	alexander.deucher@amd.com, christian.koenig@amd.com,
	airlied@gmail.com, simona@ffwll.ch
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	kernel-dev@igalia.com
Subject: Re: [PATCH 13/13] drm/amd/display: move dc_sink from dc_edid to drm_edid
Date: Mon, 14 Apr 2025 13:20:54 +0300	[thread overview]
Message-ID: <87cydft56h.fsf@intel.com> (raw)
In-Reply-To: <20250411201333.151335-14-mwen@igalia.com>

On Fri, 11 Apr 2025, Melissa Wen <mwen@igalia.com> wrote:
> +void dc_edid_copy_edid_to_sink(struct dc_sink *sink)
> +{
> +	const struct edid *edid;
> +	uint32_t edid_length;
> +
> +	edid = drm_edid_raw(sink->drm_edid); // FIXME: Get rid of drm_edid_raw()
> +	edid_length = EDID_LENGTH * (edid->extensions + 1);

I guess none of my concern, really, but here's a hint:

The underlying reason for me to create struct drm_edid to begin with,
make it opaque, and to go through all the trouble of converting tons of
code from struct edid to struct drm_edid was exactly the above statement
being replicated all over the place. It's fundamentally incompatible
with the HF-EEODB EDID extension block.

BR,
Jani.



> +	memcpy(sink->dc_edid.raw_edid, (uint8_t *) edid, edid_length);
> +	sink->dc_edid.length = edid_length;
>  }
>  
>  

-- 
Jani Nikula, Intel

      reply	other threads:[~2025-04-14 10:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11 20:08 [PATCH 00/13] drm/amd/display: more drm_edid to AMD display driver Melissa Wen
2025-04-11 20:08 ` [PATCH 01/13] drm/amd/display: make sure drm_edid stored in aconnector doesn't leak Melissa Wen
2025-04-14 18:24   ` Mario Limonciello
2025-04-11 20:08 ` [PATCH 02/13] drm/amd/display: use drm_edid_product_id for parsing EDID product info Melissa Wen
2025-04-15  9:32   ` Michel Dänzer
2025-04-17 13:27     ` Melissa Wen
2025-04-17 13:57       ` Michel Dänzer
2025-04-11 20:08 ` [PATCH 03/13] drm/amd/display: parse display name from drm_eld Melissa Wen
2025-04-14 10:10   ` Jani Nikula
2025-04-17 13:46     ` Melissa Wen
2025-04-11 20:08 ` [PATCH 04/13] drm/amd/display: get panel id with drm_edid helper Melissa Wen
2025-04-11 20:08 ` [PATCH 05/13] drm/amd/display: get SAD from drm_eld when parsing EDID caps Melissa Wen
2025-04-11 20:08 ` [PATCH 06/13] drm/amd/display: get SADB " Melissa Wen
2025-04-11 20:08 ` [PATCH 07/13] drm/amd/display: simplify dm_helpers_parse_edid_caps signature Melissa Wen
2025-04-15 10:28   ` kernel test robot
2025-04-11 20:08 ` [PATCH 08/13] drm/amd/display: change DC functions to accept private types for edid Melissa Wen
2025-04-11 20:08 ` [PATCH 09/13] drm/amd/display: add a mid-layer file to handle EDID in DC Melissa Wen
2025-04-11 20:08 ` [PATCH 10/13] drm/amd/display: create a function to fill dc_sink with edid data Melissa Wen
2025-04-11 20:08 ` [PATCH 12/13] drm/amd/display: add drm_edid to dc_sink Melissa Wen
2025-04-11 20:08 ` [PATCH 13/13] drm/amd/display: move dc_sink from dc_edid to drm_edid Melissa Wen
2025-04-14 10:20   ` 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=87cydft56h.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=alex.hung@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=kernel-dev@igalia.com \
    --cc=mario.limonciello@amd.com \
    --cc=mwen@igalia.com \
    --cc=simona@ffwll.ch \
    --cc=siqueira@igalia.com \
    --cc=sunpeng.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox