From: Fei Shao <fshao@chromium.org>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Chun-Kuang Hu <chunkuang.hu@kernel.org>
Cc: Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] drm/mediatek: Support MT8195 OVL compatible in mtk_drm_drv
Date: Mon, 26 Feb 2024 19:31:42 +0800 [thread overview]
Message-ID: <CAC=S1niCFgbNjbnHmUD46N-9gSagYuExeQ+nUHvKOvNbS-jz1A@mail.gmail.com> (raw)
In-Reply-To: <20240226080721.3331649-1-fshao@chromium.org>
On Mon, Feb 26, 2024 at 4:07 PM Fei Shao <fshao@chromium.org> wrote:
>
> Specify the component type for mediatek,mt8195-disp-ovl in the MediaTek
> DRM driver on top of commit 76cdcb87d391 ("drm/mediatek: Add MT8195 ovl
> driver support").
>
> With this, the compatible can function as an independent fallback for
> other display overlays without relying on MT8192.
>
> Signed-off-by: Fei Shao <fshao@chromium.org>
Please disregard this patch.
With the feedback in [1], I can also fix the issue from within the
SoC's device tree.
Even taking a step back, I just learned that this is a duplicate of
[2], so it makes no sense to merge mine in any case.
Sorry for the noise.
[1]: https://lore.kernel.org/all/c4814e25-42c9-4604-b86a-8ef0bd634f78@collabora.com/
[2]: https://lore.kernel.org/all/20240215101119.12629-3-shawn.sung@mediatek.com/
Regards,
Fei
prev parent reply other threads:[~2024-02-26 11:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 8:06 [PATCH] drm/mediatek: Support MT8195 OVL compatible in mtk_drm_drv Fei Shao
2024-02-26 11:31 ` Fei Shao [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='CAC=S1niCFgbNjbnHmUD46N-9gSagYuExeQ+nUHvKOvNbS-jz1A@mail.gmail.com' \
--to=fshao@chromium.org \
--cc=airlied@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.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 NNTP newsgroup(s).