[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fa386a3ab2f2ed0c963d5fdec8bbea56ba276169.camel@mediatek.com>
Date: Mon, 16 Jan 2023 02:42:43 +0000
From: Moudy Ho (何宗原) <Moudy.Ho@...iatek.com>
To: "matthias.bgg@...il.com" <matthias.bgg@...il.com>,
"krzysztof.kozlowski@...aro.org" <krzysztof.kozlowski@...aro.org>,
"angelogioacchino.delregno@...labora.com"
<angelogioacchino.delregno@...labora.com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"krzysztof.kozlowski+dt@...aro.org"
<krzysztof.kozlowski+dt@...aro.org>,
"chunkuang.hu@...nel.org" <chunkuang.hu@...nel.org>
CC: "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mediatek@...ts.infradead.org"
<linux-mediatek@...ts.infradead.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Project_Global_Chrome_Upstream_Group
<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 Fri, 2023-01-13 at 12:58 +0100, Krzysztof Kozlowski wrote:
> 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
>
Hi Krzysztof,
Refer to the comments of 0/8 and 1/8 in the following series:
https://patchwork.kernel.org/project/linux-mediatek/list/?series=702518
This patch is used in conjunction with another one(Message ID =
20230113054304.21841-7-moudy.ho@...iatek.com/) to fix the binding
warnings caused by newly added in MMSYS.
Thanks & Regards,
Moudy
Powered by blists - more mailing lists