Odroid N2 failes to boot using upstream kernel & u-boot
Subsystems (4)
cover Odroid N2 failes to boot using upstream kernel & u-boot
We am trying to build the upstream u-boot and upstream kernel, but it fails to pass the initialization of PWM_MESON driver. So these patches help boot the kernel on microSD card.
Patchs based on Linux 5.4-rc2
Boot log failed are shown below.
[0] https://pastebin.com/cEtWq2iX
[ 1.569240] meson-gx-mmc ffe05000.sd: Got CD GPIO [ 1.599227] pwm-regulator regulator-vddcpu-a: Failed to get PWM: -517 [ 1.600605] pwm-regulator regulator-vddcpu-b: Failed to get PWM: -517 [ 1.607166] pwm-regulator regulator-vddcpu-a: Failed to get PWM: -517 [ 1.613273] pwm-regulator regulator-vddcpu-b: Failed to get PWM: -517 [ 1.619931] hctosys: unable to open rtc device (rtc0)
My guess their is not much issue with eMMC module, if their is other approach to resolve this issue, I will give this a try.
Best Regards
-Anand
Anand Moon (5):
arm64: dts: meson: Add missing 5V_EN gpio signal for VCC5V regulator
arm64: dts: meson: Add missing pwm control gpio signal for
pwm-regulator
arm64: dts: meson: Add missing regulator linked to VDDAO_3V3 regulator
to FLASH_VDD
arm64: dts: meson: Add missing regulator linked to VCCV5 regulator to
VDDIO_C/TF_IO
arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
.../arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts | 13 +++++++++++++ arch/arm64/configs/defconfig | 2 +- 2 files changed, 14 insertions(+), 1 deletion(-)
Signature · 1 line
2.23.0
RFC 1/5 arm64: dts: meson: Add missing 5V_EN gpio signal for VCC5V regulator
As per schematics add missing 5V_EN gpio signal to enable VCC5V regulator node.
--- arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts | 3 +++ 1 file changed, 3 insertions(+)
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +3 -0
@@ -94,6 +94,9 @@ regulator-max-microvolt = <5000000>; regulator-always-on; vin-supply = <&main_12v>; + /* U12 NB679GD 5V_EN */ + gpio = <&gpio GPIOH_8 GPIO_OPEN_DRAIN>; + enable-active-high; }; vcc_1v8: regulator-vcc_1v8 {
Signature · 1 line
2.23.0
Re: [RFCv1 1/5] arm64: dts: meson: Add missing 5V_EN gpio signal for VCC5V regulator
Hi Anand,
Quoted 17 lines · Anand Moon
As per schematics add missing 5V_EN gpio signal to enable VCC5V regulator node.
Fixes c35f6dc5c377 (arm64: dts: meson: Add minimal support for Odroid-N2)Cc Martin Blumenstingl <[email protected]>Cc Jerome Brunet <[email protected]>Cc Neil Armstrong <[email protected]>Signed-off-by Anand Moon <[email protected]>--- arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts | 3 +++ 1 file changed, 3 insertions(+)arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +0
-0
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts line 99
Quoted 6 lines
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +3
-0@@ -94,6 +94,9 @@ regulator-max-microvolt = <5000000>; regulator-always-on; vin-supply = <&main_12v>; + /* U12 NB679GD 5V_EN */ + gpio = <&gpio GPIOH_8 GPIO_OPEN_DRAIN>; + enable-active-high;
This GPIO is handled by the BL301 SCP firmware, I'm personally against adding this to the DT since it's out of control of Linux or any OS.
Neil
Quoted 4 lines
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +0
-0}; vcc_1v8: regulator-vcc_1v8 {
Re: [RFCv1 1/5] arm64: dts: meson: Add missing 5V_EN gpio signal for VCC5V regulator
Hi Neil,
Quoted 31 lines · Neil Armstrong
Hi Anand,
Quoted 17 lines · Anand Moon
As per schematics add missing 5V_EN gpio signal to enable VCC5V regulator node.
Fixes c35f6dc5c377 (arm64: dts: meson: Add minimal support for Odroid-N2)Cc Martin Blumenstingl <[email protected]>Cc Jerome Brunet <[email protected]>Cc Neil Armstrong <[email protected]>Signed-off-by Anand Moon <[email protected]>--- arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts | 3 +++ 1 file changed, 3 insertions(+)arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +0
-0arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts line 99
Quoted 6 lines
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +3
-0@@ -94,6 +94,9 @@ regulator-max-microvolt = <5000000>; regulator-always-on; vin-supply = <&main_12v>; + /* U12 NB679GD 5V_EN */ + gpio = <&gpio GPIOH_8 GPIO_OPEN_DRAIN>; + enable-active-high;This GPIO is handled by the BL301 SCP firmware, I'm personally against adding this to the DT since it's out of control of Linux or any OS.
Quoted 2 lines
Neil
Thanks for your input.
Quoted 5 lines
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts line 102
Quoted 4 lines
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +0
-0}; vcc_1v8: regulator-vcc_1v8 {
Best Regards
-Anand
RFC 2/5 arm64: dts: meson: Add missing pwm control gpio signal for pwm-regulator
In reply to Anand MoonAs per schematics add missing VDDCPUA_PWM and VDDCPUB_PWM gpio signal use to enable/disable the pwm regulator for DVFS.
--- arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts | 4 ++++ 1 file changed, 4 insertions(+)
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +4 -0
@@ -135,6 +135,8 @@ regulator-boot-on; regulator-always-on; + /* VDDCPUA_PWM */ + enable-gpios = <&gpio GPIOE_1 GPIO_ACTIVE_HIGH>; }; vddcpu_b: regulator-vddcpu-b {
@@ -154,6 +156,8 @@ regulator-boot-on; regulator-always-on; + /* VDDCPUB_PWM */ + enable-gpios = <&gpio GPIOE_2 GPIO_ACTIVE_HIGH>; }; hub_5v: regulator-hub_5v {
Signature · 1 line
2.23.0
Re: [RFCv1 2/5] arm64: dts: meson: Add missing pwm control gpio signal for pwm-regulator
Quoted 27 lines · Anand Moon
As per schematics add missing
VDDCPUA_PWMandVDDCPUB_PWMgpio signal use to enable/disable the pwm regulator for DVFS.Fixes d14734a04a8a (arm64: dts: meson-g12b-odroid-n2: enable DVFS)Cc Martin Blumenstingl <[email protected]>Cc Jerome Brunet <[email protected]>Cc Neil Armstrong <[email protected]>Signed-off-by Anand Moon <[email protected]>--- arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts | 4 ++++ 1 file changed, 4 insertions(+)arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +2
-0@@ -135,6 +135,8 @@ regulator-boot-on; regulator-always-on; + /* VDDCPUA_PWM */ + enable-gpios = <&gpio GPIOE_1 GPIO_ACTIVE_HIGH>; }; vddcpu_b: regulator-vddcpu-b {
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts line 163
Quoted 8 lines
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +2
-0@@ -154,6 +156,8 @@ regulator-boot-on; regulator-always-on; + /* VDDCPUB_PWM */ + enable-gpios = <&gpio GPIOE_2 GPIO_ACTIVE_HIGH>; }; hub_5v: regulator-hub_5v {
Same as 5V_EN, This GPIO is handled by the BL301 SCP firmware, I'm personally against adding this to the DT since it's out of control of Linux or any OS.
This GPIO id controlles by the PSCI call to SCP to enable/disable the CPU clusters.
Neil
Re: [RFCv1 2/5] arm64: dts: meson: Add missing pwm control gpio signal for pwm-regulator
Hi Neil,
Quoted 41 lines · Neil Armstrong
Quoted 27 lines · Anand Moon
As per schematics add missing
VDDCPUA_PWMandVDDCPUB_PWMgpio signal use to enable/disable the pwm regulator for DVFS.Fixes d14734a04a8a (arm64: dts: meson-g12b-odroid-n2: enable DVFS)Cc Martin Blumenstingl <[email protected]>Cc Jerome Brunet <[email protected]>Cc Neil Armstrong <[email protected]>Signed-off-by Anand Moon <[email protected]>--- arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts | 4 ++++ 1 file changed, 4 insertions(+)arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +2
-0@@ -135,6 +135,8 @@ regulator-boot-on; regulator-always-on; + /* VDDCPUA_PWM */ + enable-gpios = <&gpio GPIOE_1 GPIO_ACTIVE_HIGH>; }; vddcpu_b: regulator-vddcpu-b {arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts line 163
Quoted 8 lines
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +2
-0@@ -154,6 +156,8 @@ regulator-boot-on; regulator-always-on; + /* VDDCPUB_PWM */ + enable-gpios = <&gpio GPIOE_2 GPIO_ACTIVE_HIGH>; }; hub_5v: regulator-hub_5v {Same as 5V_EN, This GPIO is handled by the BL301 SCP firmware, I'm personally against adding this to the DT since it's out of control of Linux or any OS.
Quoted 4 lines
This GPIO id controlles by the PSCI call to SCP to enable/disable the CPU clusters.
Neil
Thanks for your input's.
Best Regards
-Anand
RFC 3/5 arm64: dts: meson: Add missing regulator linked to VDDAO_3V3 regulator to FLASH_VDD
In reply to Anand MoonAs per schematics add missing VDDAO_3V3 power supply to FLASH_VDD regulator. Also add TFLASH_VDD_EN signal name to gpio pin.
--- arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts | 3 +++ 1 file changed, 3 insertions(+)
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +3 -0
@@ -51,9 +51,12 @@ regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; + /* TFLASH_VDD_EN */ gpio = <&gpio_ao GPIOAO_8 GPIO_ACTIVE_HIGH>; enable-active-high; regulator-always-on; + /* U18 FC8731-09VF05NRR */ + vin-supply = <&vddao_3v3>; }; tf_io: gpio-regulator-tf_io {
Signature · 1 line
2.23.0
Re: [RFCv1 3/5] arm64: dts: meson: Add missing regulator linked to VDDAO_3V3 regulator to FLASH_VDD
Quoted 20 lines · Anand Moon
As per schematics add missing
VDDAO_3V3power supply toFLASH_VDDregulator. Also addTFLASH_VDD_ENsignal name to gpio pin.Fixes c35f6dc5c377 (arm64: dts: meson: Add minimal support for Odroid-N2)Cc Martin Blumenstingl <[email protected]>Cc Jerome Brunet <[email protected]>Cc Neil Armstrong <[email protected]>Signed-off-by Anand Moon <[email protected]>--- arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts | 3 +++ 1 file changed, 3 insertions(+)arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +0
-0@@ -51,9 +51,12 @@ regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>;
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts line 62
Quoted 10 lines
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +3
-0+ /* TFLASH_VDD_EN */ gpio = <&gpio_ao GPIOAO_8 GPIO_ACTIVE_HIGH>; enable-active-high; regulator-always-on; + /* U18 FC8731-09VF05NRR */ + vin-supply = <&vddao_3v3>; }; tf_io: gpio-regulator-tf_io {
Re: [RFCv1 3/5] arm64: dts: meson: Add missing regulator linked to VDDAO_3V3 regulator to FLASH_VDD
Hi Neil,
Quoted 30 lines · Neil Armstrong
Quoted 28 lines · Anand Moon
As per schematics add missing
VDDAO_3V3power supply toFLASH_VDDregulator. Also addTFLASH_VDD_ENsignal name to gpio pin.Fixes c35f6dc5c377 (arm64: dts: meson: Add minimal support for Odroid-N2)Cc Martin Blumenstingl <[email protected]>Cc Jerome Brunet <[email protected]>Cc Neil Armstrong <[email protected]>Signed-off-by Anand Moon <[email protected]>--- arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts | 3 +++ 1 file changed, 3 insertions(+)arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +3
-0@@ -51,9 +51,12 @@ regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; + /* TFLASH_VDD_EN */ gpio = <&gpio_ao GPIOAO_8 GPIO_ACTIVE_HIGH>; enable-active-high; regulator-always-on; + /* U18 FC8731-09VF05NRR */ + vin-supply = <&vddao_3v3>; };
Quoted 4 lines
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts line 62
Quoted 2 lines
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +0
-0tf_io: gpio-regulator-tf_io {Reviewed-by Neil Armstrong <[email protected]>
Thanks,
Best Regards
-Anand
RFC 4/5 arm64: dts: meson: Add missing regulator linked to VCCV5 regulator to VDDIO_C/TF_IO
In reply to Anand MoonAs per schematics add missing VCCV5 power supply to VDDIO_C/TF_IO regulator. Also add TF_3V3N_1V8_EN signal name to gpio pin.
--- arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts | 3 +++ 1 file changed, 3 insertions(+)
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +3 -0
@@ -66,11 +66,14 @@ regulator-min-microvolt = <1800000>; regulator-max-microvolt = <3300000>; + /* TF_3V3N_1V8_EN */ gpios = <&gpio_ao GPIOAO_9 GPIO_ACTIVE_HIGH>; gpios-states = <0>; states = <3300000 0>, <1800000 1>; + /* U16 RT9179GB */ + vin-supply = <&vcc_5v>; }; flash_1v8: regulator-flash_1v8 {
Signature · 1 line
2.23.0
Re: [RFCv1 4/5] arm64: dts: meson: Add missing regulator linked to VCCV5 regulator to VDDIO_C/TF_IO
Quoted 22 lines · Anand Moon
As per schematics add missing VCCV5 power supply to VDDIO_C/TF_IO regulator. Also add
TF_3V3N_1V8_ENsignal name to gpio pin.Fixes c35f6dc5c377 (arm64: dts: meson: Add minimal support for Odroid-N2)Cc Martin Blumenstingl <[email protected]>Cc Jerome Brunet <[email protected]>Cc Neil Armstrong <[email protected]>Signed-off-by Anand Moon <[email protected]>--- arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts | 3 +++ 1 file changed, 3 insertions(+)arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +1
-0@@ -66,11 +66,14 @@ regulator-min-microvolt = <1800000>; regulator-max-microvolt = <3300000>; + /* TF_3V3N_1V8_EN */
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts line 79
Quoted 10 lines
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +2
-0gpios = <&gpio_ao GPIOAO_9 GPIO_ACTIVE_HIGH>; gpios-states = <0>; states = <3300000 0>, <1800000 1>; + /* U16 RT9179GB */ + vin-supply = <&vcc_5v>; }; flash_1v8: regulator-flash_1v8 {
Re: [RFCv1 4/5] arm64: dts: meson: Add missing regulator linked to VCCV5 regulator to VDDIO_C/TF_IO
Hi Neil,
Quoted 32 lines · Neil Armstrong
Quoted 30 lines · Anand Moon
As per schematics add missing VCCV5 power supply to VDDIO_C/TF_IO regulator. Also add
TF_3V3N_1V8_ENsignal name to gpio pin.Fixes c35f6dc5c377 (arm64: dts: meson: Add minimal support for Odroid-N2)Cc Martin Blumenstingl <[email protected]>Cc Jerome Brunet <[email protected]>Cc Neil Armstrong <[email protected]>Signed-off-by Anand Moon <[email protected]>--- arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts | 3 +++ 1 file changed, 3 insertions(+)arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +3
-0@@ -66,11 +66,14 @@ regulator-min-microvolt = <1800000>; regulator-max-microvolt = <3300000>; + /* TF_3V3N_1V8_EN */ gpios = <&gpio_ao GPIOAO_9 GPIO_ACTIVE_HIGH>; gpios-states = <0>; states = <3300000 0>, <1800000 1>; + /* U16 RT9179GB */ + vin-supply = <&vcc_5v>; };
Quoted 4 lines
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts line 79
Quoted 2 lines
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +0
-0flash_1v8: regulator-flash_1v8 {Reviewed-by Neil Armstrong <[email protected]>
Thanks,
Best Regards
-Anand
RFC 5/5 arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
In reply to Anand MoonUsing microSD card we cannot get the mainline kernel to boot using mainline u-boot it fails with below logs. Build PWM_MESSON as build-in solve the issue.
[ 1.569240] meson-gx-mmc ffe05000.sd: Got CD GPIO [ 1.599227] pwm-regulator regulator-vddcpu-a: Failed to get PWM: -517 [ 1.600605] pwm-regulator regulator-vddcpu-b: Failed to get PWM: -517 [ 1.607166] pwm-regulator regulator-vddcpu-a: Failed to get PWM: -517 [ 1.613273] pwm-regulator regulator-vddcpu-b: Failed to get PWM: -517 [ 1.619931] hctosys: unable to open rtc device (rtc0)
---
Odroid N2 Schematics says "GPIOC_6 should not pulled low if GPIOC is not work as SDCARD"
Is their any other approch to help resolve this issue.
Boot log failed with cold boot:
[0] https://pastebin.com/cEtWq2iX
--- arch/arm64/configs/defconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/configs/defconfig +1 -1
@@ -774,7 +774,7 @@ CONFIG_MPL3115=m CONFIG_PWM=y CONFIG_PWM_BCM2835=m CONFIG_PWM_CROS_EC=m -CONFIG_PWM_MESON=m +CONFIG_PWM_MESON=y CONFIG_PWM_RCAR=m CONFIG_PWM_ROCKCHIP=y CONFIG_PWM_SAMSUNG=y
Signature · 1 line
2.23.0
Re: [RFCv1 5/5] arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
Quoted 1 line · Anand Moon
Using microSD card we cannot get the mainline kernel to boot
What's the link with microSD card here ?
Quoted 10 lines
using mainline u-boot it fails with below logs.
BuildPWM_MESSONas build-in solve the issue.[ 1.569240] meson-gx-mmc ffe05000.sd: Got CD GPIO [ 1.599227] pwm-regulator regulator-vddcpu-a: Failed to get PWM: -517 [ 1.600605] pwm-regulator regulator-vddcpu-b: Failed to get PWM: -517 [ 1.607166] pwm-regulator regulator-vddcpu-a: Failed to get PWM: -517 [ 1.613273] pwm-regulator regulator-vddcpu-b: Failed to get PWM: -517 [ 1.619931] hctosys: unable to open rtc device (rtc0)
Quoted 7 lines
Cc Martin Blumenstingl <[email protected]>Cc Jerome Brunet <[email protected]>Cc Neil Armstrong <[email protected]>Signed-off-by Anand Moon <[email protected]>---
Odroid N2 Schematics says "GPIOC_6should not pulled low if GPIOC is not work as SDCARD"
Sorry, what's the link with the PWM build-in, and your case ?
This comment is linked to the comment in the datasheet:
""
If GPIOC is not work as SDIO port, please do not pull CARD_DET(GPIOC_6) low when system booting up, to avoid romcode trying to boot from SD CARD.
""
Seems pretty explicit for me.
Quoted 14 lines
Is their any other approch to help resolve this issue.
Boot log failed with cold boot:
[0] https://pastebin.com/cEtWq2iX--- arch/arm64/configs/defconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)arch/arm64/configs/defconfig +0
-0
arch/arm64/configs/defconfig CONFIG_MPL3115=m · line 780
Quoted 8 lines
arch/arm64/configs/defconfig +1
-1@@ -774,7 +774,7 @@ CONFIG_MPL3115=m CONFIG_PWM=y CONFIG_PWM_BCM2835=m CONFIG_PWM_CROS_EC=m -CONFIG_PWM_MESON=m +CONFIG_PWM_MESON=y CONFIG_PWM_RCAR=m CONFIG_PWM_ROCKCHIP=y CONFIG_PWM_SAMSUNG=y
For these changes without the microSD fail description in the commit log :
Re: [RFCv1 5/5] arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
Hi Neil,
Quoted 5 lines · Neil Armstrong
Quoted 1 line · Anand Moon
Using microSD card we cannot get the mainline kernel to boot
What's the link with microSD card here ?
Well I thought that the PWM failed stop's booting further on linux kernel.
But looking into kernelcli.org it seem to be working fine, but not at my end.
[0] https://storage.kernelci.org/media/master/v5.4-rc1-82-gc0e284ccfeda/arm64/defconfig/gcc-8/lab-baylibre/boot-meson-g12b-odroid-n2.txt
Quoted 19 lines
Quoted 11 lines
using mainline u-boot it fails with below logs.
BuildPWM_MESSONas build-in solve the issue.[ 1.569240] meson-gx-mmc ffe05000.sd: Got CD GPIO [ 1.599227] pwm-regulator regulator-vddcpu-a: Failed to get PWM: -517 [ 1.600605] pwm-regulator regulator-vddcpu-b: Failed to get PWM: -517 [ 1.607166] pwm-regulator regulator-vddcpu-a: Failed to get PWM: -517 [ 1.613273] pwm-regulator regulator-vddcpu-b: Failed to get PWM: -517 [ 1.619931] hctosys: unable to open rtc device (rtc0)Quoted 7 lines
Cc Martin Blumenstingl <[email protected]>Cc Jerome Brunet <[email protected]>Cc Neil Armstrong <[email protected]>Signed-off-by Anand Moon <[email protected]>---
Odroid N2 Schematics says "GPIOC_6should not pulled low if GPIOC is not work as SDCARD"
Quoted 2 lines
Sorry, what's the link with the PWM build-in, and your case ?
Sorry I linked two issues with this commit message.
Quoted 7 lines
This comment is linked to the comment in the datasheet:
""
If GPIOC is not work as SDIO port, please do not pullCARD_DET(GPIOC_6)low when system booting up, to avoid romcode trying to boot from SD CARD.
""
Seems pretty explicit for me.
Ok I will recheck this at my end.
Quoted 24 lines
Quoted 14 lines
Is their any other approch to help resolve this issue.
Boot log failed with cold boot:
[0] https://pastebin.com/cEtWq2iX--- arch/arm64/configs/defconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)arch/arm64/configs/defconfig +0
-0arch/arm64/configs/defconfig CONFIG_MPL3115=m · line 780
Quoted 8 lines
arch/arm64/configs/defconfig +1
-1@@ -774,7 +774,7 @@ CONFIG_MPL3115=m CONFIG_PWM=y CONFIG_PWM_BCM2835=m CONFIG_PWM_CROS_EC=m -CONFIG_PWM_MESON=m +CONFIG_PWM_MESON=y CONFIG_PWM_RCAR=m CONFIG_PWM_ROCKCHIP=y CONFIG_PWM_SAMSUNG=yFor these changes without the microSD fail description in the commit log :
Quoted 1 line
Acked-by Neil Armstrong <[email protected]>
Thanks. I will rephrase this without linking the microSD card, with better commit message.
Best Regards
-Anand
Martin Blumenstingl
reviewerRe: [RFCv1 5/5] arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
In reply to Anand MoonOn Mon, Oct 7, 2019 at 3:17 PM Anand Moon <[email protected]> wrote:
[...]
arch/arm64/configs/defconfig CONFIG_MPL3115=m · line 777
Quoted 10 lines
arch/arm64/configs/defconfig +1
-1@@ -774,7 +774,7 @@ CONFIG_MPL3115=m CONFIG_PWM=y CONFIG_PWM_BCM2835=m CONFIG_PWM_CROS_EC=m -CONFIG_PWM_MESON=m +CONFIG_PWM_MESON=y
some time ago I submitted a similar patch for the 32-bit SoCs it turned that that pwm-meson can be built as module because the kernel will run without CPU DVFS as long as the clock and regulator drivers are returning -EPROBE_DEFER (-517)
did you check whether there's some other problem like some unused clock which is being disabled at that moment?
I've been hunting weird problems in the past where it turned out that changing kernel config bits changed the boot timing - that masked the original problem
Martin
Kevin Hilman
maintainerRe: [RFCv1 5/5] arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
Quoted 17 lines · Martin Blumenstingl
On Mon, Oct 7, 2019 at 3:17 PM Anand Moon <[email protected]> wrote:
[...]arch/arm64/configs/defconfig CONFIG_MPL3115=m · line 777
Quoted 10 lines
arch/arm64/configs/defconfig +1
-1@@ -774,7 +774,7 @@ CONFIG_MPL3115=m CONFIG_PWM=y CONFIG_PWM_BCM2835=m CONFIG_PWM_CROS_EC=m -CONFIG_PWM_MESON=m +CONFIG_PWM_MESON=ysome time ago I submitted a similar patch for the 32-bit SoCs it turned that that pwm-meson can be built as module because the kernel will run without CPU DVFS as long as the clock and regulator drivers are returning -EPROBE_DEFER (-517)
On 64-bit SoCs, the kernel boots with PWM as a module also, but DVFS only works sometimes, and making it built-in fixes the problem. Actually, it doesn't fix, it just hides the problem, which is likely a race or timeout happening during deferred probing.
Quoted 5 lines
did you check whether there's some other problem like some unused clock which is being disabled at that moment?
I've been hunting weird problems in the past where it turned out that changing kernel config bits changed the boot timing - that masked the original problem
Right, I would definitely prefer to not make this built-in without a lot more information to *why* this is needed. In figuring that out, we'll probably find the race/timeout that's the root cause.
Kevin
Re: [RFCv1 5/5] arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
Hi Kevin / Martin,
Quoted 32 lines · Kevin Hilman
Quoted 17 lines · Martin Blumenstingl
On Mon, Oct 7, 2019 at 3:17 PM Anand Moon <[email protected]> wrote:
[...]arch/arm64/configs/defconfig CONFIG_MPL3115=m · line 777
Quoted 10 lines
arch/arm64/configs/defconfig +1
-1@@ -774,7 +774,7 @@ CONFIG_MPL3115=m CONFIG_PWM=y CONFIG_PWM_BCM2835=m CONFIG_PWM_CROS_EC=m -CONFIG_PWM_MESON=m +CONFIG_PWM_MESON=ysome time ago I submitted a similar patch for the 32-bit SoCs it turned that that pwm-meson can be built as module because the kernel will run without CPU DVFS as long as the clock and regulator drivers are returning -EPROBE_DEFER (-517)
On 64-bit SoCs, the kernel boots with PWM as a module also, but DVFS only works sometimes, and making it built-in fixes the problem. Actually, it doesn't fix, it just hides the problem, which is likely a race or timeout happening during deferred probing.
Quoted 5 lines
did you check whether there's some other problem like some unused clock which is being disabled at that moment?
I've been hunting weird problems in the past where it turned out that changing kernel config bits changed the boot timing - that masked the original problem
Quoted 7 lines
Right, I would definitely prefer to not make this built-in without a lot more information to *why* this is needed. In figuring that out, we'll probably find the race/timeout that's the root cause.
Kevin
Kevin,
As per my understanding from the kernelci.org logs it seen that pwm-meson driver is requested more than once before it finally load the module.
Hi Martin,
I have tired your Martin's patch [1] and still the boot fails to move ahead with below logs.
[1] https://lore.kernel.org/patchwork/patch/1034186/
[ 1.543928] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed [ 1.550422] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [ 1.558702] hub 2-0:1.0: USB hub found [ 1.562131] hub 2-0:1.0: 1 port detected [ 1.566206] dwc3-meson-g12a ffe09000.usb: switching to Device Mode [ 1.573252] meson-gx-mmc ffe05000.sd: Got CD GPIO [ 1.607405] hctosys: unable to open rtc device (rtc0)
I have put some more prints in pwm-meson.c it fails to load the module as microsSD card is not completely initialized.
Here is what I have tried to enable sd_emmc_b node, but still it fails to initialize this driver..
- max-frequency = <50000000>;
+ sd-uhs-sdr12;
+ sd-uhs-sdr25;
+ sd-uhs-sdr50;
+ sd-uhs-ddr50;
+ max-frequency = <100000000>;
disable-wp;Below are the boot logs.
[ 1.729877] meson-gx-mmc ffe05000.sd: Anand mmc proble start1 [ 1.734658] meson-gx-mmc ffe05000.sd: Got CD GPIO [ 1.739237] meson-gx-mmc ffe05000.sd: Anand mmc proble start2 [ 1.744900] meson-gx-mmc ffe05000.sd: Anand mmc proble start3 [ 1.750594] meson-gx-mmc ffe05000.sd: Anand mmc proble start4 [ 1.756292] meson-gx-mmc ffe05000.sd: Anand mmc proble start5 [ 1.761987] meson-gx-mmc ffe05000.sd: Anand mmc proble start6 [ 1.767668] meson-gx-mmc ffe05000.sd: Anand mmc proble start7 [ 1.773356] meson-gx-mmc ffe05000.sd: Anand mmc proble start8 [ 1.779050] meson-gx-mmc ffe05000.sd: Anand mmc proble start9 [ 1.784748] meson-gx-mmc ffe05000.sd: Anand mmc proble start10 [ 1.790523] meson-gx-mmc ffe05000.sd: Anand mmc proble start11 [ 1.796578] meson-gx-mmc ffe05000.sd: Anand mmc proble start12 [ 1.802150] meson-gx-mmc ffe05000.sd: Anand mmc proble start13 [ 1.807980] meson-gx-mmc ffe05000.sd: Anand mmc proble start14 [ 1.813642] meson-gx-mmc ffe05000.sd: Anand mmc proble start15 [ 1.819416] meson-gx-mmc ffe05000.sd: Anand mmc proble start17 [ 1.825491] meson-gx-mmc ffe05000.sd: Anand mmc proble start18 [ 1.830984] meson-gx-mmc ffe05000.sd: Anand mmc proble start19 [ 1.862000] meson-gx-mmc ffe05000.sd: Anand mmc Final proble good to go [ 1.863323] pwm-regulator regulator-vddcpu-a: Anand : dutycycle_unit 100: dutycycle_range 100:0 [ 1.871617] pwm-regulator regulator-vddcpu-a: Failed to get PWM: -517 [ 1.878560] pwm-regulator regulator-vddcpu-b: Anand : dutycycle_unit 100: dutycycle_range 100:0 [ 1.886613] pwm-regulator regulator-vddcpu-b: Failed to get PWM: -517 [ 1.894094] pwm-regulator regulator-vddcpu-a: Anand : dutycycle_unit 100: dutycycle_range 100:0 [ 1.901771] pwm-regulator regulator-vddcpu-a: Failed to get PWM: -517 [ 1.909089] pwm-regulator regulator-vddcpu-b: Anand : dutycycle_unit 100: dutycycle_range 100:0 [ 1.916658] pwm-regulator regulator-vddcpu-b: Failed to get PWM: -517 [ 1.924147] hctosys: unable to open rtc device (rtc0)
sd_emmc_b probe function return success but still not able to progress further.
Best Regards
-Anand
Martin Blumenstingl
reviewerRe: [RFCv1 5/5] arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
Hi Anand,
Quoted 44 lines · Anand Moon
Hi Kevin / Martin,
Quoted 32 lines · Kevin Hilman
Quoted 17 lines · Martin Blumenstingl
On Mon, Oct 7, 2019 at 3:17 PM Anand Moon <[email protected]> wrote:
[...]arch/arm64/configs/defconfig CONFIG_MPL3115=m · line 777
Quoted 10 lines
arch/arm64/configs/defconfig +1
-1@@ -774,7 +774,7 @@ CONFIG_MPL3115=m CONFIG_PWM=y CONFIG_PWM_BCM2835=m CONFIG_PWM_CROS_EC=m -CONFIG_PWM_MESON=m +CONFIG_PWM_MESON=ysome time ago I submitted a similar patch for the 32-bit SoCs it turned that that pwm-meson can be built as module because the kernel will run without CPU DVFS as long as the clock and regulator drivers are returning -EPROBE_DEFER (-517)
On 64-bit SoCs, the kernel boots with PWM as a module also, but DVFS only works sometimes, and making it built-in fixes the problem. Actually, it doesn't fix, it just hides the problem, which is likely a race or timeout happening during deferred probing.
Quoted 5 lines
did you check whether there's some other problem like some unused clock which is being disabled at that moment?
I've been hunting weird problems in the past where it turned out that changing kernel config bits changed the boot timing - that masked the original problemQuoted 7 lines
Right, I would definitely prefer to not make this built-in without a lot more information to *why* this is needed. In figuring that out, we'll probably find the race/timeout that's the root cause.
Kevin
Quoted 6 lines
Kevin,
As per my understanding from the kernelci.org logs it seen that pwm-meson driver is requested more than once before it finally load the module.
my understanding is that:
- the PWM regulator driver is built in (=y)
- the Meson PWM controller driver is built as module (=m)
- during boot the PWM regulator node is found and it has a matching driver (built-in)
- the PWM regulator driver tries to find the PWM controller but cannot find it yet (and reports "Failed to get PWM: -517")
- (this repeats a few times)
- then the filesystem / initramfs is loaded where the modules are located
- now the Meson PWM controller driver is loaded
- the PWM regulator driver tries to find the PWM controller -> now it found it
Quoted 5 lines
Hi Martin,
I have tired your Martin's patch [1] and still the boot fails to move ahead with below logs.
[1] https://lore.kernel.org/patchwork/patch/1034186/
this patch only silences the "Failed to get PWM: -517" message Mark didn't apply it back then because without that message it would be harder to debug these issues
Quoted 11 lines
[ 1.543928] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed [ 1.550422] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [ 1.558702] hub 2-0:1.0: USB hub found [ 1.562131] hub 2-0:1.0: 1 port detected [ 1.566206] dwc3-meson-g12a ffe09000.usb: switching to Device Mode [ 1.573252] meson-gx-mmc ffe05000.sd: Got CD GPIO [ 1.607405] hctosys: unable to open rtc device (rtc0)I have put some more prints in
pwm-meson.cit fails to load the module as microsSD card is not completely initialized.
what makes you think that there's a problem with pwm-meson?
can you please share a boot log with the command line parameter "initcall_debug" [0]?
from Documentation/admin-guide/kernel-parameters.txt:
initcall_debug [KNL] Trace initcalls as they are executed. Useful for working out where the kernel is dying during startup.
you can also try the command line parameter "clk_ignore_unused" (it's just a gut feeling: maybe a "critical" clock is being disabled because it's not wired up correctly).
back when I was working out the CPU clock tree for the 32-bit SoCs I had a bad parent clock in one of the muxes which resulted in sporadic lockups if CPU DVFS was enabled.
you can try to disable CPU DVFS by dropping the OPP table and it's references from the .dtsi
Martin
Re: [RFCv1 5/5] arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
Hi Martin,
Thanks for your inputs.
Quoted 54 lines · Martin Blumenstingl
Hi Anand,
Quoted 44 lines · Anand Moon
Hi Kevin / Martin,
Quoted 32 lines · Kevin Hilman
Quoted 17 lines · Martin Blumenstingl
On Mon, Oct 7, 2019 at 3:17 PM Anand Moon <[email protected]> wrote:
[...]arch/arm64/configs/defconfig CONFIG_MPL3115=m · line 777
Quoted 10 lines
arch/arm64/configs/defconfig +1
-1@@ -774,7 +774,7 @@ CONFIG_MPL3115=m CONFIG_PWM=y CONFIG_PWM_BCM2835=m CONFIG_PWM_CROS_EC=m -CONFIG_PWM_MESON=m +CONFIG_PWM_MESON=ysome time ago I submitted a similar patch for the 32-bit SoCs it turned that that pwm-meson can be built as module because the kernel will run without CPU DVFS as long as the clock and regulator drivers are returning -EPROBE_DEFER (-517)
On 64-bit SoCs, the kernel boots with PWM as a module also, but DVFS only works sometimes, and making it built-in fixes the problem. Actually, it doesn't fix, it just hides the problem, which is likely a race or timeout happening during deferred probing.
Quoted 5 lines
did you check whether there's some other problem like some unused clock which is being disabled at that moment?
I've been hunting weird problems in the past where it turned out that changing kernel config bits changed the boot timing - that masked the original problemQuoted 7 lines
Right, I would definitely prefer to not make this built-in without a lot more information to *why* this is needed. In figuring that out, we'll probably find the race/timeout that's the root cause.
Kevin
Quoted 6 lines
Kevin,
As per my understanding from the kernelci.org logs it seen that pwm-meson driver is requested more than once before it finally load the module.
Quoted 12 lines
my understanding is that:
- the PWM regulator driver is built in (=y)
- the Meson PWM controller driver is built as module (=m)
- during boot the PWM regulator node is found and it has a matching driver (built-in)
- the PWM regulator driver tries to find the PWM controller but cannot find it yet (and reports "Failed to get PWM: -517")
- (this repeats a few times)
- then the filesystem / initramfs is loaded where the modules are located
- now the Meson PWM controller driver is loaded
- the PWM regulator driver tries to find the PWM controller -> now it found it
Thanks of this information.
At my end on archlinux I also tried to update my initramfs to add support for *pwm-meson* to but it did not work for me.
Quoted 20 lines
Quoted 5 lines
Hi Martin,
I have tired your Martin's patch [1] and still the boot fails to move ahead with below logs.
[1] https://lore.kernel.org/patchwork/patch/1034186/this patch only silences the "Failed to get PWM: -517" message Mark didn't apply it back then because without that message it would be harder to debug these issues
Quoted 11 lines
[ 1.543928] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed [ 1.550422] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [ 1.558702] hub 2-0:1.0: USB hub found [ 1.562131] hub 2-0:1.0: 1 port detected [ 1.566206] dwc3-meson-g12a ffe09000.usb: switching to Device Mode [ 1.573252] meson-gx-mmc ffe05000.sd: Got CD GPIO [ 1.607405] hctosys: unable to open rtc device (rtc0)I have put some more prints in
pwm-meson.cit fails to load the module as microsSD card is not completely initialized.
Quoted 9 lines
what makes you think that there's a problem with pwm-meson?
can you please share a boot log with the command line parameter "
initcall_debug" [0]?
fromDocumentation/admin-guide/kernel-parameters.txt:
initcall_debug[KNL] Trace initcalls as they are executed. Useful for working out where the kernel is dying during startup.
Well I have tied to add this command *initcall_debug* to kernel command prompt. Here is the console log, but I did not see any init kernel timer logs
Kernel command line: console=ttyAML0,115200n8 root=PARTUUID=45d7d61e-01 rw rootwait earlyprintk=serial,ttyAML0,115200 initcall_debug printk.time=y
[0] https://pastebin.com/eBgJrSKe
Quoted 4 lines
you can also try the command line parameter "
clk_ignore_unused" (it's just a gut feeling: maybe a "critical" clock is being disabled because it's not wired up correctly).
It look like some clk issue after I added the *clk_ignore_unused* to kernel command line
it booted further to login prompt and cpufreq DVFS seem to be loaded. So I could conclude this is clk issue.below is the boot log
Kernel command line: console=ttyAML0,115200n8 root=PARTUUID=45d7d61e-01 rw rootwait earlyprintk=serial,ttyAML0,115200 initcall_debug printk.time=y clk_ignore_unused
[1] https://pastebin.com/Nsk0wZQJ
Quoted 6 lines
back when I was working out the CPU clock tree for the 32-bit SoCs I had a bad parent clock in one of the muxes which resulted in sporadic lockups if CPU DVFS was enabled.
you can try to disable CPU DVFS by dropping the OPP table and it's references from the .dtsi
Yep yesterday my focus was to disable PWM feature and get boot up-to login prompt
But not I have to look into clk feature.
*Many thanks for your valuable inputs, I learned a lot of things.*
Quoted 5 lines
Martin
Best Regards
-Anand
Jerome Brunet
maintainerRe: [RFCv1 5/5] arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
Quoted 17 lines · Anand Moon
Kernel command line: console=ttyAML0,115200n8 root=PARTUUID=45d7d61e-01 rw rootwait earlyprintk=serial,ttyAML0,115200
initcall_debugprintk.time=y[0] https://pastebin.com/eBgJrSKe
Quoted 4 lines
you can also try the command line parameter "
clk_ignore_unused" (it's just a gut feeling: maybe a "critical" clock is being disabled because it's not wired up correctly).It look like some clk issue after I added the *clk_ignore_unused* to kernel command line
it booted further to login prompt and cpufreq DVFS seem to be loaded. So I could conclude this is clk issue.below is the boot log
Quoted 7 lines
Kernel command line: console=ttyAML0,115200n8 root=PARTUUID=45d7d61e-01 rw rootwait earlyprintk=serial,ttyAML0,115200
initcall_debugprintk.time=yclk_ignore_unused
Next step it to try narrow down the clock causing the issue. Remove clk_ignore_unused from the command line and add CLK_INGORE_UNUSED to the flag of some clocks your clock controller (g12a I think) until
The peripheral clock gates already have this flag (something we should fix someday) so don't bother looking there.
Most likely the source of the pwm is getting disabled between the late_init call and the probe of the PWM module. Since the pwm is already active (w/o a driver), gating the clock source shuts dowm the power to the cores.
Looking a the possible inputs in pwm driver, I'd bet on fdiv4.
Re: [RFCv1 5/5] arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
Hi Jerome / Neil / Martin,
Quoted 35 lines · Jerome Brunet
Quoted 17 lines · Anand Moon
Kernel command line: console=ttyAML0,115200n8 root=PARTUUID=45d7d61e-01 rw rootwait earlyprintk=serial,ttyAML0,115200
initcall_debugprintk.time=y[0] https://pastebin.com/eBgJrSKe
Quoted 4 lines
you can also try the command line parameter "
clk_ignore_unused" (it's just a gut feeling: maybe a "critical" clock is being disabled because it's not wired up correctly).It look like some clk issue after I added the *clk_ignore_unused* to kernel command line
it booted further to login prompt and cpufreq DVFS seem to be loaded. So I could conclude this is clk issue.below is the boot logQuoted 7 lines
Kernel command line: console=ttyAML0,115200n8 root=PARTUUID=45d7d61e-01 rw rootwait earlyprintk=serial,ttyAML0,115200
initcall_debugprintk.time=yclk_ignore_unusedNext step it to try narrow down the clock causing the issue. Remove
clk_ignore_unusedfrom the command line and addCLK_INGORE_UNUSEDto the flag of some clocks your clock controller (g12a I think) untilThe peripheral clock gates already have this flag (something we should fix someday) so don't bother looking there.
Quoted 7 lines
Most likely the source of the pwm is getting disabled between the
late_initcall and the probe of the PWM module. Since the pwm is already active (w/o a driver), gating the clock source shuts dowm the power to the cores.Looking a the possible inputs in pwm driver, I'd bet on fdiv4.
I had give this above steps a try but with little success. I am still looking into this much close.
Well I am not the expert in clk or bus configuration. but after looking into the datasheet of for clk configuration I found some bus are not configured correctly.
As per Amlogic's kernel S922X (Hardkernel)
below link share the bus controller.
looking in to current dts changes it looks bit wrong to me.
*As per 6.1 Memory Map*apb_efuse: bus@30000 --> apb_efuse: bus@ff630000
periphs: bus@34400 --> periphs: bus@ff634400
dmc: bus@38000 --> dmc: bus@ff638000
hiu: bus@3c000 --> hiu: bus@ff63c0000
Also the order of these is not correct.
Down the line in the datasheet some of the interrupt GIC bit are not mapped correctly for example.
*As per 6.9.2 Interrupt Control Source*
223 SD_EMMC_C
222 SD_EMMC_B
221 SD_EMMC_A
and so on.
Please share your thought if these changes are valid.
Best Regards
-Anand
Re: [RFCv1 5/5] arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
Quoted 58 lines · Anand Moon
Hi Jerome / Neil / Martin,
Quoted 35 lines · Jerome Brunet
Quoted 17 lines · Anand Moon
Kernel command line: console=ttyAML0,115200n8 root=PARTUUID=45d7d61e-01 rw rootwait earlyprintk=serial,ttyAML0,115200
initcall_debugprintk.time=y[0] https://pastebin.com/eBgJrSKe
Quoted 4 lines
you can also try the command line parameter "
clk_ignore_unused" (it's just a gut feeling: maybe a "critical" clock is being disabled because it's not wired up correctly).It look like some clk issue after I added the *clk_ignore_unused* to kernel command line
it booted further to login prompt and cpufreq DVFS seem to be loaded. So I could conclude this is clk issue.below is the boot logQuoted 7 lines
Kernel command line: console=ttyAML0,115200n8 root=PARTUUID=45d7d61e-01 rw rootwait earlyprintk=serial,ttyAML0,115200
initcall_debugprintk.time=yclk_ignore_unusedNext step it to try narrow down the clock causing the issue. Remove
clk_ignore_unusedfrom the command line and addCLK_INGORE_UNUSEDto the flag of some clocks your clock controller (g12a I think) untilThe peripheral clock gates already have this flag (something we should fix someday) so don't bother looking there.
Quoted 7 lines
Most likely the source of the pwm is getting disabled between the
late_initcall and the probe of the PWM module. Since the pwm is already active (w/o a driver), gating the clock source shuts dowm the power to the cores.Looking a the possible inputs in pwm driver, I'd bet on fdiv4.
I had give this above steps a try but with little success. I am still looking into this much close.
Well I am not the expert in clk or bus configuration. but after looking into the datasheet of for clk configuration I found some bus are not configured correctly.
As per Amlogic's kernel S922X (Hardkernel)
below link share the bus controller.
Quoted 7 lines
looking in to current dts changes it looks bit wrong to me.
*As per 6.1 Memory Map*
apb_efuse: bus@30000 -->apb_efuse: bus@ff630000
periphs: bus@34400 --> periphs: bus@ff634400
dmc: bus@38000 --> dmc: bus@ff638000
hiu: bus@3c000 --> hiu: bus@ff63c0000
If these was wrong, the drivers simply won't work, at all
Quoted 2 lines
Also the order of these is not correct.
The order is correct, actually
Quoted 8 lines
Down the line in the datasheet some of the interrupt GIC bit are not mapped correctly for example.
*As per 6.9.2 Interrupt Control Source*
223SD_EMMC_C
222SD_EMMC_B
221SD_EMMC_A
There is an offset between the doc and the actual GIC_SPI line, they start the datasheet numbers from the GIC_PPI numbers (+32).
Neil
Quoted 7 lines
and so on.
Please share your thought if these changes are valid.Best Regards
-Anand
Re: [RFCv1 5/5] arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
Hi Neil,
Quoted 79 lines · Neil Armstrong
Quoted 58 lines · Anand Moon
Hi Jerome / Neil / Martin,
Quoted 35 lines · Jerome Brunet
Quoted 17 lines · Anand Moon
Kernel command line: console=ttyAML0,115200n8 root=PARTUUID=45d7d61e-01 rw rootwait earlyprintk=serial,ttyAML0,115200
initcall_debugprintk.time=y[0] https://pastebin.com/eBgJrSKe
Quoted 4 lines
you can also try the command line parameter "
clk_ignore_unused" (it's just a gut feeling: maybe a "critical" clock is being disabled because it's not wired up correctly).It look like some clk issue after I added the *clk_ignore_unused* to kernel command line
it booted further to login prompt and cpufreq DVFS seem to be loaded. So I could conclude this is clk issue.below is the boot logQuoted 7 lines
Kernel command line: console=ttyAML0,115200n8 root=PARTUUID=45d7d61e-01 rw rootwait earlyprintk=serial,ttyAML0,115200
initcall_debugprintk.time=yclk_ignore_unusedNext step it to try narrow down the clock causing the issue. Remove
clk_ignore_unusedfrom the command line and addCLK_INGORE_UNUSEDto the flag of some clocks your clock controller (g12a I think) untilThe peripheral clock gates already have this flag (something we should fix someday) so don't bother looking there.
Quoted 7 lines
Most likely the source of the pwm is getting disabled between the
late_initcall and the probe of the PWM module. Since the pwm is already active (w/o a driver), gating the clock source shuts dowm the power to the cores.Looking a the possible inputs in pwm driver, I'd bet on fdiv4.
I had give this above steps a try but with little success. I am still looking into this much close.
Well I am not the expert in clk or bus configuration. but after looking into the datasheet of for clk configuration I found some bus are not configured correctly.
As per Amlogic's kernel S922X (Hardkernel)
below link share the bus controller.Quoted 7 lines
looking in to current dts changes it looks bit wrong to me.
*As per 6.1 Memory Map*
apb_efuse: bus@30000 -->apb_efuse: bus@ff630000
periphs: bus@34400 --> periphs: bus@ff634400
dmc: bus@38000 --> dmc: bus@ff638000
hiu: bus@3c000 --> hiu: bus@ff63c0000If these was wrong, the drivers simply won't work, at all
Quoted 2 lines
Also the order of these is not correct.
The order is correct, actually
Quoted 4 lines
Down the line in the datasheet some of the interrupt GIC bit are not mapped correctly for example.
Quoted 8 lines
Quoted 4 lines
*As per 6.9.2 Interrupt Control Source*
223SD_EMMC_C
222SD_EMMC_B
221SD_EMMC_AThere is an offset between the doc and the actual
GIC_SPIline, they start the datasheet numbers from theGIC_PPInumbers (+32).
Ok. Thanks.
Quoted 2 lines
Neil
Thanks for answering my query.
Best Regards
-Anand
Martin Blumenstingl
reviewerRe: [RFCv1 5/5] arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
In reply to Anand MoonHi Anand,
On Fri, Oct 18, 2019 at 4:04 PM Anand Moon <[email protected]> wrote:
[...]
Quoted 12 lines
Quoted 12 lines
Next step it to try narrow down the clock causing the issue. Remove
clk_ignore_unusedfrom the command line and addCLK_INGORE_UNUSEDto the flag of some clocks your clock controller (g12a I think) untilThe peripheral clock gates already have this flag (something we should fix someday) so don't bother looking there.
Most likely the source of the pwm is getting disabled between the
late_initcall and the probe of the PWM module. Since the pwm is already active (w/o a driver), gating the clock source shuts dowm the power to the cores.
Quoted 5 lines
Quoted 2 lines
Looking a the possible inputs in pwm driver, I'd bet on fdiv4.
I had give this above steps a try but with little success. I am still looking into this much close.
it's not clear to me if you have only tested with the PWM and/or FCLK_DIV4 clocks. can you please describe what you have tested so far?
for reference - my way of debugging this in the past was:
1. add some printks to clk_disable_unused_subtree (right after the clk_core_is_enabled check) to see which clocks are being disabled
2. add CLK_IGNORE_UNUSED or CLK_IS_CRITICAL to the clocks which are being disabled based on the information from step #1
3. (at some point I had a working kernel with lots of clocks with CLK_IGNORE_UNUSED/CLK_IS_CRITICAL)
4. start dropping the CLK_IGNORE_UNUSED/CLK_IS_CRITICAL flags again until you have traced it down to the clocks that are the actual issue (so far I always had only one clock which caused issues, but it may be multiple)
5. investigate (and/or ask on the mailing list, Amlogic developers are reading the mails here as well) for the few clocks from step #4
Quoted 3 lines
Well I am not the expert in clk or bus configuration. but after looking into the datasheet of for clk configuration I found some bus are not configured correctly.
did you find any reason which indicates that the problem is related to a bus? the issues I had were due to clocks not being assigned to their consumers in .dts - that can be anything (from a bus to something different).
Martin
Re: [RFCv1 5/5] arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
Hi Martin,
Quoted 17 lines · Martin Blumenstingl
Hi Anand,
On Fri, Oct 18, 2019 at 4:04 PM Anand Moon <[email protected]> wrote:
[...]Quoted 12 lines
Quoted 12 lines
Next step it to try narrow down the clock causing the issue. Remove
clk_ignore_unusedfrom the command line and addCLK_INGORE_UNUSEDto the flag of some clocks your clock controller (g12a I think) untilThe peripheral clock gates already have this flag (something we should fix someday) so don't bother looking there.
Most likely the source of the pwm is getting disabled between the
late_initcall and the probe of the PWM module. Since the pwm is already active (w/o a driver), gating the clock source shuts dowm the power to the cores.
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
Looking a the possible inputs in pwm driver, I'd bet on fdiv4.
I had give this above steps a try but with little success. I am still looking into this much close.
it's not clear to me if you have only tested with the PWM and/or
FCLK_DIV4clocks. can you please describe what you have tested so far?
Sorry for delayed response.
I had just looked into clk related to SD_EMMC_A/B/C, with adding CLK_IGNORE/CRITICAL.
Also looked into clk_summary for eMMC and microSD card, to identify the root cause, but I failed to move ahead.
Quoted 5 lines
for reference - my way of debugging this in the past was:
1. add some printks toclk_disable_unused_subtree(right after theclk_core_is_enabledcheck) to see which clocks are being disabled
2. addCLK_IGNORE_UNUSEDorCLK_IS_CRITICALto the clocks which are being disabled based on the information from step #1
Quoted 9 lines
3. (at some point I had a working kernel with lots of clocks with CLK_IGNORE_UNUSED/CLK_IS_CRITICAL)
4. start dropping the CLK_IGNORE_UNUSED/CLK_IS_CRITICAL flags again until you have traced it down to the clocks that are the actual issue (so far I always had only one clock which caused issues, but it may be multiple)
5. investigate (and/or ask on the mailing list, Amlogic developers are reading the mails here as well) for the few clocks from step #4
Thanks for you valuable suggestion. I have your patch to debug this
[0] https://patchwork.kernel.org/patch/9725921/mbox/
So from the fist step I could identify that all the clk were getting closed after some core cpu clk was failing. Here is the log.
step1: [1] https://pastebin.com/p13F9HGG
so I marked these clk as CLK_IGNORE_UNUSED and finally I made it to boot using microSD card.
After this just I converted these CLK to CLK_IS_CRITICAL as mostly these are used the CPU clk for now. Here is boot log successful for as of now.
Finally: [2] https://pastebin.com/qB6pMyGQ
I know clk maintainer are against marking flags as *CLK_IS_CRITICAL* But this is just the step to move ahead.
Attach is my local clk and dts patch.Just for testing.
[3] clk_critical.patch
Plz share your thought on this.
Quoted 8 lines
Quoted 3 lines
Well I am not the expert in clk or bus configuration. but after looking into the datasheet of for clk configuration I found some bus are not configured correctly.
did you find any reason which indicates that the problem is related to a bus? the issues I had were due to clocks not being assigned to their consumers in .dts - that can be anything (from a bus to something different).
Yes I feel each core bus should be independent
as each clk PLL controls these bus.
for example datasheet: *6-5 Clock Connections*
What I feel currently missing with bus are
clock gating (enable/disable of features).
clock-controller
reset-controller
Here is the current overview of bus topology
using latest u-boot (dm tree).
[4] https://pastebin.com/MZ25bgiP
Bet Regards
-Anand
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +5 -1
@@ -54,6 +54,9 @@ gpio = <&gpio_ao GPIOAO_8 GPIO_ACTIVE_HIGH>; enable-active-high; regulator-always-on; + + /* FC8731-09VF05NRR */ + vin-supply = <&vddao_3v3>; }; tf_io: gpio-regulator-tf_io {
@@ -68,6 +71,8 @@ states = <3300000 0>, <1800000 1>; + /* RT9179GB */ + vin-supply = <&vcc_5v>; }; flash_1v8: regulator-flash_1v8 {
@@ -429,7 +434,6 @@ cd-gpios = <&gpio GPIOC_6 GPIO_ACTIVE_LOW>; vmmc-supply = <&tflash_vdd>; vqmmc-supply = <&tf_io>; - }; /* eMMC */
drivers/clk/meson/g12a.c +44 -4
186 lines not on this page · raw message
Re: [RFCv1 5/5] arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
Hi Anand,
Quoted 62 lines · Anand Moon
Hi Martin,
Quoted 17 lines · Martin Blumenstingl
Hi Anand,
On Fri, Oct 18, 2019 at 4:04 PM Anand Moon <[email protected]> wrote:
[...]Quoted 12 lines
Quoted 12 lines
Next step it to try narrow down the clock causing the issue. Remove
clk_ignore_unusedfrom the command line and addCLK_INGORE_UNUSEDto the flag of some clocks your clock controller (g12a I think) untilThe peripheral clock gates already have this flag (something we should fix someday) so don't bother looking there.
Most likely the source of the pwm is getting disabled between the
late_initcall and the probe of the PWM module. Since the pwm is already active (w/o a driver), gating the clock source shuts dowm the power to the cores.Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
Looking a the possible inputs in pwm driver, I'd bet on fdiv4.
I had give this above steps a try but with little success. I am still looking into this much close.
it's not clear to me if you have only tested with the PWM and/or
FCLK_DIV4clocks. can you please describe what you have tested so far?Sorry for delayed response.
I had just looked into clk related to SD_EMMC_A/B/C, with adding CLK_IGNORE/CRITICAL.
Also looked intoclk_summaryfor eMMC and microSD card, to identify the root cause, but I failed to move ahead.Quoted 5 lines
for reference - my way of debugging this in the past was:
1. add some printks toclk_disable_unused_subtree(right after theclk_core_is_enabledcheck) to see which clocks are being disabled
2. addCLK_IGNORE_UNUSEDorCLK_IS_CRITICALto the clocks which are being disabled based on the information from step #1Quoted 9 lines
3. (at some point I had a working kernel with lots of clocks with CLK_IGNORE_UNUSED/CLK_IS_CRITICAL)
4. start dropping the CLK_IGNORE_UNUSED/CLK_IS_CRITICAL flags again until you have traced it down to the clocks that are the actual issue (so far I always had only one clock which caused issues, but it may be multiple)
5. investigate (and/or ask on the mailing list, Amlogic developers are reading the mails here as well) for the few clocks from step #4Thanks for you valuable suggestion. I have your patch to debug this
[0] https://patchwork.kernel.org/patch/9725921/mbox/So from the fist step I could identify that all the clk were getting closed after some core cpu clk was failing. Here is the log.
step1: [1] https://pastebin.com/p13F9HGG
so I marked these clk as
CLK_IGNORE_UNUSEDand finally I made it to boot using microSD card.
Quoted 8 lines
After this just I converted these CLK to
CLK_IS_CRITICALas mostly these are used the CPU clk for now. Here is boot log successful for as of now.Finally: [2] https://pastebin.com/qB6pMyGQ
I know clk maintainer are against marking flags as *CLK_IS_CRITICAL* But this is just the step to move ahead.
Thanks for the extensive debug.
Quoted 3 lines
Attach is my local clk and dts patch.Just for testing.
[3] clk_critical.patch
Could you test with only the following changes:
drivers/clk/meson/g12a.c +2 -1
@@ -298,6 +298,7 @@ static struct clk_regmap g12a_fclk_div2 = { &g12a_fclk_div2_div.hw }, .num_parents = 1, + .flags = CLK_IS_CRITICAL, }, };
@@ -672,7 +673,7 @@ static struct clk_regmap g12b_cpub_clk = { &g12a_sys_pll.hw }, .num_parents = 2, - .flags = CLK_SET_RATE_PARENT, + .flags = CLK_SET_RATE_PARENT | CLK_IS_CRITICAL, }, };
Quoted 30 lines
Plz share your thought on this.
Quoted 8 lines
Quoted 3 lines
Well I am not the expert in clk or bus configuration. but after looking into the datasheet of for clk configuration I found some bus are not configured correctly.
did you find any reason which indicates that the problem is related to a bus? the issues I had were due to clocks not being assigned to their consumers in .dts - that can be anything (from a bus to something different).
Yes I feel each core bus should be independent
as each clk PLL controls these bus.for example datasheet: *6-5 Clock Connections*
What I feel currently missing with bus are
clock gating (enable/disable of features).
clock-controller
reset-controllerHere is the current overview of bus topology
using latest u-boot (dm tree).[4] https://pastebin.com/MZ25bgiP
Bet Regards
-Anand
Re: [RFCv1 5/5] arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
Hi Neil,
Quoted 96 lines · Neil Armstrong
Hi Anand,
Quoted 62 lines · Anand Moon
Hi Martin,
Quoted 17 lines · Martin Blumenstingl
Hi Anand,
On Fri, Oct 18, 2019 at 4:04 PM Anand Moon <[email protected]> wrote:
[...]Quoted 12 lines
Quoted 12 lines
Next step it to try narrow down the clock causing the issue. Remove
clk_ignore_unusedfrom the command line and addCLK_INGORE_UNUSEDto the flag of some clocks your clock controller (g12a I think) untilThe peripheral clock gates already have this flag (something we should fix someday) so don't bother looking there.
Most likely the source of the pwm is getting disabled between the
late_initcall and the probe of the PWM module. Since the pwm is already active (w/o a driver), gating the clock source shuts dowm the power to the cores.Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
Looking a the possible inputs in pwm driver, I'd bet on fdiv4.
I had give this above steps a try but with little success. I am still looking into this much close.
it's not clear to me if you have only tested with the PWM and/or
FCLK_DIV4clocks. can you please describe what you have tested so far?Sorry for delayed response.
I had just looked into clk related to SD_EMMC_A/B/C, with adding CLK_IGNORE/CRITICAL.
Also looked intoclk_summaryfor eMMC and microSD card, to identify the root cause, but I failed to move ahead.Quoted 5 lines
for reference - my way of debugging this in the past was:
1. add some printks toclk_disable_unused_subtree(right after theclk_core_is_enabledcheck) to see which clocks are being disabled
2. addCLK_IGNORE_UNUSEDorCLK_IS_CRITICALto the clocks which are being disabled based on the information from step #1Quoted 9 lines
3. (at some point I had a working kernel with lots of clocks with CLK_IGNORE_UNUSED/CLK_IS_CRITICAL)
4. start dropping the CLK_IGNORE_UNUSED/CLK_IS_CRITICAL flags again until you have traced it down to the clocks that are the actual issue (so far I always had only one clock which caused issues, but it may be multiple)
5. investigate (and/or ask on the mailing list, Amlogic developers are reading the mails here as well) for the few clocks from step #4Thanks for you valuable suggestion. I have your patch to debug this
[0] https://patchwork.kernel.org/patch/9725921/mbox/So from the fist step I could identify that all the clk were getting closed after some core cpu clk was failing. Here is the log.
step1: [1] https://pastebin.com/p13F9HGG
so I marked these clk as
CLK_IGNORE_UNUSEDand finally I made it to boot using microSD card.Quoted 8 lines
After this just I converted these CLK to
CLK_IS_CRITICALas mostly these are used the CPU clk for now. Here is boot log successful for as of now.Finally: [2] https://pastebin.com/qB6pMyGQ
I know clk maintainer are against marking flags as *CLK_IS_CRITICAL* But this is just the step to move ahead.
Thanks for the extensive debug.
Quoted 3 lines
Attach is my local clk and dts patch.Just for testing.
[3] clk_critical.patchCould you test with only the following changes:
drivers/clk/meson/g12a.c +1
-0@@ -298,6 +298,7 @@ static struct clk_regmap g12a_fclk_div2 = { &g12a_fclk_div2_div.hw }, .num_parents = 1, + .flags = CLK_IS_CRITICAL, }, };
drivers/clk/meson/g12a.c static struct clk_regmap g12b_cpub_clk = { · line 679
Quoted 8 lines
drivers/clk/meson/g12a.c +1
-1@@ -672,7 +673,7 @@ static struct clk_regmap g12b_cpub_clk = { &g12a_sys_pll.hw }, .num_parents = 2, - .flags = CLK_SET_RATE_PARENT, + .flags = CLK_SET_RATE_PARENT | CLK_IS_CRITICAL, }, };
Yes these changes work at my end,
I want to narrow down my changes, this looks pretty good.
Best Regards
-Anand
Anand Moon
Tested-byRe: [RFCv1 5/5] arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
Hi Neil,
Quoted 99 lines · Anand Moon
Hi Neil,
Quoted 95 lines · Neil Armstrong
Hi Anand,
Quoted 62 lines · Anand Moon
Hi Martin,
Quoted 17 lines · Martin Blumenstingl
Hi Anand,
On Fri, Oct 18, 2019 at 4:04 PM Anand Moon <[email protected]> wrote:
[...]Quoted 12 lines
Quoted 12 lines
Next step it to try narrow down the clock causing the issue. Remove
clk_ignore_unusedfrom the command line and addCLK_INGORE_UNUSEDto the flag of some clocks your clock controller (g12a I think) untilThe peripheral clock gates already have this flag (something we should fix someday) so don't bother looking there.
Most likely the source of the pwm is getting disabled between the
late_initcall and the probe of the PWM module. Since the pwm is already active (w/o a driver), gating the clock source shuts dowm the power to the cores.Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
Looking a the possible inputs in pwm driver, I'd bet on fdiv4.
I had give this above steps a try but with little success. I am still looking into this much close.
it's not clear to me if you have only tested with the PWM and/or
FCLK_DIV4clocks. can you please describe what you have tested so far?Sorry for delayed response.
I had just looked into clk related to SD_EMMC_A/B/C, with adding CLK_IGNORE/CRITICAL.
Also looked intoclk_summaryfor eMMC and microSD card, to identify the root cause, but I failed to move ahead.Quoted 5 lines
for reference - my way of debugging this in the past was:
1. add some printks toclk_disable_unused_subtree(right after theclk_core_is_enabledcheck) to see which clocks are being disabled
2. addCLK_IGNORE_UNUSEDorCLK_IS_CRITICALto the clocks which are being disabled based on the information from step #1Quoted 9 lines
3. (at some point I had a working kernel with lots of clocks with CLK_IGNORE_UNUSED/CLK_IS_CRITICAL)
4. start dropping the CLK_IGNORE_UNUSED/CLK_IS_CRITICAL flags again until you have traced it down to the clocks that are the actual issue (so far I always had only one clock which caused issues, but it may be multiple)
5. investigate (and/or ask on the mailing list, Amlogic developers are reading the mails here as well) for the few clocks from step #4Thanks for you valuable suggestion. I have your patch to debug this
[0] https://patchwork.kernel.org/patch/9725921/mbox/So from the fist step I could identify that all the clk were getting closed after some core cpu clk was failing. Here is the log.
step1: [1] https://pastebin.com/p13F9HGG
so I marked these clk as
CLK_IGNORE_UNUSEDand finally I made it to boot using microSD card.Quoted 8 lines
After this just I converted these CLK to
CLK_IS_CRITICALas mostly these are used the CPU clk for now. Here is boot log successful for as of now.Finally: [2] https://pastebin.com/qB6pMyGQ
I know clk maintainer are against marking flags as *CLK_IS_CRITICAL* But this is just the step to move ahead.
Thanks for the extensive debug.
Quoted 3 lines
Attach is my local clk and dts patch.Just for testing.
[3] clk_critical.patchCould you test with only the following changes:
drivers/clk/meson/g12a.c +1
-0@@ -298,6 +298,7 @@ static struct clk_regmap g12a_fclk_div2 = { &g12a_fclk_div2_div.hw }, .num_parents = 1, + .flags = CLK_IS_CRITICAL, }, };
Quoted 10 lines
drivers/clk/meson/g12a.c static struct clk_regmap g12b_cpub_clk = { · line 679
Quoted 9 lines
drivers/clk/meson/g12a.c +1
-1@@ -672,7 +673,7 @@ static struct clk_regmap g12b_cpub_clk = { &g12a_sys_pll.hw }, .num_parents = 2, - .flags = CLK_SET_RATE_PARENT, + .flags = CLK_SET_RATE_PARENT | CLK_IS_CRITICAL, }, };
I am blocked with my eMMC is not working with latest u-boot so that I could not verify that nothing break with this changes.
Could you send this patch upstream with adding my.
Best Regards
-Anand
Martin Blumenstingl
reviewerRe: [RFCv1 5/5] arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
In reply to Anand MoonHi Anand,
Quoted 30 lines · Anand Moon
Hi Martin,
Quoted 17 lines · Martin Blumenstingl
Hi Anand,
On Fri, Oct 18, 2019 at 4:04 PM Anand Moon <[email protected]> wrote:
[...]Quoted 12 lines
Quoted 12 lines
Next step it to try narrow down the clock causing the issue. Remove
clk_ignore_unusedfrom the command line and addCLK_INGORE_UNUSEDto the flag of some clocks your clock controller (g12a I think) untilThe peripheral clock gates already have this flag (something we should fix someday) so don't bother looking there.
Most likely the source of the pwm is getting disabled between the
late_initcall and the probe of the PWM module. Since the pwm is already active (w/o a driver), gating the clock source shuts dowm the power to the cores.Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
Looking a the possible inputs in pwm driver, I'd bet on fdiv4.
I had give this above steps a try but with little success. I am still looking into this much close.
it's not clear to me if you have only tested with the PWM and/or
FCLK_DIV4clocks. can you please describe what you have tested so far?
Quoted 6 lines
Sorry for delayed response.
I had just looked into clk related to SD_EMMC_A/B/C, with adding CLK_IGNORE/CRITICAL.
Also looked intoclk_summaryfor eMMC and microSD card, to identify the root cause, but I failed to move ahead.
I learned to be aware of the decisions that I make when finding a bug somewhere instead of following the initial problem that I see I ask myself "is there any proof that this initial problem is the actual root cause". I can then make the decision to do some experiments to rule out a problem - until I come to a point where I ask myself again "am I still going in the right direction - how does this bring me to the root cause of the problem"
unfortunately that's harder than it seems - but it keeps me from spending time going in the wrong direction
Quoted 18 lines
Quoted 5 lines
for reference - my way of debugging this in the past was:
1. add some printks toclk_disable_unused_subtree(right after theclk_core_is_enabledcheck) to see which clocks are being disabled
2. addCLK_IGNORE_UNUSEDorCLK_IS_CRITICALto the clocks which are being disabled based on the information from step #1Quoted 9 lines
3. (at some point I had a working kernel with lots of clocks with CLK_IGNORE_UNUSED/CLK_IS_CRITICAL)
4. start dropping the CLK_IGNORE_UNUSED/CLK_IS_CRITICAL flags again until you have traced it down to the clocks that are the actual issue (so far I always had only one clock which caused issues, but it may be multiple)
5. investigate (and/or ask on the mailing list, Amlogic developers are reading the mails here as well) for the few clocks from step #4Thanks for you valuable suggestion. I have your patch to debug this
[0] https://patchwork.kernel.org/patch/9725921/mbox/
Quoted 7 lines
So from the fist step I could identify that all the clk were getting closed after some core cpu clk was failing. Here is the log.
step1: [1] https://pastebin.com/p13F9HGG
so I marked these clk as
CLK_IGNORE_UNUSEDand finally I made it to boot using microSD card.
nice, congrats for finding this!
Quoted 6 lines
After this just I converted these CLK to
CLK_IS_CRITICALas mostly these are used the CPU clk for now. Here is boot log successful for as of now.Finally: [2] https://pastebin.com/qB6pMyGQ
Quoted 7 lines
I know clk maintainer are against marking flags as *CLK_IS_CRITICAL* But this is just the step to move ahead.
Attach is my local clk and dts patch.Just for testing.
[3] clk_critical.patchPlz share your thought on this.
interesting, the clock driver for the 32-bit SoCs (driver/clk/meson/meson8b.c) sets CLK_IS_CRITICAL for meson8b_cpu_clk. you have something similar in your patch for the G12A/B CPU clocks I guess that also explains why changing CONFIG_PWM_MESON from =m to =y "fixes" it:
- as long as the PWM driver is not loaded the VDDCPU regulator does not probe either
- this goes on for the initial boot process
- now the PWM driver is still not loaded and the common clock framework tries to disable the unused clocks
- it disables the CPU clock and the system now stops working
- (only later it would load the PWM driver and allow the cpufreq subsystem to come up)
with CONFIG_PWM_MESON=y you get:
- PWM driver is built-in so the VDDCPU regulator shows up
- the cpufreq subsystem comes up and enables the clock (in reality it only increments the refcount because the clock is already enabled)
- the common clock framework tries to disable the unused clocks - it doesn't disable the CPU clock this time because it's used (according to the ref count/enable count)
- ...
Martin
Martin Blumenstingl
reviewerRe: [RFCv1 5/5] arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
In reply to Anand MoonHi Anand,
On Wed, Oct 9, 2019 at 10:49 AM Anand Moon <[email protected]> wrote:
[...]
Quoted 10 lines
Quoted 7 lines
can you please share a boot log with the command line parameter "
initcall_debug" [0]?
fromDocumentation/admin-guide/kernel-parameters.txt:
initcall_debug[KNL] Trace initcalls as they are executed. Useful for working out where the kernel is dying during startup.Well I have tied to add this command *initcall_debug* to kernel command prompt. Here is the console log, but I did not see any init kernel timer logs
I don't remember from the top of my head if any additional Kconfig setting is needed
Quoted 11 lines
Kernel command line: console=ttyAML0,115200n8 root=PARTUUID=45d7d61e-01 rw rootwait earlyprintk=serial,ttyAML0,115200
initcall_debugprintk.time=y[0] https://pastebin.com/eBgJrSKe
Quoted 4 lines
you can also try the command line parameter "
clk_ignore_unused" (it's just a gut feeling: maybe a "critical" clock is being disabled because it's not wired up correctly).
Quoted 4 lines
It look like some clk issue after I added the *clk_ignore_unused* to kernel command line
it booted further to login prompt and cpufreq DVFS seem to be loaded. So I could conclude this is clk issue.below is the boot log
interesting - as Jerome suggested: the next step is to find out which clock is causing problems
last time I checked there was no debug print in the code which disables unused clocks so I had to add that myself
Quoted 14 lines
Kernel command line: console=ttyAML0,115200n8 root=PARTUUID=45d7d61e-01 rw rootwait earlyprintk=serial,ttyAML0,115200
initcall_debugprintk.time=yclk_ignore_unused[1] https://pastebin.com/Nsk0wZQJ
Quoted 6 lines
back when I was working out the CPU clock tree for the 32-bit SoCs I had a bad parent clock in one of the muxes which resulted in sporadic lockups if CPU DVFS was enabled.
you can try to disable CPU DVFS by dropping the OPP table and it's references from the .dtsi
Quoted 5 lines
Yep yesterday my focus was to disable PWM feature and get boot up-to login prompt
But not I have to look into clk feature.*Many thanks for your valuable inputs, I learned a lot of things.*
you're welcome :-)
Martin
Re: [RFCv1 5/5] arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y
In reply to Martin BlumenstinglHi Martin.
Quoted 18 lines · Martin Blumenstingl
On Mon, Oct 7, 2019 at 3:17 PM Anand Moon <[email protected]> wrote:
[...]arch/arm64/configs/defconfig CONFIG_MPL3115=m · line 777
Quoted 10 lines
arch/arm64/configs/defconfig +1
-1@@ -774,7 +774,7 @@ CONFIG_MPL3115=m CONFIG_PWM=y CONFIG_PWM_BCM2835=m CONFIG_PWM_CROS_EC=m -CONFIG_PWM_MESON=m +CONFIG_PWM_MESON=ysome time ago I submitted a similar patch for the 32-bit SoCs it turned that that pwm-meson can be built as module because the kernel will run without CPU DVFS as long as the clock and regulator drivers are returning -EPROBE_DEFER (-517)
Quoted 5 lines
did you check whether there's some other problem like some unused clock which is being disabled at that moment?
I've been hunting weird problems in the past where it turned out that changing kernel config bits changed the boot timing - that masked the original problem
OK.
Quoted 3 lines
Martin
Sorry for linking this two separate issue PWM failed and microSD detect failed. Thanks for the input, I will check if you patch help, I will try to investigate more why it fails at my end.
Best Regards
-Anand