From: Doug Anderson <dianders@chromium.org>
To: Hsin-Yi Wang <hsinyi@chromium.org>
Cc: dri-devel@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>,
David Airlie <airlied@gmail.com>,
Jessica Zhang <quic_jesszhan@quicinc.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Sam Ravnborg <sam@ravnborg.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/panel-edp: Add ID for KD KD116N09-30NH-A016
Date: Mon, 6 May 2024 09:02:15 -0700 [thread overview]
Message-ID: <CAD=FV=UavcwPud8q57bWGPaJn4z0aP_abuBddhNh8eKVhjF4tg@mail.gmail.com> (raw)
In-Reply-To: <CAJMQK-h24xoO6jsYu4NK8ENoA6nsidcF8aN2pCzNMPgmu1NxEw@mail.gmail.com>
Hi,
On Thu, May 2, 2024 at 4:55 PM Hsin-Yi Wang <hsinyi@chromium.org> wrote:
>
> On Thu, May 2, 2024 at 4:48 PM Douglas Anderson <dianders@chromium.org> wrote:
> >
> > As evidenced by in-field reports, this panel shipped on pompom but we
> > never added the ID and thus we're stuck w/ conservative timings. The
> > panel was part of early patches but somehow got left off in the
> > end. :( Add it in now.
> >
> > For future reference, EDID from this panel is:
> > 00ffffffffffff002c82121200000000
> > 321e0104951a0e780ae511965e55932c
> > 19505400000001010101010101010101
> > 010101010101a41f5686500084302820
> > 55000090100000180000000000000000
> > 00000000000000000000000000000000
> > 000000000000000000000000000000fe
> > 004b443131364e3039333041313600f6
> >
> > We use the ASCII string from decoding the EDID ("KD116N0930A16") as
> > the panel name.
> >
> > Signed-off-by: Douglas Anderson <dianders@chromium.org>
>
> Reviewed-by: Hsin-Yi Wang <hsinyi@chromium.org>
Pushed to drm-misc-next:
a6cd27d92a96 drm/panel-edp: Add ID for KD KD116N09-30NH-A016
prev parent reply other threads:[~2024-05-06 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 23:47 [PATCH] drm/panel-edp: Add ID for KD KD116N09-30NH-A016 Douglas Anderson
2024-05-02 23:55 ` Hsin-Yi Wang
2024-05-06 16:02 ` Doug Anderson [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='CAD=FV=UavcwPud8q57bWGPaJn4z0aP_abuBddhNh8eKVhjF4tg@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hsinyi@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_jesszhan@quicinc.com \
--cc=sam@ravnborg.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).