Hi Miquel
On 15/04/25 13:45, Miquel Raynal wrote:
> Hello,
>
> Thanks for the report.
>
>>>>>> Neha bisected it down to 197376fbf300e92afa0a1583815d9c9eb52d613a commit
>>>>>> which is this patch.
>>>>>
>>>>> And assuming it's the same failure I got reported this morning by one of
>>>>> my coworkers, we just get:
>>>>> U-Boot SPL 2025.04-01050-ga40fc5afaec0 (Apr 14 2025 - 07:31:32 +0000)
>>>>> SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.7--v09.02.07 (Kool Koala)')
>>>
>>> This is not the failure I am seeing, we hang before console comes up so
>>> no prints. Looks like the different failure signature is due to TIFS
>>> (SYSFW) firmware being different (v9.2.7 vs. 11.0.4)
>>
>> To me it was failing freezing just after this
>>
>> U-Boot SPL 2025.04-01076-g739ad58dbee8 (Apr 14 2025 - 17:23:46 +0200)
>> SYSFW ABI: 4.0 (firmware rev 0x000b '11.0.7--v11.00.07 (Fancy Rat)')
>>
>> and, with commit 197376fbf300 ("power-domain: Add refcounting") reverted
>> the issue is fixed and I get to the U-Boot command line.
>
> Francesco, are you also testing on K3 platforms?
>
Yes he would be, since the firmware print is K3 firmware.
> Can one of you boot with the patch below applied? It should partially
> revert the commit to the ancient behaviour, while adding more debug
> traces (please enable the debug logs as well). This should clarify
> which one of the 3 different path is likely failing. It should also help
> identify who's the user that fails to enable/disable its own power
> domain. I will need to know what board/SoC was used for the test, so I
> can look the relevant driver up.
Booted on j784s4_evm
https://gist.github.com/nehamalcom/b09687a523bec89f9df3537fdd99b6f3
Currently debugging on my build where I hang in console_init itself, I
think the path for failure is different here, will confirm.
>
> Thanks for your help,
> Miquèl
>
> ---
>
--
Thanking You
Neha Malcom Francis
