On 9/14/26 22:34, Marek Vasut wrote:
> On 9/14/26 8:45 AM, Patrice CHOTARD wrote:
>
> Hello Patrice,
>
>>>> schedule() execution doesn't takes 70ms.
>>>> Moving schedule() from main loop to same level that ctrlc(), it allows to
>>>> call ctrlc() every ~70ms.
>>> In the current state, the ctrlc() is called every ... how many ... ms ?
>>
>> Currently ctrlc() is called every 700ms
>>
>>>
>>> How come this trips the watchdog timeout ? What is the watchdog timeout
>>> delay set to in your case ?
>>
>> In our case, watchdog is set to 32 seconds on STM32MP157c-DK2.
>>
>> For information, this patch is superseeded by
>>
>> https://patchwork.ozlabs.org/project/uboot/patch/20260817-move_schedule_inside_sleep_thread-v1-2-0023194e8...@foss.st.com/
> Let me ask a different question -- is the problem that this is trying to
> solve the responsiveness of ctrl-c , or is the problem that this trips the
> WDT ?
>
> If the later, how come 700ms cycle trips 32 second timeout WDT ?
>
> (I'm sorry, I feel like I must be missing something obvious here?)
Hi Marek
The goal of this patch is only to solve the responsiveness of CTRL-C.
Patrice
