[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <acec69f943f85b02909d8ce3e4d538c3@kernel.org>
Date: Wed, 30 Aug 2023 12:55:55 +0200
From: Michael Walle <mwalle@...nel.org>
To: NĂcolas F. R. A. Prado
<nfraprado@...labora.com>
Cc: Chun-Kuang Hu <chunkuang.hu@...nel.org>,
Philipp Zabel <p.zabel@...gutronix.de>,
David Airlie <airlied@...il.com>,
Daniel Vetter <daniel@...ll.ch>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>,
"Nancy . Lin" <nancy.lin@...iatek.com>,
Frank Wunderlich <frank-w@...lic-files.de>,
Jitao Shi <jitao.shi@...iatek.com>,
Stu Hsieh <stu.hsieh@...iatek.com>,
dri-devel@...ts.freedesktop.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 2/2] drm/mediatek: dpi/dsi: fix possible_crtcs calculation
> 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
Powered by blists - more mailing lists