From: mtk18742 <[email protected]>
Changes since v3:
- Rebase on linux-next
Changes since v2:
- Depend on :
[1] https://patchwork.kernel.org/project/linux-mediatek/list/?series=681097
- Split dts settings into two patches based on belonging to MMSYS or MUTEX.
Changes since v1:
- Depend on :
[1] https://patchwork.kernel.org/project/linux-mediatek/list/?series=681097
- Add compatible names to VPPSYS0 and VPPSYS1 in MMSYS binding file.
- Fix VPPSYS's MMSYS and MUTEX dts to pass the dtsb_check.
- Rename mtk_mmsys_merge_config() and mtk_mmsys_rsz_dcm_config() to
mtk_mmsys_vpp_rsz_merge_config() and mtk_mmsys_vpp_rsz_dcm_config().
- Clean up mtk_mmsys_vpp_rsz_dcm_config().
- Add a comment to mtk_mutex_write_mod() and clean it up for use in more
than 32 mods.
Hi,
This series add support for MT8195's two VPPSYS(Video Processor Pipe Subsystem),
under which there will be corresponding MMSYS and MUTEX settings that
need to be configured.
Moudy Ho (2):
dt-bindings: arm: mediatek: mmsys: Add support for MT8195 VPPSYS
arm64: dts: mediatek: mt8195: add MUTEX configuration for VPPSYS
Roy-CW.Yeh (6):
dt-bindings: soc: mediatek: Add support for MT8195 VPPSYS
arm64: dts: mediatek: mt8195: add MMSYS configuration for VPPSYS
soc: mediatek: mmsys: add support for MT8195 VPPSYS
soc: mediatek: mmsys: add config api for RSZ switching and DCM
soc: mediatek: mutex: Add mtk_mutex_set_mod support to set MOD1
soc: mediatek: mutex: support MT8195 VPPSYS
.../bindings/arm/mediatek/mediatek,mmsys.yaml | 5 +-
.../bindings/soc/mediatek/mediatek,mutex.yaml | 1 +
arch/arm64/boot/dts/mediatek/mt8195.dtsi | 28 +++-
drivers/soc/mediatek/mt8195-mmsys.h | 13 ++
drivers/soc/mediatek/mtk-mmsys.c | 64 +++++++++
drivers/soc/mediatek/mtk-mmsys.h | 1 +
drivers/soc/mediatek/mtk-mutex.c | 135 +++++++++++++++++-
include/linux/soc/mediatek/mtk-mmsys.h | 4 +
include/linux/soc/mediatek/mtk-mutex.h | 35 +++++
9 files changed, 274 insertions(+), 12 deletions(-)
--
2.18.0
In MT8195, the MMSYS has two Video Processor Pipepline Subsystems
named VPPSYS0 and VPPSYS1, each with specific MUTEX to control
Start of Frame(SOF) and End of Frame (EOF) signals.
Before working with them, the addresses, interrupts, clocks and power
domains need to be set up in dts.
Signed-off-by: Moudy Ho <[email protected]>
Reviewed-by: AngeloGioacchino Del Regno <[email protected]>
---
arch/arm64/boot/dts/mediatek/mt8195.dtsi | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8195.dtsi b/arch/arm64/boot/dts/mediatek/mt8195.dtsi
index bd33b414c484..0ece3b46b66a 100644
--- a/arch/arm64/boot/dts/mediatek/mt8195.dtsi
+++ b/arch/arm64/boot/dts/mediatek/mt8195.dtsi
@@ -1639,6 +1639,15 @@
#clock-cells = <1>;
};
+ mutex@1400f000 {
+ compatible = "mediatek,mt8195-vpp-mutex";
+ reg = <0 0x1400f000 0 0x1000>;
+ interrupts = <GIC_SPI 592 IRQ_TYPE_LEVEL_HIGH 0>;
+ mediatek,gce-client-reg = <&gce1 SUBSYS_1400XXXX 0xf000 0x1000>;
+ clocks = <&vppsys0 CLK_VPP0_MUTEX>;
+ power-domains = <&spm MT8195_POWER_DOMAIN_VPPSYS0>;
+ };
+
smi_sub_common_vpp0_vpp1_2x1: smi@14010000 {
compatible = "mediatek,mt8195-smi-sub-common";
reg = <0 0x14010000 0 0x1000>;
@@ -1745,6 +1754,15 @@
#clock-cells = <1>;
};
+ mutex@14f01000 {
+ compatible = "mediatek,mt8195-vpp-mutex";
+ reg = <0 0x14f01000 0 0x1000>;
+ interrupts = <GIC_SPI 635 IRQ_TYPE_LEVEL_HIGH 0>;
+ mediatek,gce-client-reg = <&gce1 SUBSYS_14f0XXXX 0x1000 0x1000>;
+ clocks = <&vppsys1 CLK_VPP1_DISP_MUTEX>;
+ power-domains = <&spm MT8195_POWER_DOMAIN_VPPSYS1>;
+ };
+
larb5: larb@14f02000 {
compatible = "mediatek,mt8195-smi-larb";
reg = <0 0x14f02000 0 0x1000>;
--
2.18.0
For MT8195, VPPSYS0 and VPPSYS1 are 2 display pipes with
hardware differences in power domains, clocks and subsystem counts,
which should be determined by compatible names.
Signed-off-by: Moudy Ho <[email protected]>
Acked-by: Krzysztof Kozlowski <[email protected]>
---
.../devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
index 0711f1834fbd..493aa9e8d484 100644
--- a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
+++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
@@ -48,7 +48,10 @@ properties:
- const: syscon
- items:
- - const: mediatek,mt8195-vdosys0
+ - enum:
+ - mediatek,mt8195-vdosys0
+ - mediatek,mt8195-vppsys0
+ - mediatek,mt8195-vppsys1
- const: mediatek,mt8195-mmsys
- const: syscon
--
2.18.0
Il 07/12/22 10:49, Moudy Ho ha scritto:
> For MT8195, VPPSYS0 and VPPSYS1 are 2 display pipes with
> hardware differences in power domains, clocks and subsystem counts,
> which should be determined by compatible names.
>
> Signed-off-by: Moudy Ho <[email protected]>
> Acked-by: Krzysztof Kozlowski <[email protected]>
Reviewed-by: AngeloGioacchino Del Regno <[email protected]>
Whole series applied, thanks!
On 07/12/2022 10:49, Moudy Ho wrote:
> From: mtk18742 <[email protected]>
>
> Changes since v3:
> - Rebase on linux-next
>
> Changes since v2:
> - Depend on :
> [1] https://patchwork.kernel.org/project/linux-mediatek/list/?series=681097
> - Split dts settings into two patches based on belonging to MMSYS or MUTEX.
>
> Changes since v1:
> - Depend on :
> [1] https://patchwork.kernel.org/project/linux-mediatek/list/?series=681097
> - Add compatible names to VPPSYS0 and VPPSYS1 in MMSYS binding file.
> - Fix VPPSYS's MMSYS and MUTEX dts to pass the dtsb_check.
> - Rename mtk_mmsys_merge_config() and mtk_mmsys_rsz_dcm_config() to
> mtk_mmsys_vpp_rsz_merge_config() and mtk_mmsys_vpp_rsz_dcm_config().
> - Clean up mtk_mmsys_vpp_rsz_dcm_config().
> - Add a comment to mtk_mutex_write_mod() and clean it up for use in more
> than 32 mods.
>
> Hi,
>
> This series add support for MT8195's two VPPSYS(Video Processor Pipe Subsystem),
> under which there will be corresponding MMSYS and MUTEX settings that
> need to be configured.
>
> Moudy Ho (2):
> dt-bindings: arm: mediatek: mmsys: Add support for MT8195 VPPSYS
> arm64: dts: mediatek: mt8195: add MUTEX configuration for VPPSYS
>
> Roy-CW.Yeh (6):
> dt-bindings: soc: mediatek: Add support for MT8195 VPPSYS
> arm64: dts: mediatek: mt8195: add MMSYS configuration for VPPSYS
> soc: mediatek: mmsys: add support for MT8195 VPPSYS
> soc: mediatek: mmsys: add config api for RSZ switching and DCM
> soc: mediatek: mutex: Add mtk_mutex_set_mod support to set MOD1
> soc: mediatek: mutex: support MT8195 VPPSYS
>
> .../bindings/arm/mediatek/mediatek,mmsys.yaml | 5 +-
> .../bindings/soc/mediatek/mediatek,mutex.yaml | 1 +
> arch/arm64/boot/dts/mediatek/mt8195.dtsi | 28 +++-
> drivers/soc/mediatek/mt8195-mmsys.h | 13 ++
> drivers/soc/mediatek/mtk-mmsys.c | 64 +++++++++
> drivers/soc/mediatek/mtk-mmsys.h | 1 +
> drivers/soc/mediatek/mtk-mutex.c | 135 +++++++++++++++++-
> include/linux/soc/mediatek/mtk-mmsys.h | 4 +
> include/linux/soc/mediatek/mtk-mutex.h | 35 +++++
> 9 files changed, 274 insertions(+), 12 deletions(-)
>
On Wed, Dec 7, 2022 at 3:49 AM Moudy Ho <[email protected]> wrote:
>
> For MT8195, VPPSYS0 and VPPSYS1 are 2 display pipes with
> hardware differences in power domains, clocks and subsystem counts,
> which should be determined by compatible names.
>
> Signed-off-by: Moudy Ho <[email protected]>
> Acked-by: Krzysztof Kozlowski <[email protected]>
> ---
> .../devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
This landed in today's linux-next causing the following binding
warnings. Is this a fix? Only fixes for 6.2 should be added during the
merge window.
/builds/robherring/linux-dt/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8195-clock.example.dtb:
clock-controller@14000000: $nodename:0: 'clock-controller@14000000'
does not match '^syscon@[0-9a-f]+$'
From schema:
/builds/robherring/linux-dt/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
/builds/robherring/linux-dt/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8195-clock.example.dtb:
clock-controller@14000000: compatible: 'oneOf' conditional failed, one
must be fixed:
['mediatek,mt8195-vppsys0'] is too short
'mediatek,mt8195-vppsys0' is not one of
['mediatek,mt2701-mmsys', 'mediatek,mt2712-mmsys',
'mediatek,mt6765-mmsys', 'mediatek,mt6779-mmsys',
'mediatek,mt6795-mmsys', 'mediatek,mt6797-mmsys',
'mediatek,mt8167-mmsys', 'mediatek,mt8173-mmsys',
'mediatek,mt8183-mmsys', 'mediatek,mt8186-mmsys',
'mediatek,mt8188-vdosys0', 'mediatek,mt8192-mmsys',
'mediatek,mt8365-mmsys']
'mediatek,mt8195-mmsys' was expected
'mediatek,mt7623-mmsys' was expected
From schema:
/builds/robherring/linux-dt/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
On 19/12/2022 14:44, Rob Herring wrote:
> On Wed, Dec 7, 2022 at 3:49 AM Moudy Ho <[email protected]> wrote:
>>
>> For MT8195, VPPSYS0 and VPPSYS1 are 2 display pipes with
>> hardware differences in power domains, clocks and subsystem counts,
>> which should be determined by compatible names.
>>
>> Signed-off-by: Moudy Ho <[email protected]>
>> Acked-by: Krzysztof Kozlowski <[email protected]>
>> ---
>> .../devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> This landed in today's linux-next causing the following binding
> warnings. Is this a fix? Only fixes for 6.2 should be added during the
> merge window.
>
No it's not a fix, it's queued for the next -rc phase. I didn't know of the
limitation of linux-next only allowing fixes in the merge window.
Actually the patch is wrong. It shouldn't include "mediatek,mt8195-mmsys" as
fallback for mediatek,mt8195-vppsys[0,1].
I'll revert the whole series from v6.2-tmp/dts64 and v6.2-tmp/soc
Regards,
Matthias
> /builds/robherring/linux-dt/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8195-clock.example.dtb:
> clock-controller@14000000: $nodename:0: 'clock-controller@14000000'
> does not match '^syscon@[0-9a-f]+$'
> From schema:
> /builds/robherring/linux-dt/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
> /builds/robherring/linux-dt/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8195-clock.example.dtb:
> clock-controller@14000000: compatible: 'oneOf' conditional failed, one
> must be fixed:
> ['mediatek,mt8195-vppsys0'] is too short
> 'mediatek,mt8195-vppsys0' is not one of
> ['mediatek,mt2701-mmsys', 'mediatek,mt2712-mmsys',
> 'mediatek,mt6765-mmsys', 'mediatek,mt6779-mmsys',
> 'mediatek,mt6795-mmsys', 'mediatek,mt6797-mmsys',
> 'mediatek,mt8167-mmsys', 'mediatek,mt8173-mmsys',
> 'mediatek,mt8183-mmsys', 'mediatek,mt8186-mmsys',
> 'mediatek,mt8188-vdosys0', 'mediatek,mt8192-mmsys',
> 'mediatek,mt8365-mmsys']
> 'mediatek,mt8195-mmsys' was expected
> 'mediatek,mt7623-mmsys' was expected
> From schema:
> /builds/robherring/linux-dt/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
On 16/12/2022 13:33, Matthias Brugger wrote:
>
> Whole series applied, thanks!
>
And now, whole series reverted, please see comment in 1/8.
Regards,
Matthias
> On 07/12/2022 10:49, Moudy Ho wrote:
>> From: mtk18742 <[email protected]>
>>
>> Changes since v3:
>> - Rebase on linux-next
>>
>> Changes since v2:
>> - Depend on :
>> [1] https://patchwork.kernel.org/project/linux-mediatek/list/?series=681097
>> - Split dts settings into two patches based on belonging to MMSYS or MUTEX.
>>
>> Changes since v1:
>> - Depend on :
>> [1] https://patchwork.kernel.org/project/linux-mediatek/list/?series=681097
>> - Add compatible names to VPPSYS0 and VPPSYS1 in MMSYS binding file.
>> - Fix VPPSYS's MMSYS and MUTEX dts to pass the dtsb_check.
>> - Rename mtk_mmsys_merge_config() and mtk_mmsys_rsz_dcm_config() to
>> mtk_mmsys_vpp_rsz_merge_config() and mtk_mmsys_vpp_rsz_dcm_config().
>> - Clean up mtk_mmsys_vpp_rsz_dcm_config().
>> - Add a comment to mtk_mutex_write_mod() and clean it up for use in more
>> than 32 mods.
>>
>> Hi,
>>
>> This series add support for MT8195's two VPPSYS(Video Processor Pipe Subsystem),
>> under which there will be corresponding MMSYS and MUTEX settings that
>> need to be configured.
>>
>> Moudy Ho (2):
>> dt-bindings: arm: mediatek: mmsys: Add support for MT8195 VPPSYS
>> arm64: dts: mediatek: mt8195: add MUTEX configuration for VPPSYS
>>
>> Roy-CW.Yeh (6):
>> dt-bindings: soc: mediatek: Add support for MT8195 VPPSYS
>> arm64: dts: mediatek: mt8195: add MMSYS configuration for VPPSYS
>> soc: mediatek: mmsys: add support for MT8195 VPPSYS
>> soc: mediatek: mmsys: add config api for RSZ switching and DCM
>> soc: mediatek: mutex: Add mtk_mutex_set_mod support to set MOD1
>> soc: mediatek: mutex: support MT8195 VPPSYS
>>
>> .../bindings/arm/mediatek/mediatek,mmsys.yaml | 5 +-
>> .../bindings/soc/mediatek/mediatek,mutex.yaml | 1 +
>> arch/arm64/boot/dts/mediatek/mt8195.dtsi | 28 +++-
>> drivers/soc/mediatek/mt8195-mmsys.h | 13 ++
>> drivers/soc/mediatek/mtk-mmsys.c | 64 +++++++++
>> drivers/soc/mediatek/mtk-mmsys.h | 1 +
>> drivers/soc/mediatek/mtk-mutex.c | 135 +++++++++++++++++-
>> include/linux/soc/mediatek/mtk-mmsys.h | 4 +
>> include/linux/soc/mediatek/mtk-mutex.h | 35 +++++
>> 9 files changed, 274 insertions(+), 12 deletions(-)
>>
On 19/12/2022 16:17, Matthias Brugger wrote:
>
>
> On 19/12/2022 14:44, Rob Herring wrote:
>> On Wed, Dec 7, 2022 at 3:49 AM Moudy Ho <[email protected]> wrote:
>>>
>>> For MT8195, VPPSYS0 and VPPSYS1 are 2 display pipes with
>>> hardware differences in power domains, clocks and subsystem counts,
>>> which should be determined by compatible names.
>>>
>>> Signed-off-by: Moudy Ho <[email protected]>
>>> Acked-by: Krzysztof Kozlowski <[email protected]>
>>> ---
>>> .../devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml | 5 ++++-
>>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> This landed in today's linux-next causing the following binding
>> warnings. Is this a fix? Only fixes for 6.2 should be added during the
>> merge window.
>>
>
> No it's not a fix, it's queued for the next -rc phase. I didn't know of the
> limitation of linux-next only allowing fixes in the merge window.
Stephen asks for it every time. Now it is in separate email:
https://lore.kernel.org/linux-next/[email protected]/
Previously it was in each linux-next announcement:
https://lore.kernel.org/linux-next/[email protected]/
>
> Actually the patch is wrong. It shouldn't include "mediatek,mt8195-mmsys" as
> fallback for mediatek,mt8195-vppsys[0,1].
>
> I'll revert the whole series from v6.2-tmp/dts64 and v6.2-tmp/soc
Thanks. Please, drop all material for next cycle from linux-next.
Best regards,
Krzysztof
On Mon, 2022-12-19 at 16:17 +0100, Matthias Brugger wrote:
>
> On 16/12/2022 13:33, Matthias Brugger wrote:
> >
> > Whole series applied, thanks!
> >
>
> And now, whole series reverted, please see comment in 1/8.
>
> Regards,
> Matthias
>
Hi Matthias,
May I send a new series without a fallback compatible like the mt8188
VDOSYS does?
https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/
Regards,
Moudy
> > On 07/12/2022 10:49, Moudy Ho wrote:
> > > From: mtk18742 <[email protected]>
> > >
> > > Changes since v3:
> > > - Rebase on linux-next
> > >
> > > Changes since v2:
> > > - Depend on :
> > > [1]
> > > https://urldefense.com/v3/__https://patchwork.kernel.org/project/linux-mediatek/list/?series=681097__;!!CTRNKA9wMg0ARbw!giZVy8TiFNylgWKOjI75fSmleN6UlckPuiXzFf5jbdVgFbHdIxG3d3Jvkqp7Eka73I2TmataD_d5QjzBnk6-sYY$
> > >
> > > - Split dts settings into two patches based on belonging to MMSYS
> > > or MUTEX.
> > >
> > > Changes since v1:
> > > - Depend on :
> > > [1]
> > > https://urldefense.com/v3/__https://patchwork.kernel.org/project/linux-mediatek/list/?series=681097__;!!CTRNKA9wMg0ARbw!giZVy8TiFNylgWKOjI75fSmleN6UlckPuiXzFf5jbdVgFbHdIxG3d3Jvkqp7Eka73I2TmataD_d5QjzBnk6-sYY$
> > >
> > > - Add compatible names to VPPSYS0 and VPPSYS1 in MMSYS binding
> > > file.
> > > - Fix VPPSYS's MMSYS and MUTEX dts to pass the dtsb_check.
> > > - Rename mtk_mmsys_merge_config() and mtk_mmsys_rsz_dcm_config()
> > > to
> > > mtk_mmsys_vpp_rsz_merge_config() and
> > > mtk_mmsys_vpp_rsz_dcm_config().
> > > - Clean up mtk_mmsys_vpp_rsz_dcm_config().
> > > - Add a comment to mtk_mutex_write_mod() and clean it up for use
> > > in more
> > > than 32 mods.
> > >
> > > Hi,
> > >
> > > This series add support for MT8195's two VPPSYS(Video Processor
> > > Pipe Subsystem),
> > > under which there will be corresponding MMSYS and MUTEX settings
> > > that
> > > need to be configured.
> > >
> > > Moudy Ho (2):
> > > dt-bindings: arm: mediatek: mmsys: Add support for MT8195
> > > VPPSYS
> > > arm64: dts: mediatek: mt8195: add MUTEX configuration for
> > > VPPSYS
> > >
> > > Roy-CW.Yeh (6):
> > > dt-bindings: soc: mediatek: Add support for MT8195 VPPSYS
> > > arm64: dts: mediatek: mt8195: add MMSYS configuration for
> > > VPPSYS
> > > soc: mediatek: mmsys: add support for MT8195 VPPSYS
> > > soc: mediatek: mmsys: add config api for RSZ switching and DCM
> > > soc: mediatek: mutex: Add mtk_mutex_set_mod support to set
> > > MOD1
> > > soc: mediatek: mutex: support MT8195 VPPSYS
> > >
> > > .../bindings/arm/mediatek/mediatek,mmsys.yaml | 5 +-
> > > .../bindings/soc/mediatek/mediatek,mutex.yaml | 1 +
> > > arch/arm64/boot/dts/mediatek/mt8195.dtsi | 28 +++-
> > > drivers/soc/mediatek/mt8195-mmsys.h | 13 ++
> > > drivers/soc/mediatek/mtk-mmsys.c | 64 +++++++++
> > > drivers/soc/mediatek/mtk-mmsys.h | 1 +
> > > drivers/soc/mediatek/mtk-mutex.c | 135
> > > +++++++++++++++++-
> > > include/linux/soc/mediatek/mtk-mmsys.h | 4 +
> > > include/linux/soc/mediatek/mtk-mutex.h | 35 +++++
> > > 9 files changed, 274 insertions(+), 12 deletions(-)
> > >
On Tue, 2022-12-20 at 10:14 +0800, moudy ho wrote:
> On Mon, 2022-12-19 at 16:17 +0100, Matthias Brugger wrote:
> >
> > On 16/12/2022 13:33, Matthias Brugger wrote:
> > >
> > > Whole series applied, thanks!
> > >
> >
> > And now, whole series reverted, please see comment in 1/8.
> >
> > Regards,
> > Matthias
> >
>
> Hi Matthias,
>
> May I send a new series without a fallback compatible like the mt8188
> VDOSYS does?
>
>
https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/
>
> Regards,
> Moudy
Hi Matthias,
Sorry for the inaccurate information, the warning mentioned in [1/8] is
because vppsys 0/1 has already been defined in "mediatek,mt8195-
clock.yaml" as follows:
https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/
Is it possible to fix it by just removing [1/8], or should I send a new
series?
Regards,
Moudy
> > > On 07/12/2022 10:49, Moudy Ho wrote:
> > > > From: mtk18742 <[email protected]>
> > > >
> > > > Changes since v3:
> > > > - Rebase on linux-next
> > > >
> > > > Changes since v2:
> > > > - Depend on :
> > > > [1]
> > > >
https://urldefense.com/v3/__https://patchwork.kernel.org/project/linux-mediatek/list/?series=681097__;!!CTRNKA9wMg0ARbw!giZVy8TiFNylgWKOjI75fSmleN6UlckPuiXzFf5jbdVgFbHdIxG3d3Jvkqp7Eka73I2TmataD_d5QjzBnk6-sYY$
> > > >
> > > >
> > > > - Split dts settings into two patches based on belonging to
> > > > MMSYS
> > > > or MUTEX.
> > > >
> > > > Changes since v1:
> > > > - Depend on :
> > > > [1]
> > > >
https://urldefense.com/v3/__https://patchwork.kernel.org/project/linux-mediatek/list/?series=681097__;!!CTRNKA9wMg0ARbw!giZVy8TiFNylgWKOjI75fSmleN6UlckPuiXzFf5jbdVgFbHdIxG3d3Jvkqp7Eka73I2TmataD_d5QjzBnk6-sYY$
> > > >
> > > >
> > > > - Add compatible names to VPPSYS0 and VPPSYS1 in MMSYS binding
> > > > file.
> > > > - Fix VPPSYS's MMSYS and MUTEX dts to pass the dtsb_check.
> > > > - Rename mtk_mmsys_merge_config() and
> > > > mtk_mmsys_rsz_dcm_config()
> > > > to
> > > > mtk_mmsys_vpp_rsz_merge_config() and
> > > > mtk_mmsys_vpp_rsz_dcm_config().
> > > > - Clean up mtk_mmsys_vpp_rsz_dcm_config().
> > > > - Add a comment to mtk_mutex_write_mod() and clean it up for
> > > > use
> > > > in more
> > > > than 32 mods.
> > > >
> > > > Hi,
> > > >
> > > > This series add support for MT8195's two VPPSYS(Video Processor
> > > > Pipe Subsystem),
> > > > under which there will be corresponding MMSYS and MUTEX
> > > > settings
> > > > that
> > > > need to be configured.
> > > >
> > > > Moudy Ho (2):
> > > > dt-bindings: arm: mediatek: mmsys: Add support for MT8195
> > > > VPPSYS
> > > > arm64: dts: mediatek: mt8195: add MUTEX configuration for
> > > > VPPSYS
> > > >
> > > > Roy-CW.Yeh (6):
> > > > dt-bindings: soc: mediatek: Add support for MT8195 VPPSYS
> > > > arm64: dts: mediatek: mt8195: add MMSYS configuration for
> > > > VPPSYS
> > > > soc: mediatek: mmsys: add support for MT8195 VPPSYS
> > > > soc: mediatek: mmsys: add config api for RSZ switching and
> > > > DCM
> > > > soc: mediatek: mutex: Add mtk_mutex_set_mod support to set
> > > > MOD1
> > > > soc: mediatek: mutex: support MT8195 VPPSYS
> > > >
> > > > .../bindings/arm/mediatek/mediatek,mmsys.yaml | 5 +-
> > > > .../bindings/soc/mediatek/mediatek,mutex.yaml | 1 +
> > > > arch/arm64/boot/dts/mediatek/mt8195.dtsi | 28 +++-
> > > > drivers/soc/mediatek/mt8195-mmsys.h | 13 ++
> > > > drivers/soc/mediatek/mtk-mmsys.c | 64 +++++++++
> > > > drivers/soc/mediatek/mtk-mmsys.h | 1 +
> > > > drivers/soc/mediatek/mtk-mutex.c | 135
> > > > +++++++++++++++++-
> > > > include/linux/soc/mediatek/mtk-mmsys.h | 4 +
> > > > include/linux/soc/mediatek/mtk-mutex.h | 35 +++++
> > > > 9 files changed, 274 insertions(+), 12 deletions(-)
> > > >
Hi Moudy,
On 20/12/2022 04:40, Moudy Ho (何宗原) wrote:
> On Tue, 2022-12-20 at 10:14 +0800, moudy ho wrote:
>> On Mon, 2022-12-19 at 16:17 +0100, Matthias Brugger wrote:
>>>
>>> On 16/12/2022 13:33, Matthias Brugger wrote:
>>>>
>>>> Whole series applied, thanks!
>>>>
>>>
>>> And now, whole series reverted, please see comment in 1/8.
>>>
>>> Regards,
>>> Matthias
>>>
>>
>> Hi Matthias,
>>
>> May I send a new series without a fallback compatible like the mt8188
>> VDOSYS does?
>>
>>
> https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/
>>
>> Regards,
>> Moudy
>
> Hi Matthias,
>
> Sorry for the inaccurate information, the warning mentioned in [1/8] is
> because vppsys 0/1 has already been defined in "mediatek,mt8195-
> clock.yaml" as follows:
>
> https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/
>
> Is it possible to fix it by just removing [1/8], or should I send a new
> series?
>
You will need to remove it from the clock binding and of course from the clock
drivers. One example is this one:
https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/
In the end the mmsys will probe by the compatible and will then probe the clock
driver as a platform driver.
Best regards,
Matthias
> Regards,
> Moudy
>
>>>> On 07/12/2022 10:49, Moudy Ho wrote:
>>>>> From: mtk18742 <[email protected]>
>>>>>
>>>>> Changes since v3:
>>>>> - Rebase on linux-next
>>>>>
>>>>> Changes since v2:
>>>>> - Depend on :
>>>>> [1]
>>>>>
> https://urldefense.com/v3/__https://patchwork.kernel.org/project/linux-mediatek/list/?series=681097__;!!CTRNKA9wMg0ARbw!giZVy8TiFNylgWKOjI75fSmleN6UlckPuiXzFf5jbdVgFbHdIxG3d3Jvkqp7Eka73I2TmataD_d5QjzBnk6-sYY$
>>>>>
>>>>>
>>>>> - Split dts settings into two patches based on belonging to
>>>>> MMSYS
>>>>> or MUTEX.
>>>>>
>>>>> Changes since v1:
>>>>> - Depend on :
>>>>> [1]
>>>>>
> https://urldefense.com/v3/__https://patchwork.kernel.org/project/linux-mediatek/list/?series=681097__;!!CTRNKA9wMg0ARbw!giZVy8TiFNylgWKOjI75fSmleN6UlckPuiXzFf5jbdVgFbHdIxG3d3Jvkqp7Eka73I2TmataD_d5QjzBnk6-sYY$
>>>>>
>>>>>
>>>>> - Add compatible names to VPPSYS0 and VPPSYS1 in MMSYS binding
>>>>> file.
>>>>> - Fix VPPSYS's MMSYS and MUTEX dts to pass the dtsb_check.
>>>>> - Rename mtk_mmsys_merge_config() and
>>>>> mtk_mmsys_rsz_dcm_config()
>>>>> to
>>>>> mtk_mmsys_vpp_rsz_merge_config() and
>>>>> mtk_mmsys_vpp_rsz_dcm_config().
>>>>> - Clean up mtk_mmsys_vpp_rsz_dcm_config().
>>>>> - Add a comment to mtk_mutex_write_mod() and clean it up for
>>>>> use
>>>>> in more
>>>>> than 32 mods.
>>>>>
>>>>> Hi,
>>>>>
>>>>> This series add support for MT8195's two VPPSYS(Video Processor
>>>>> Pipe Subsystem),
>>>>> under which there will be corresponding MMSYS and MUTEX
>>>>> settings
>>>>> that
>>>>> need to be configured.
>>>>>
>>>>> Moudy Ho (2):
>>>>> dt-bindings: arm: mediatek: mmsys: Add support for MT8195
>>>>> VPPSYS
>>>>> arm64: dts: mediatek: mt8195: add MUTEX configuration for
>>>>> VPPSYS
>>>>>
>>>>> Roy-CW.Yeh (6):
>>>>> dt-bindings: soc: mediatek: Add support for MT8195 VPPSYS
>>>>> arm64: dts: mediatek: mt8195: add MMSYS configuration for
>>>>> VPPSYS
>>>>> soc: mediatek: mmsys: add support for MT8195 VPPSYS
>>>>> soc: mediatek: mmsys: add config api for RSZ switching and
>>>>> DCM
>>>>> soc: mediatek: mutex: Add mtk_mutex_set_mod support to set
>>>>> MOD1
>>>>> soc: mediatek: mutex: support MT8195 VPPSYS
>>>>>
>>>>> .../bindings/arm/mediatek/mediatek,mmsys.yaml | 5 +-
>>>>> .../bindings/soc/mediatek/mediatek,mutex.yaml | 1 +
>>>>> arch/arm64/boot/dts/mediatek/mt8195.dtsi | 28 +++-
>>>>> drivers/soc/mediatek/mt8195-mmsys.h | 13 ++
>>>>> drivers/soc/mediatek/mtk-mmsys.c | 64 +++++++++
>>>>> drivers/soc/mediatek/mtk-mmsys.h | 1 +
>>>>> drivers/soc/mediatek/mtk-mutex.c | 135
>>>>> +++++++++++++++++-
>>>>> include/linux/soc/mediatek/mtk-mmsys.h | 4 +
>>>>> include/linux/soc/mediatek/mtk-mutex.h | 35 +++++
>>>>> 9 files changed, 274 insertions(+), 12 deletions(-)
>>>>>