[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAFGrd9qVhJb--COXJmGHuW6NxDnXZGdQnxbHGRvaA5Jqhx-yNg@mail.gmail.com>
Date: Wed, 15 Mar 2023 10:26:23 +0100
From: Alexandre Mergnat <amergnat@...libre.com>
To: Chun-Kuang Hu <chunkuang.hu@...nel.org>
Cc: Daniel Vetter <daniel@...ll.ch>, CK Hu <ck.hu@...iatek.com>,
Jitao Shi <jitao.shi@...iatek.com>,
Thierry Reding <thierry.reding@...il.com>,
Philipp Zabel <p.zabel@...gutronix.de>,
Sam Ravnborg <sam@...nborg.org>,
Rob Herring <robh+dt@...nel.org>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
Matthias Brugger <matthias.bgg@...il.com>,
David Airlie <airlied@...il.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Xinlei Lee <xinlei.lee@...iatek.com>,
Guillaume La Roque <glaroque@...libre.com>,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org,
dri-devel@...ts.freedesktop.org,
Fabien Parent <fparent@...libre.com>,
Neil Armstrong <neil.armstrong@...aro.org>,
linux-pwm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 07/21] dt-bindings: display: mediatek: dpi: add binding
for MT8365
Hi Chun-Kuang,
Le lun. 13 mars 2023 à 16:17, Chun-Kuang Hu <chunkuang.hu@...nel.org> a écrit :
>
> Hi, Alexandre:
>
> Alexandre Mergnat <amergnat@...libre.com> 於 2023年3月9日 週四 下午10:23寫道:
> >
> > From: Fabien Parent <fparent@...libre.com>
> >
> > DPI for MT8365 is compatible with MT8192 but requires an additional
> > clock. Modify the documentation to requires this clock only on MT8365 SoCs.
>
> If MT8365 DPI has additional clock, why it is compatible with MT8192 DPI?
> I think some part of MT8165 DPI works under the speed control by the
> DPI clock and this is different with MT8192 DPI, how could these two
> are compatible?
AFAII, The mtk_dpi driver manage the 4th clock as optional
dpi->dpi_clk = devm_clk_get_optional(dev, "dpi");
And all configuration variables for mt8192 are the same for mt8365.
These configuration clock variables (like cal_factor) aren't
correlated with the 4th clock.
The clock number doesn't impact the configuration variable because the
4th clock is simply retrieved from DTS, saved in the driver structure
and prepare/unprepare/enable/disable, like other clocks.
Regards,
Alex
Powered by blists - more mailing lists