[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <329aed63-4522-9859-4359-2a450c46dcc0@linaro.org>
Date: Fri, 13 Jan 2023 12:58:08 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Moudy Ho <moudy.ho@...iatek.com>, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>,
Chun-Kuang Hu <chunkuang.hu@...nel.org>
Cc: linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org,
Project_Global_Chrome_Upstream_Group@...iatek.com
Subject: Re: [PATCH v5 01/10] dt-bindings: arm: mediatek: migrate MT8195
vppsys0/1 to mtk-mmsys driver
On 13/01/2023 06:42, Moudy Ho wrote:
> MT8195 vppsys0/1 should be probed from mtk-mmsys driver to
> populate device by platform_device_register_data then start
> its own clock driver.
Unfortunately I don't understand why this justifies removal of compatibles.
How do you propagate or instantiate devices is not really connected with
the hardware description.
Best regards,
Krzysztof
Powered by blists - more mailing lists