On 10/10/23 17:49, Maramaina Naresh wrote:
PM QoS per-cpu framework provides performance requirements for each cpu. The per-cpu PM QoS framework will provide the corresponding interface to collect the resume_latency request of the specified device and provide it to the runtime PM. When suspending the device, it will consider this requirement and decide whether to suspend the device. Voting will follow below sequence. 1. Vote for maximum latency S32_MAX in driver init. 2. Schedule a vote of PERF when a transfer request is received. 3. Update the vote to S32_MAX during clock gating. Signed-off-by: Asutosh Das <quic_asutoshd@xxxxxxxxxxx> Signed-off-by: Nitin Rawat <quic_nitirawa@xxxxxxxxxxx> Signed-off-by: Naveen Kumar Goud Arepalli <quic_narepall@xxxxxxxxxxx> Signed-off-by: Maramaina Naresh <quic_mnaresh@xxxxxxxxxxx> ---
Is this the same patch as 2/4? Konrad
