On Tue, Apr 08, 2025 at 04:13:17PM +0530, Souradeep Chowdhury wrote:
> Add device awake calls in case of rproc boot and rproc shutdown path.
> Currently, device awake call is only present in the recovery path
> of remoteproc. If an user stops and starts rproc by using the sysfs
> interface, then on
Gentle Reminder
On 5/19/2025 10:54 AM, Souradeep Chowdhury wrote:
Gentle Reminder
On 5/14/2025 1:03 PM, Souradeep Chowdhury wrote:
Gentle Reminder
On 4/8/2025 4:13 PM, Souradeep Chowdhury wrote:
Add device awake calls in case of rproc boot and rproc shutdown path.
Currently, device awake
Gentle Reminder
On 5/14/2025 1:03 PM, Souradeep Chowdhury wrote:
Gentle Reminder
On 4/8/2025 4:13 PM, Souradeep Chowdhury wrote:
Add device awake calls in case of rproc boot and rproc shutdown path.
Currently, device awake call is only present in the recovery path
of remoteproc. If an user s
Gentle Reminder
On 4/8/2025 4:13 PM, Souradeep Chowdhury wrote:
Add device awake calls in case of rproc boot and rproc shutdown path.
Currently, device awake call is only present in the recovery path
of remoteproc. If an user stops and starts rproc by using the sysfs
interface, then on pm suspe
Gentle Reminder
On 4/8/2025 4:13 PM, Souradeep Chowdhury wrote:
Add device awake calls in case of rproc boot and rproc shutdown path.
Currently, device awake call is only present in the recovery path
of remoteproc. If an user stops and starts rproc by using the sysfs
interface, then on pm suspen
Add device awake calls in case of rproc boot and rproc shutdown path.
Currently, device awake call is only present in the recovery path
of remoteproc. If an user stops and starts rproc by using the sysfs
interface, then on pm suspension the firmware fails to load as the
request_firmware call under
6 matches
Mail list logo
