From: Thomas Zimmermann <tzimmermann@suse.de>
To: Jammy Huang <jammy_huang@aspeedtech.com>,
Dave Airlie <airlied@redhat.com>,
Jocelyn Falempe <jfalempe@redhat.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
jani.nikula@linux.intel.com, ville.syrjala@linux.intel.com
Subject: Re: [PATCH v3] drm/ast: DisplayPort edid supports 256 bytes
Date: Thu, 20 Aug 2026 08:29:18 +0200 [thread overview]
Message-ID: <e36b76e7-3b11-4bef-8e08-ad1bbfd77f96@suse.de> (raw)
In-Reply-To: <20260819-upstream_ast_dp_edid-v3-1-15d36c28afe2@aspeedtech.com>
Hi
Am 19.08.26 um 07:58 schrieb Jammy Huang:
> DisplayPort supports EDID up to 256 bytes (blocks 0 and 1). Update the
> block check to allow these two blocks. For any block beyond that
> (i.e. the monitor's EDID is larger than the 256 bytes ASPEED DP can
> hold), report it as an all-zero block instead of a read failure.
>
> Also remove the manual checksum/extension-count patch of block 0's
> last four bytes. That code was already dead, so the condition can never
> be true.
>
> Signed-off-by: Jammy Huang <jammy_huang@aspeedtech.com>
I know it's controversial, but there appears to be no better solution
now. Therefore
Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
Best regards
Thomas
> ---
> ASPEED DisplayPort's EDID size can be 256 bytes at most. Thus, EDID
> blocks fetched can be 0 and 1.
> ---
> Changes in v3:
> - For block > 1, write a zeroed buffer. Returning a zeroed block
> instead makes drm_edid's block checker classify it as
> EDID_BLOCK_ZERO, which is treated as a non-fatal invalid block.
> - Link to v2: https://lore.kernel.org/r/20260317-upstream_ast_dp_edid-v2-1-31166703c491@aspeedtech.com
>
> Changes in v2:
> Becasue drm-edid will handle invalid EDID if happen, we have 2 changes
> below.
> - Return 0 for the number of block more than 1.
> - Remove modification of EDID
> - Link to v1: https://lore.kernel.org/r/20260313-upstream_ast_dp_edid-v1-1-2a75b7c091b2@aspeedtech.com
> ---
> drivers/gpu/drm/ast/ast_dp.c | 24 ++++++++----------------
> 1 file changed, 8 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/gpu/drm/ast/ast_dp.c b/drivers/gpu/drm/ast/ast_dp.c
> index 9d07dad358c..38530cd126c 100644
> --- a/drivers/gpu/drm/ast/ast_dp.c
> +++ b/drivers/gpu/drm/ast/ast_dp.c
> @@ -88,8 +88,14 @@ static int ast_astdp_read_edid_block(void *data, u8 *buf, unsigned int block, si
> int ret = 0;
> unsigned int i;
>
> - if (block > 0)
> - return -EIO; /* extension headers not supported */
> + if (block > 1) {
> + /* ASPEED DP's EDID buffer holds blocks 0 and 1 only (256
> + * bytes). Report anything beyond that as an all-zero block
> + * rather than a read failure.
> + */
> + memset(buf, 0, len);
> + return 0;
> + }
>
> /*
> * Protect access to I/O registers from concurrent modesetting
> @@ -154,20 +160,6 @@ static int ast_astdp_read_edid_block(void *data, u8 *buf, unsigned int block, si
> ediddata[2] = ast_get_index_reg(ast, AST_IO_VGACRI, 0xda);
> ediddata[3] = ast_get_index_reg(ast, AST_IO_VGACRI, 0xdb);
>
> - if (i == 31) {
> - /*
> - * For 128-bytes EDID_1.3,
> - * 1. Add the value of Bytes-126 to Bytes-127.
> - * The Bytes-127 is Checksum. Sum of all 128bytes should
> - * equal 0 (mod 256).
> - * 2. Modify Bytes-126 to be 0.
> - * The Bytes-126 indicates the Number of extensions to
> - * follow. 0 represents noextensions.
> - */
> - ediddata[3] = ediddata[3] + ediddata[2];
> - ediddata[2] = 0;
> - }
> -
> memcpy(buf, ediddata, min((len - i), 4));
> buf += 4;
> }
>
> ---
> base-commit: 5ee8dbf54602dc340d6235b1d6aa17c0f283f48c
> change-id: 20260313-upstream_ast_dp_edid-5fe6adf7ad36
>
> Best regards,
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Jochen Jaser, Andrew McDonald, (HRB 36809, AG Nürnberg)
prev parent reply other threads:[~2026-08-20 6:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 5:58 Jammy Huang
2026-08-20 6:29 ` Thomas Zimmermann [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=e36b76e7-3b11-4bef-8e08-ad1bbfd77f96@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jammy_huang@aspeedtech.com \
--cc=jani.nikula@linux.intel.com \
--cc=jfalempe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--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 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®