Re: [PATCH v2] remoteproc: k3-r5: Delay notification of wakeup event

2024-09-04 Thread Beleswar Prasad Padhi
On 03-09-2024 20:02, Mathieu Poirier wrote: On Tue, 3 Sept 2024 at 04:15, Beleswar Prasad Padhi wrote: Hi Mathieu, On 20-08-2024 16:20, Beleswar Padhi wrote: From: Udit Kumar Few times, core1 was scheduled to boot first before core0, which leads to error: 'k3_r5_rproc_start: can not star

Re: [PATCH v2] remoteproc: k3-r5: Delay notification of wakeup event

2024-09-03 Thread Mathieu Poirier
On Tue, 3 Sept 2024 at 04:15, Beleswar Prasad Padhi wrote: > > Hi Mathieu, > > On 20-08-2024 16:20, Beleswar Padhi wrote: > > From: Udit Kumar > > > > Few times, core1 was scheduled to boot first before core0, which leads > > to error: > > > > 'k3_r5_rproc_start: can not start core 1 before core

Re: [PATCH v2] remoteproc: k3-r5: Delay notification of wakeup event

2024-09-03 Thread Beleswar Prasad Padhi
Hi Mathieu, On 20-08-2024 16:20, Beleswar Padhi wrote: From: Udit Kumar Few times, core1 was scheduled to boot first before core0, which leads to error: 'k3_r5_rproc_start: can not start core 1 before core 0'. This was happening due to some scheduling between prepare and start callback. The

[PATCH v2] remoteproc: k3-r5: Delay notification of wakeup event

2024-08-20 Thread Beleswar Padhi
From: Udit Kumar Few times, core1 was scheduled to boot first before core0, which leads to error: 'k3_r5_rproc_start: can not start core 1 before core 0'. This was happening due to some scheduling between prepare and start callback. The probe function waits for event, which is getting triggered