* [PATCH 0/4] arm64: dts: k3: Resolve remaining dtbs_check warnings
@ 2024-06-24 6:20 Jan Kiszka
2024-06-24 6:20 ` [PATCH 1/4] arm64: dts: ti: k3-j72xx-mcu-wakeup: add dedicated wakeup controller compatible Jan Kiszka
` (3 more replies)
0 siblings, 4 replies; 9+ messages in thread
From: Jan Kiszka @ 2024-06-24 6:20 UTC (permalink / raw)
To: Nishanth Menon, Vignesh Raghavendra, Tero Kristo, Rob Herring,
Krzysztof Kozlowski, Conor Dooley
Cc: linux-arm-kernel, linux-kernel, devicetree, Bao Cheng Su,
Diogo Ivo
This goes on top of
https://patchwork.kernel.org/project/linux-arm-kernel/cover/20240518-dt-bindings-ti-soc-mfd-v1-0-b3952f104c9a@linaro.org/
As we are working in this area, having a zero-warning baseline helps a
lot finding own issues quicker. Maybe not all of the suggested
resolutions are optimal, open for feedback, just want to have them all
fixed now soon.
Jan
Jan Kiszka (4):
arm64: dts: ti: k3-j72xx-mcu-wakeup: add dedicated wakeup controller
compatible
arm64: dts: ti: k3-am642-evm: Silence schema warning
dt-bindings: soc: ti: am645-system-controller: add child nodes used by
main domain
arm64: dts: ti: k3-am65-main: add system controller compatible
.../soc/ti/ti,am654-system-controller.yaml | 29 +++++++++++++++++++
arch/arm64/boot/dts/ti/k3-am642-evm.dts | 4 +++
arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 2 +-
.../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 2 +-
.../boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 2 +-
.../boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 2 +-
6 files changed, 37 insertions(+), 4 deletions(-)
--
2.43.0
^ permalink raw reply [flat|nested] 9+ messages in thread
* [PATCH 1/4] arm64: dts: ti: k3-j72xx-mcu-wakeup: add dedicated wakeup controller compatible
2024-06-24 6:20 [PATCH 0/4] arm64: dts: k3: Resolve remaining dtbs_check warnings Jan Kiszka
@ 2024-06-24 6:20 ` Jan Kiszka
2024-06-27 23:31 ` Andrew Davis
2024-06-24 6:20 ` [PATCH 2/4] arm64: dts: ti: k3-am642-evm: Silence schema warning Jan Kiszka
` (2 subsequent siblings)
3 siblings, 1 reply; 9+ messages in thread
From: Jan Kiszka @ 2024-06-24 6:20 UTC (permalink / raw)
To: Nishanth Menon, Vignesh Raghavendra, Tero Kristo, Rob Herring,
Krzysztof Kozlowski, Conor Dooley
Cc: linux-arm-kernel, linux-kernel, devicetree, Bao Cheng Su,
Diogo Ivo
From: Jan Kiszka <jan.kiszka@siemens.com>
Each syscon node must come with a dedicated/specific compatible, which
is also reported by dtbs_check:
k3-j7200-common-proc-board.dtb: scm-conf@40f00000: compatible: ['syscon', 'simple-mfd'] is too short
Add one for the TI K3 AM654 MCU wakeup system controller used in J72xx
SoCs.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 2 +-
arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 2 +-
arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
index fccaabfb1348..3a78a3c1676d 100644
--- a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
@@ -165,7 +165,7 @@ mcu_timer9: timer@40490000 {
};
mcu_conf: syscon@40f00000 {
- compatible = "syscon", "simple-mfd";
+ compatible = "ti,am654-system-controller", "syscon", "simple-mfd";
reg = <0x00 0x40f00000 0x00 0x20000>;
#address-cells = <1>;
#size-cells = <1>;
diff --git a/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
index 9349ae07c046..d68e33d71eb3 100644
--- a/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
@@ -35,7 +35,7 @@ k3_reset: reset-controller {
};
mcu_conf: syscon@40f00000 {
- compatible = "syscon", "simple-mfd";
+ compatible = "ti,am654-system-controller", "syscon", "simple-mfd";
reg = <0x0 0x40f00000 0x0 0x20000>;
#address-cells = <1>;
#size-cells = <1>;
diff --git a/arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi
index 5ccb04c7c462..1edb71f4a1bb 100644
--- a/arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi
@@ -140,7 +140,7 @@ wkup_gpio_intr: interrupt-controller@42200000 {
};
mcu_conf: syscon@40f00000 {
- compatible = "syscon", "simple-mfd";
+ compatible = "ti,am654-system-controller", "syscon", "simple-mfd";
reg = <0x0 0x40f00000 0x0 0x20000>;
#address-cells = <1>;
#size-cells = <1>;
--
2.43.0
^ permalink raw reply related [flat|nested] 9+ messages in thread
* [PATCH 2/4] arm64: dts: ti: k3-am642-evm: Silence schema warning
2024-06-24 6:20 [PATCH 0/4] arm64: dts: k3: Resolve remaining dtbs_check warnings Jan Kiszka
2024-06-24 6:20 ` [PATCH 1/4] arm64: dts: ti: k3-j72xx-mcu-wakeup: add dedicated wakeup controller compatible Jan Kiszka
@ 2024-06-24 6:20 ` Jan Kiszka
2024-06-24 6:20 ` [PATCH 3/4] dt-bindings: soc: ti: am645-system-controller: add child nodes used by main domain Jan Kiszka
2024-06-24 6:20 ` [PATCH 4/4] arm64: dts: ti: k3-am65-main: add system controller compatible Jan Kiszka
3 siblings, 0 replies; 9+ messages in thread
From: Jan Kiszka @ 2024-06-24 6:20 UTC (permalink / raw)
To: Nishanth Menon, Vignesh Raghavendra, Tero Kristo, Rob Herring,
Krzysztof Kozlowski, Conor Dooley
Cc: linux-arm-kernel, linux-kernel, devicetree, Bao Cheng Su,
Diogo Ivo
From: Jan Kiszka <jan.kiszka@siemens.com>
The resolves
k3-am642-evm.dtb: adc: 'ti,adc-channels' is a required property
from schema $id: http://devicetree.org/schemas/iio/adc/ti,am3359-adc.yaml#
As the adc is reserved, thus not used by Linux, this has no practical
impact.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
arch/arm64/boot/dts/ti/k3-am642-evm.dts | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am642-evm.dts b/arch/arm64/boot/dts/ti/k3-am642-evm.dts
index e20e4ffd0f1f..0e42d09aa785 100644
--- a/arch/arm64/boot/dts/ti/k3-am642-evm.dts
+++ b/arch/arm64/boot/dts/ti/k3-am642-evm.dts
@@ -640,6 +640,10 @@ cpsw3g_phy0: ethernet-phy@0 {
&tscadc0 {
/* ADC is reserved for R5 usage */
status = "reserved";
+
+ adc {
+ ti,adc-channels = <0 1 2 3 4 5 6 7>;
+ };
};
&ospi0 {
--
2.43.0
^ permalink raw reply related [flat|nested] 9+ messages in thread
* [PATCH 3/4] dt-bindings: soc: ti: am645-system-controller: add child nodes used by main domain
2024-06-24 6:20 [PATCH 0/4] arm64: dts: k3: Resolve remaining dtbs_check warnings Jan Kiszka
2024-06-24 6:20 ` [PATCH 1/4] arm64: dts: ti: k3-j72xx-mcu-wakeup: add dedicated wakeup controller compatible Jan Kiszka
2024-06-24 6:20 ` [PATCH 2/4] arm64: dts: ti: k3-am642-evm: Silence schema warning Jan Kiszka
@ 2024-06-24 6:20 ` Jan Kiszka
2024-06-24 16:24 ` Conor Dooley
2024-06-24 6:20 ` [PATCH 4/4] arm64: dts: ti: k3-am65-main: add system controller compatible Jan Kiszka
3 siblings, 1 reply; 9+ messages in thread
From: Jan Kiszka @ 2024-06-24 6:20 UTC (permalink / raw)
To: Nishanth Menon, Vignesh Raghavendra, Tero Kristo, Rob Herring,
Krzysztof Kozlowski, Conor Dooley
Cc: linux-arm-kernel, linux-kernel, devicetree, Bao Cheng Su,
Diogo Ivo
From: Jan Kiszka <jan.kiszka@siemens.com>
Expand bindings to cover both the MCU and the main usage of the AM654
system controller.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
.../soc/ti/ti,am654-system-controller.yaml | 29 +++++++++++++++++++
1 file changed, 29 insertions(+)
diff --git a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
index e79803e586ca..0eec807f38df 100644
--- a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
+++ b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
@@ -34,6 +34,35 @@ patternProperties:
type: object
$ref: /schemas/phy/ti,phy-gmii-sel.yaml#
+ "^mux-controller$":
+ type: object
+ description:
+ This is the SERDES lane control mux.
+
+ "^clock@[0-9a-f]+$":
+ type: object
+ $ref: /schemas/mfd/syscon.yaml#
+ properties:
+ compatible:
+ items:
+ - const: ti,am654-serdes-ctrl
+ - const: syscon
+
+ "^dss-oldi-io-ctrl@[0-9a-f]+$":
+ type: object
+ $ref: /schemas/mfd/syscon.yaml#
+ properties:
+ compatible:
+ items:
+ - const: ti,am654-dss-oldi-io-ctrl
+ - const: syscon
+
+ "^clock-controller@[0-9a-f]+$":
+ type: object
+ $ref: /schemas/clock/ti,am654-ehrpwm-tbclk.yaml#
+ description:
+ Clock provider for TI EHRPWM nodes.
+
required:
- compatible
- reg
--
2.43.0
^ permalink raw reply related [flat|nested] 9+ messages in thread
* [PATCH 4/4] arm64: dts: ti: k3-am65-main: add system controller compatible
2024-06-24 6:20 [PATCH 0/4] arm64: dts: k3: Resolve remaining dtbs_check warnings Jan Kiszka
` (2 preceding siblings ...)
2024-06-24 6:20 ` [PATCH 3/4] dt-bindings: soc: ti: am645-system-controller: add child nodes used by main domain Jan Kiszka
@ 2024-06-24 6:20 ` Jan Kiszka
3 siblings, 0 replies; 9+ messages in thread
From: Jan Kiszka @ 2024-06-24 6:20 UTC (permalink / raw)
To: Nishanth Menon, Vignesh Raghavendra, Tero Kristo, Rob Herring,
Krzysztof Kozlowski, Conor Dooley
Cc: linux-arm-kernel, linux-kernel, devicetree, Bao Cheng Su,
Diogo Ivo
From: Jan Kiszka <jan.kiszka@siemens.com>
Now that the TI K3 AM654 system controller bindings also cover the usage
in the main domain, add its compatible to address dtbs_check complaints:
k3-am654-base-board.dtb: scm-conf@100000: compatible: ['syscon', 'simple-mfd'] is too short
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/ti/k3-am65-main.dtsi b/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
index 30c514e458a3..fe90e84c34fc 100644
--- a/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
@@ -471,7 +471,7 @@ sdhci1: mmc@4fa0000 {
};
scm_conf: scm-conf@100000 {
- compatible = "syscon", "simple-mfd";
+ compatible = "ti,am654-system-controller", "syscon", "simple-mfd";
reg = <0 0x00100000 0 0x1c000>;
#address-cells = <1>;
#size-cells = <1>;
--
2.43.0
^ permalink raw reply related [flat|nested] 9+ messages in thread
* Re: [PATCH 3/4] dt-bindings: soc: ti: am645-system-controller: add child nodes used by main domain
2024-06-24 6:20 ` [PATCH 3/4] dt-bindings: soc: ti: am645-system-controller: add child nodes used by main domain Jan Kiszka
@ 2024-06-24 16:24 ` Conor Dooley
2024-06-24 20:23 ` Jan Kiszka
0 siblings, 1 reply; 9+ messages in thread
From: Conor Dooley @ 2024-06-24 16:24 UTC (permalink / raw)
To: Jan Kiszka
Cc: Nishanth Menon, Vignesh Raghavendra, Tero Kristo, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, linux-arm-kernel, linux-kernel,
devicetree, Bao Cheng Su, Diogo Ivo
[-- Attachment #1: Type: text/plain, Size: 1756 bytes --]
On Mon, Jun 24, 2024 at 08:20:49AM +0200, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Expand bindings to cover both the MCU and the main usage of the AM654
> system controller.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> .../soc/ti/ti,am654-system-controller.yaml | 29 +++++++++++++++++++
> 1 file changed, 29 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
> index e79803e586ca..0eec807f38df 100644
> --- a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
> +++ b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
> @@ -34,6 +34,35 @@ patternProperties:
> type: object
> $ref: /schemas/phy/ti,phy-gmii-sel.yaml#
>
> + "^mux-controller$":
> + type: object
> + description:
> + This is the SERDES lane control mux.
Where is this object described?
> +
> + "^clock@[0-9a-f]+$":
> + type: object
> + $ref: /schemas/mfd/syscon.yaml#
> + properties:
> + compatible:
> + items:
> + - const: ti,am654-serdes-ctrl
> + - const: syscon
> +
> + "^dss-oldi-io-ctrl@[0-9a-f]+$":
> + type: object
> + $ref: /schemas/mfd/syscon.yaml#
> + properties:
> + compatible:
> + items:
> + - const: ti,am654-dss-oldi-io-ctrl
> + - const: syscon
> +
> + "^clock-controller@[0-9a-f]+$":
> + type: object
> + $ref: /schemas/clock/ti,am654-ehrpwm-tbclk.yaml#
> + description:
> + Clock provider for TI EHRPWM nodes.
> +
> required:
> - compatible
> - reg
> --
> 2.43.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH 3/4] dt-bindings: soc: ti: am645-system-controller: add child nodes used by main domain
2024-06-24 16:24 ` Conor Dooley
@ 2024-06-24 20:23 ` Jan Kiszka
2024-06-25 16:10 ` Conor Dooley
0 siblings, 1 reply; 9+ messages in thread
From: Jan Kiszka @ 2024-06-24 20:23 UTC (permalink / raw)
To: Conor Dooley
Cc: Nishanth Menon, Vignesh Raghavendra, Tero Kristo, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, linux-arm-kernel, linux-kernel,
devicetree, Bao Cheng Su, Diogo Ivo
On 24.06.24 18:24, Conor Dooley wrote:
> On Mon, Jun 24, 2024 at 08:20:49AM +0200, Jan Kiszka wrote:
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> Expand bindings to cover both the MCU and the main usage of the AM654
>> system controller.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>> .../soc/ti/ti,am654-system-controller.yaml | 29 +++++++++++++++++++
>> 1 file changed, 29 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
>> index e79803e586ca..0eec807f38df 100644
>> --- a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
>> +++ b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
>> @@ -34,6 +34,35 @@ patternProperties:
>> type: object
>> $ref: /schemas/phy/ti,phy-gmii-sel.yaml#
>>
>> + "^mux-controller$":
>> + type: object
>> + description:
>> + This is the SERDES lane control mux.
>
> Where is this object described?
>
Nowhere so far - I've only followed the pattern in
mfd/ti,j721e-system-controller.yaml. Would adding "ref:
/schemas/mux/reg-mux.yaml" be enough?
Jan
--
Siemens AG, Technology
Linux Expert Center
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH 3/4] dt-bindings: soc: ti: am645-system-controller: add child nodes used by main domain
2024-06-24 20:23 ` Jan Kiszka
@ 2024-06-25 16:10 ` Conor Dooley
0 siblings, 0 replies; 9+ messages in thread
From: Conor Dooley @ 2024-06-25 16:10 UTC (permalink / raw)
To: Jan Kiszka
Cc: Nishanth Menon, Vignesh Raghavendra, Tero Kristo, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, linux-arm-kernel, linux-kernel,
devicetree, Bao Cheng Su, Diogo Ivo
[-- Attachment #1: Type: text/plain, Size: 1400 bytes --]
On Mon, Jun 24, 2024 at 10:23:37PM +0200, Jan Kiszka wrote:
> On 24.06.24 18:24, Conor Dooley wrote:
> > On Mon, Jun 24, 2024 at 08:20:49AM +0200, Jan Kiszka wrote:
> >> From: Jan Kiszka <jan.kiszka@siemens.com>
> >>
> >> Expand bindings to cover both the MCU and the main usage of the AM654
> >> system controller.
> >>
> >> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> >> ---
> >> .../soc/ti/ti,am654-system-controller.yaml | 29 +++++++++++++++++++
> >> 1 file changed, 29 insertions(+)
> >>
> >> diff --git a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
> >> index e79803e586ca..0eec807f38df 100644
> >> --- a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
> >> +++ b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
> >> @@ -34,6 +34,35 @@ patternProperties:
> >> type: object
> >> $ref: /schemas/phy/ti,phy-gmii-sel.yaml#
> >>
> >> + "^mux-controller$":
> >> + type: object
> >> + description:
> >> + This is the SERDES lane control mux.
> >
> > Where is this object described?
> >
>
> Nowhere so far - I've only followed the pattern in
> mfd/ti,j721e-system-controller.yaml. Would adding "ref:
> /schemas/mux/reg-mux.yaml" be enough?
I think that would be okay, yea
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH 1/4] arm64: dts: ti: k3-j72xx-mcu-wakeup: add dedicated wakeup controller compatible
2024-06-24 6:20 ` [PATCH 1/4] arm64: dts: ti: k3-j72xx-mcu-wakeup: add dedicated wakeup controller compatible Jan Kiszka
@ 2024-06-27 23:31 ` Andrew Davis
0 siblings, 0 replies; 9+ messages in thread
From: Andrew Davis @ 2024-06-27 23:31 UTC (permalink / raw)
To: Jan Kiszka, Nishanth Menon, Vignesh Raghavendra, Tero Kristo,
Rob Herring, Krzysztof Kozlowski, Conor Dooley
Cc: linux-arm-kernel, linux-kernel, devicetree, Bao Cheng Su,
Diogo Ivo
On 6/24/24 1:20 AM, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Each syscon node must come with a dedicated/specific compatible, which
> is also reported by dtbs_check:
>
> k3-j7200-common-proc-board.dtb: scm-conf@40f00000: compatible: ['syscon', 'simple-mfd'] is too short
>
> Add one for the TI K3 AM654 MCU wakeup system controller used in J72xx
> SoCs.
Unfortunately this is not correct, this region is not an AM654 MCU system
controller, it is a J721e MCU system controller. Some registers are the same,
but others are not. So if labeled as a "ti,am654-system-controller" we would
not be able to add the rest of the child nodes only found on the J7x devices.
A more correct fix for the warning would be the following:
diff --git a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
index fccaabfb13482..5097d192c2b20 100644
--- a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
@@ -164,12 +164,16 @@ mcu_timer9: timer@40490000 {
ti,timer-pwm;
};
- mcu_conf: syscon@40f00000 {
- compatible = "syscon", "simple-mfd";
- reg = <0x00 0x40f00000 0x00 0x20000>;
+ mcu_conf: bus@40f00000 {
+ compatible = "simple-bus";
#address-cells = <1>;
#size-cells = <1>;
- ranges = <0x00 0x00 0x40f00000 0x20000>;
+ ranges = <0x0 0x0 0x40f00000 0x20000>;
+
+ cpsw_mac_syscon: ethernet-mac-syscon@200 {
+ compatible = "ti,am62p-cpsw-mac-efuse", "syscon";
+ reg = <0x200 0x8>;
+ };
phy_gmii_sel: phy@4040 {
compatible = "ti,am654-phy-gmii-sel";
@@ -420,7 +424,7 @@ cpsw_port1: port@1 {
reg = <1>;
ti,mac-only;
label = "port1";
- ti,syscon-efuse = <&mcu_conf 0x200>;
+ ti,syscon-efuse = <&cpsw_mac_syscon 0x0>;
phys = <&phy_gmii_sel 1>;
};
};
I'll clean this up and post it for the other J7x devices tomorrow.
Andrew
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 2 +-
> arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 2 +-
> arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
> index fccaabfb1348..3a78a3c1676d 100644
> --- a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
> @@ -165,7 +165,7 @@ mcu_timer9: timer@40490000 {
> };
>
> mcu_conf: syscon@40f00000 {
> - compatible = "syscon", "simple-mfd";
> + compatible = "ti,am654-system-controller", "syscon", "simple-mfd";
> reg = <0x00 0x40f00000 0x00 0x20000>;
> #address-cells = <1>;
> #size-cells = <1>;
> diff --git a/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
> index 9349ae07c046..d68e33d71eb3 100644
> --- a/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
> @@ -35,7 +35,7 @@ k3_reset: reset-controller {
> };
>
> mcu_conf: syscon@40f00000 {
> - compatible = "syscon", "simple-mfd";
> + compatible = "ti,am654-system-controller", "syscon", "simple-mfd";
> reg = <0x0 0x40f00000 0x0 0x20000>;
> #address-cells = <1>;
> #size-cells = <1>;
> diff --git a/arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi
> index 5ccb04c7c462..1edb71f4a1bb 100644
> --- a/arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi
> @@ -140,7 +140,7 @@ wkup_gpio_intr: interrupt-controller@42200000 {
> };
>
> mcu_conf: syscon@40f00000 {
> - compatible = "syscon", "simple-mfd";
> + compatible = "ti,am654-system-controller", "syscon", "simple-mfd";
> reg = <0x0 0x40f00000 0x0 0x20000>;
> #address-cells = <1>;
> #size-cells = <1>;
^ permalink raw reply related [flat|nested] 9+ messages in thread
end of thread, other threads:[~2024-06-27 23:31 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-06-24 6:20 [PATCH 0/4] arm64: dts: k3: Resolve remaining dtbs_check warnings Jan Kiszka
2024-06-24 6:20 ` [PATCH 1/4] arm64: dts: ti: k3-j72xx-mcu-wakeup: add dedicated wakeup controller compatible Jan Kiszka
2024-06-27 23:31 ` Andrew Davis
2024-06-24 6:20 ` [PATCH 2/4] arm64: dts: ti: k3-am642-evm: Silence schema warning Jan Kiszka
2024-06-24 6:20 ` [PATCH 3/4] dt-bindings: soc: ti: am645-system-controller: add child nodes used by main domain Jan Kiszka
2024-06-24 16:24 ` Conor Dooley
2024-06-24 20:23 ` Jan Kiszka
2024-06-25 16:10 ` Conor Dooley
2024-06-24 6:20 ` [PATCH 4/4] arm64: dts: ti: k3-am65-main: add system controller compatible Jan Kiszka
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).