[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8eab7134-9d1f-0101-509a-0d664b000a36@gmail.com>
Date: Thu, 26 Jan 2023 15:33:47 +0100
From: Matthias Brugger <matthias.bgg@...il.com>
To: Stephen Boyd <sboyd@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Michael Turquette <mturquette@...libre.com>,
Moudy Ho <moudy.ho@...iatek.com>,
Rob Herring <robh+dt@...nel.org>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-clk@...r.kernel.org,
Project_Global_Chrome_Upstream_Group@...iatek.com
Subject: Re: [PATCH v6 1/4] dt-bindings: arm: mediatek: migrate MT8195
vppsys0/1 to mtk-mmsys driver
On 26/01/2023 15:32, Matthias Brugger wrote:
>
>
> On 26/01/2023 03:05, Stephen Boyd wrote:
>> Quoting Matthias Brugger (2023-01-19 08:08:48)
>>>
>>>
>>> On 18/01/2023 04:15, Moudy Ho wrote:
>>>> MT8195 VPPSYS 0/1 should be probed from mtk-mmsys driver to
>>>> populate device by platform_device_register_data then start
>>>> its own clock driver.
>>>>
>>>> Signed-off-by: Moudy Ho <moudy.ho@...iatek.com>
>>>
>>> Reviewed-by: Matthias Brugger <matthias.bgg@...il.com>
>>>
>>> Stephen, if you want I can take 1/4 and 3/4 through my tree. 3/4 shouldn't be a
>>> problem, not sure about this patch. In any case if you want me to do so, I'd
>>> need a Acked-by from you.
>>
>> Do you need to take them? I'm picking up mediatek patches currently so I
>> can probably just take 1 and 3 if there isn't any build dependency.
>
> No I don't need to, no build depencies. Ok, I'll take 1 and 3 then.
Argh, 2 and 4 of course. 1 and 3 will go through your tree. Sorry for the confusion.
Matthias
Powered by blists - more mailing lists