On 10/21/21 4:58 PM, Tony Lindgren wrote:
>> Could it be possible the "secure_32k_fck" clock has some system hanging
>> issue on my beagle? How I understand from e428e250fde6 ("ARM: dts:
>> Configure system timers for omap3") that "secure_32k_fck" is not
>> referenced explicitly but your patch here does.
>
> Yes seems like there may be some extra issue on the omap3-beagle
> boards. Seeing the earlycon output would be good to see.
>
Here are the last lines with your earlier patch and patch below applied
(my tested-by below):
...
[ 0.000000] IRQ: Found an INTC at 0x(ptrval) (revision 4.0) with 96
interrupts
[ 0.000000] random: get_random_bytes called from
start_kernel+0x464/0x6c4 with crng_init=0
[ 0.000000] Clocking rate (Crystal/Core/MPU): 26.0/332/600 MHz
[ 0.000000] OMAP clocksource: 32k_counter at 32768 Hz
[ 0.000000] clocksource: 32k_counter: mask: 0xffffffff max_cycles:
0xffffffff, max_idle_ns: 58327039986419 ns
[ 0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps
every 65535999984741ns
[ 0.014617] TI gptimer clocksource: always-on
/ocp@68000000/target-module@48304000
[ 0.022583] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps
every 65535999984741ns
[ 0.032073] clocksource: dmtimer: mask: 0xffffffff max_cycles:
0xffffffff, max_idle_ns: 58327039986419 ns
[ 0.044372] Console: colour dummy device 80x30
> Subject: [PATCH] ARM: dts: Add missing stdout-path for omap3-beagle
> variants
>
> This allows seeing early serial console output as long as the kernel
> config has CONFIG_SERIAL_EARLYCON=y, and the kernel command line has
> earlycon.
>
> Signed-off-by: Tony Lindgren <tony@xxxxxxxxxxx>
You may add to this patch:
Tested-by: Jarkko Nikula <jarkko.nikula@xxxxxxxxxx>
