From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
Alper Nebi Yasak <alpernebiyasak@gmail.com>
Cc: Pi-Hsun Shih <pihsun@chromium.org>,
linux-arm-kernel@lists.infradead.org,
Chen-Yu Tsai <wenst@chromium.org>,
Fabien Parent <fparent@baylibre.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Jitao Shi <jitao.shi@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Pin-yen Lin <treapking@chromium.org>,
linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH] arm64: dts: mediatek: mt8183-kukui: Disable DPI display interface
Date: Wed, 02 Oct 2024 11:33:29 +0200 [thread overview]
Message-ID: <172786160926.39477.6425761248165017242.b4-ty@collabora.com> (raw)
In-Reply-To: <20240916162956.267340-1-alpernebiyasak@gmail.com>
On Mon, 16 Sep 2024 19:29:32 +0300, Alper Nebi Yasak wrote:
> Commit 009d855a26fd ("arm64: dts: mt8183: add dpi node to mt8183") adds
> a device-tree node for the DPI display interface that feeds the external
> display pipeline, to enable HDMI support on the Pumpkin board.
>
> However, the external display is not fully described on Chrome devices,
> blocked by further work on DP / USB-C muxing graph bindings. This
> incomplete description currently breaks internal display at least on the
> Cozmo board. The same issue was found and fixed on MT8186 devices with
> commit 3079fb09ddac ("arm64: dts: mediatek: mt8186-corsola: Disable DPI
> display interface"), but the MT8183 change wasn't merged until then.
>
> [...]
Applied to v6.12-next/dts64, thanks!
[1/1] arm64: dts: mediatek: mt8183-kukui: Disable DPI display interface
https://git.kernel.org/mediatek/c/377548f0
Cheers,
Angelo
prev parent reply other threads:[~2024-10-02 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 16:29 Alper Nebi Yasak
2024-09-18 6:59 ` Pin-yen Lin
2024-09-19 13:14 ` AngeloGioacchino Del Regno
2024-10-02 9:33 ` AngeloGioacchino Del Regno [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=172786160926.39477.6425761248165017242.b4-ty@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=alpernebiyasak@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fparent@baylibre.com \
--cc=jitao.shi@mediatek.com \
--cc=krzk+dt@kernel.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=pihsun@chromium.org \
--cc=robh@kernel.org \
--cc=treapking@chromium.org \
--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
all inboxes | Powered by JetHome®