From: Michael Walle <mwalle@kernel.org>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
Cc: Chun-Kuang Hu <chunkuang.hu@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
"Nancy . Lin" <nancy.lin@mediatek.com>,
Frank Wunderlich <frank-w@public-files.de>,
Jitao Shi <jitao.shi@mediatek.com>,
Stu Hsieh <stu.hsieh@mediatek.com>,
dri-devel@lists.freedesktop.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] drm/mediatek: dpi/dsi: fix possible_crtcs calculation
Date: Wed, 30 Aug 2023 12:55:55 +0200 [thread overview]
Message-ID: <acec69f943f85b02909d8ce3e4d538c3@kernel.org> (raw)
In-Reply-To: <fca464b9-9f32-4420-90fd-05e851871c25@notapiano>
> This won't work. On MT8195 there are two display IPs, vdosys0 and
> vdosys1,
> vdosys0 only has the main path while vdosys1 only has the external
> path. So you
> need to loop over each one in all_drm_private[j] to get the right crtc
> ID for
> MT8195.
Ahh thanks, got it.
-michael
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-30 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 13:19 [PATCH 1/2] drm/mediathek: fix kernel oops if no crtc is found Michael Walle
2023-08-29 13:19 ` [PATCH 2/2] drm/mediatek: dpi/dsi: fix possible_crtcs calculation Michael Walle
2023-08-29 17:50 ` Nícolas F. R. A. Prado
2023-08-30 10:55 ` Michael Walle [this message]
2023-08-29 16:00 ` [PATCH 1/2] drm/mediathek: fix kernel oops if no crtc is found Nícolas F. R. A. Prado
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=acec69f943f85b02909d8ce3e4d538c3@kernel.org \
--to=mwalle@kernel.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=frank-w@public-files.de \
--cc=jitao.shi@mediatek.com \
--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=nancy.lin@mediatek.com \
--cc=nfraprado@collabora.com \
--cc=p.zabel@pengutronix.de \
--cc=stu.hsieh@mediatek.com \
/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).