On 10/28/2025 1:06 AM, Karol Wachowski wrote:
During power down, pending DVFS operations may still be in progress
when the NPU reset is asserted after CDYN=0 is set. Since the READY
bit may already be deasserted at this point, checking only the READY
bit is insufficient to ensure all transactions have completed.
Add an explicit check for CDYN de-assertion after the READY bit check
to guarantee no outstanding transactions remain before proceeding.
Is it worthwhile to mention what can break if transactions are pending
while we proceed? Is there something that the user will see?
I'm guessing that proceeding with active transactions is bad, but its
unclear to me if this is just a best practice, or actually fixes some
kind of issue that will actually impact the user. If there is actual
user impact that this addresses, should we consider a fixes tag?
-Jeff
