Hi
On 9/21/21 10:00 AM, Tony Lindgren wrote:
> * Jarkko Nikula <jarkko.nikula@xxxxxxxxxx> [210920 16:35]:
>> On 9/20/21 4:34 PM, Tony Lindgren wrote:
>>> The patch below should take us back to the earlier configuration,
>>> can you please give it a try?
>>>
>> I double checked and unfortunate it doesn't boot at all or give any
>> output when patch is applied:
>
> Hmm I tested it with copying the beagle timer configuration to omap3.dtsi
> and things worked for me. If you can, please try adding
> CONFIG_SERIAL_EARLYCON=y and then also add "debug earlyprintk" to kernel
> command line. It might show something that I'm not able to reproduce.
> Maybe there is a bootloader dependency or something like that.
>
As discussed offline recently I triple checked your first patch in this
thread on top of v5.15-rc6 and using omap2plus_defconfig (has
CONFIG_SERIAL_EARLYCON=y) and still I'm not able to get any output with
earlyprintk.
My kernel command line included "console=ttyO2,115200n8 debug
earlyprintk=ttyO2,115200n8". Plain v5.15-rc6 boots.
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.
Jarkko
