| Message ID | 20230118031509.29834-2-moudy.ho@mediatek.com (mailing list archive) |
|---|---|
| State | Accepted, archived |
| Headers | show |
| Series | Migrate MT8195 VPPSYS 0/1 to mtk-mmsys driver | expand |
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@mediatek.com> > --- > .../arm/mediatek/mediatek,mt8195-clock.yaml | 16 ---------------- > 1 file changed, 16 deletions(-) Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Best regards, Krzysztof
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@mediatek.com> Reviewed-by: Matthias Brugger <matthias.bgg@gmail.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. Regards, Matthias > --- > .../arm/mediatek/mediatek,mt8195-clock.yaml | 16 ---------------- > 1 file changed, 16 deletions(-) > > diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8195-clock.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8195-clock.yaml > index 17fcbb45d121..d62d60181147 100644 > --- a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8195-clock.yaml > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8195-clock.yaml > @@ -28,11 +28,9 @@ properties: > - mediatek,mt8195-imp_iic_wrap_s > - mediatek,mt8195-imp_iic_wrap_w > - mediatek,mt8195-mfgcfg > - - mediatek,mt8195-vppsys0 > - mediatek,mt8195-wpesys > - mediatek,mt8195-wpesys_vpp0 > - mediatek,mt8195-wpesys_vpp1 > - - mediatek,mt8195-vppsys1 > - mediatek,mt8195-imgsys > - mediatek,mt8195-imgsys1_dip_top > - mediatek,mt8195-imgsys1_dip_nr > @@ -92,13 +90,6 @@ examples: > #clock-cells = <1>; > }; > > - - | > - vppsys0: clock-controller@14000000 { > - compatible = "mediatek,mt8195-vppsys0"; > - reg = <0x14000000 0x1000>; > - #clock-cells = <1>; > - }; > - > - | > wpesys: clock-controller@14e00000 { > compatible = "mediatek,mt8195-wpesys"; > @@ -120,13 +111,6 @@ examples: > #clock-cells = <1>; > }; > > - - | > - vppsys1: clock-controller@14f00000 { > - compatible = "mediatek,mt8195-vppsys1"; > - reg = <0x14f00000 0x1000>; > - #clock-cells = <1>; > - }; > - > - | > imgsys: clock-controller@15000000 { > compatible = "mediatek,mt8195-imgsys";
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@mediatek.com> > > Reviewed-by: Matthias Brugger <matthias.bgg@gmail.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.
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@mediatek.com> >> >> Reviewed-by: Matthias Brugger <matthias.bgg@gmail.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.
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@mediatek.com> >>> >>> Reviewed-by: Matthias Brugger <matthias.bgg@gmail.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
Quoting Moudy Ho (2023-01-17 19:15:06) > 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@mediatek.com> > --- Applied to clk-next
diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8195-clock.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8195-clock.yaml index 17fcbb45d121..d62d60181147 100644 --- a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8195-clock.yaml +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8195-clock.yaml @@ -28,11 +28,9 @@ properties: - mediatek,mt8195-imp_iic_wrap_s - mediatek,mt8195-imp_iic_wrap_w - mediatek,mt8195-mfgcfg - - mediatek,mt8195-vppsys0 - mediatek,mt8195-wpesys - mediatek,mt8195-wpesys_vpp0 - mediatek,mt8195-wpesys_vpp1 - - mediatek,mt8195-vppsys1 - mediatek,mt8195-imgsys - mediatek,mt8195-imgsys1_dip_top - mediatek,mt8195-imgsys1_dip_nr @@ -92,13 +90,6 @@ examples: #clock-cells = <1>; }; - - | - vppsys0: clock-controller@14000000 { - compatible = "mediatek,mt8195-vppsys0"; - reg = <0x14000000 0x1000>; - #clock-cells = <1>; - }; - - | wpesys: clock-controller@14e00000 { compatible = "mediatek,mt8195-wpesys"; @@ -120,13 +111,6 @@ examples: #clock-cells = <1>; }; - - | - vppsys1: clock-controller@14f00000 { - compatible = "mediatek,mt8195-vppsys1"; - reg = <0x14f00000 0x1000>; - #clock-cells = <1>; - }; - - | imgsys: clock-controller@15000000 { compatible = "mediatek,mt8195-imgsys";
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@mediatek.com> --- .../arm/mediatek/mediatek,mt8195-clock.yaml | 16 ---------------- 1 file changed, 16 deletions(-)