From: Pekka Paalanen <pekka.paalanen@haloniitty.fi>
To: Maxime Ripard <mripard@kernel.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
David Airlie <airlied@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Jani Nikula <jani.nikula@intel.com>
Subject: Re: [PATCH v2] drm/edid/firmware: Remove built-in EDIDs
Date: Wed, 21 Feb 2024 13:07:31 +0200 [thread overview]
Message-ID: <20240221130731.70664a22@eldfell> (raw)
In-Reply-To: <20240221092636.691701-1-mripard@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2994 bytes --]
On Wed, 21 Feb 2024 10:26:36 +0100
Maxime Ripard <mripard@kernel.org> wrote:
> The EDID firmware loading mechanism introduced a few built-in EDIDs that
> could be forced on any connector, bypassing the EDIDs it exposes.
>
> While convenient, this limited set of EDIDs doesn't take into account
> the connector type, and we can end up with an EDID that is completely
> invalid for a given connector.
>
> For example, the edid/800x600.bin file matches the following EDID:
...
>
> So, an analog monitor EDID. However, if the connector was an HDMI
> monitor for example, it breaks the HDMI specification that requires,
> among other things, a digital display, the VIC 1 mode and an HDMI Forum
> Vendor Specific Data Block in an CTA-861 extension.
>
> We thus end up with a completely invalid EDID, which thus might confuse
> HDMI-related code that could parse it.
>
> After some discussions on IRC, we identified mainly two ways to fix
> this:
>
> - We can either create more EDIDs for each connector type to provide
> a built-in EDID that matches the resolution passed in the name, and
> still be a sensible EDID for that connector type;
>
> - Or we can just prevent the EDID to be exposed to userspace if it's
> built-in.
>
> Or possibly both.
>
> However, the conclusion was that maybe we just don't need the built-in
> EDIDs at all and we should just get rid of them. So here we are.
Sounds good to me.
Acked-by: Pekka Paalanen <pekka.paalanen@collabora.com>
If it turns out that these cannot be completely removed, then yet
another option would to refuse to use these on digital connectors.
Thanks,
pq
>
> Acked-by: Thomas Zimmermann <tzimmermann@suse.de>
> Signed-off-by: Maxime Ripard <mripard@kernel.org>
> ---
> Documentation/admin-guide/edid.rst | 35 +--
> .../admin-guide/kernel-parameters.txt | 14 +-
> drivers/gpu/drm/drm_edid_load.c | 160 +---------
> tools/edid/1024x768.S | 43 ---
> tools/edid/1280x1024.S | 43 ---
> tools/edid/1600x1200.S | 43 ---
> tools/edid/1680x1050.S | 43 ---
> tools/edid/1920x1080.S | 43 ---
> tools/edid/800x600.S | 40 ---
> tools/edid/Makefile | 37 ---
> tools/edid/edid.S | 274 ------------------
> tools/edid/hex | 1 -
> 12 files changed, 18 insertions(+), 758 deletions(-)
> delete mode 100644 tools/edid/1024x768.S
> delete mode 100644 tools/edid/1280x1024.S
> delete mode 100644 tools/edid/1600x1200.S
> delete mode 100644 tools/edid/1680x1050.S
> delete mode 100644 tools/edid/1920x1080.S
> delete mode 100644 tools/edid/800x600.S
> delete mode 100644 tools/edid/Makefile
> delete mode 100644 tools/edid/edid.S
> delete mode 100644 tools/edid/hex
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-21 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 9:26 [PATCH v2] drm/edid/firmware: Remove built-in EDIDs Maxime Ripard
2024-02-21 11:07 ` Pekka Paalanen [this message]
2024-02-26 11:24 ` Jani Nikula
2024-02-26 12:08 ` Maxime Ripard
2024-02-26 13:14 ` (subset) " Maxime Ripard
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=20240221130731.70664a22@eldfell \
--to=pekka.paalanen@haloniitty.fi \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dave.stevenson@raspberrypi.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox