From: Doug Anderson <dianders@chromium.org>
To: Chen-Yu Tsai <wenst@chromium.org>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Jessica Zhang <jesszhan0024@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/panel-edp: Add AUO B133HAN06.6 and BOE NV133FHM-N4F V8.0
Date: Mon, 11 May 2026 07:16:09 -0700 [thread overview]
Message-ID: <CAD=FV=VGvJL_scfs18JgQs=fAX3yCnRMqCE71n3Kqa3QP8SywQ@mail.gmail.com> (raw)
In-Reply-To: <20260511095914.1200201-1-wenst@chromium.org>
Hi,
On Mon, May 11, 2026 at 2:59 AM Chen-Yu Tsai <wenst@chromium.org> wrote:
>
> These two panels are found in MT8195 Dojo, a.k.a. the HP Chromebook
> x360 13b-ca0xxx laptop.
>
> Only the BOE entry was tested on an actual device. The AUO entry is
> solely based on the provided datasheet.
>
> Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
> ---
> drivers/gpu/drm/panel/panel-edp.c | 2 ++
> 1 file changed, 2 insertions(+)
In recent patches, we've been including the EDID in the commit
message. That helps later if someone finds that they need different
settings for the same ID. We can figure out if two panels somehow
reused the same ID or if the original timings just need updating.
-Doug
next prev parent reply other threads:[~2026-05-11 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 9:59 [PATCH] drm/panel-edp: Add AUO B133HAN06.6 and BOE NV133FHM-N4F V8.0 Chen-Yu Tsai
2026-05-11 14:16 ` Doug Anderson [this message]
2026-05-16 5:39 ` Claude review: " Claude Code Review Bot
2026-05-16 5:39 ` Claude Code Review Bot
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=VGvJL_scfs18JgQs=fAX3yCnRMqCE71n3Kqa3QP8SywQ@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesszhan0024@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=wenst@chromium.org \
/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