[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAA8EJpre_HOY1xzOZPv5gPiJ-kEZEJiEm8oyYzXTiPj66vY8aw@mail.gmail.com>
Date: Tue, 27 Feb 2024 02:37:12 +0200
From: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
To: Hsin-Yi Wang <hsinyi@...omium.org>
Cc: Douglas Anderson <dianders@...omium.org>, Neil Armstrong <neil.armstrong@...aro.org>,
Jessica Zhang <quic_jesszhan@...cinc.com>, Sam Ravnborg <sam@...nborg.org>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>, Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>, David Airlie <airlied@...il.com>, Daniel Vetter <daniel@...ll.ch>,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] Match panel hash for overridden mode
On Sat, 24 Feb 2024 at 00:40, Hsin-Yi Wang <hsinyi@...omium.org> wrote:
>
> This series is a follow up for 1a5e81de180e ("Revert "drm/panel-edp: Add
> auo_b116xa3_mode""). It's found that 2 different AUO panels use the same
> product id. One of them requires an overridden mode, while the other should
> use the mode directly from edid.
>
> Since product id match is no longer sufficient, EDP_PANEL_ENTRY2 is extended
> to check the crc hash of the entire edid base block.
Do you have these EDIDs posted somewhere? Can we use something less
cryptic than hash for matching the panel, e.g. strings from Monitor
Descriptors?
>
> Hsin-Yi Wang (2):
> drm_edid: Add a function to get EDID base block
> drm/panel: panel-edp: Match with panel hash for overridden modes
>
> drivers/gpu/drm/drm_edid.c | 55 +++++++++++++++-------------
> drivers/gpu/drm/panel/panel-edp.c | 60 ++++++++++++++++++++++++++-----
> include/drm/drm_edid.h | 3 +-
> 3 files changed, 84 insertions(+), 34 deletions(-)
>
> --
> 2.44.0.rc0.258.g7320e95886-goog
>
--
With best wishes
Dmitry
Powered by blists - more mailing lists