dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Karol Wachowski <karol.wachowski@linux.intel.com>
To: Jeff Hugo <jeff.hugo@oss.qualcomm.com>, dri-devel@lists.freedesktop.org
Cc: oded.gabbay@gmail.com, maciej.falkowski@linux.intel.com,
	lizhi.hou@amd.com
Subject: Re: [PATCH] accel/ivpu: Wait for CDYN de-assertion during power down sequence
Date: Thu, 30 Oct 2025 10:04:28 +0100	[thread overview]
Message-ID: <ed574e3c-61d8-4dfd-81f2-5a7fc00df224@linux.intel.com> (raw)
In-Reply-To: <dd579486-efbf-41a4-8523-a804c8f7e68f@oss.qualcomm.com>

On 10/29/2025 4:47 PM, Jeff Hugo wrote:
> 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 
Hi
Jeff,                                                                                                                                           

This is primarily a best practice to avoid potential issues on NPU6,
where pending transactions can cause issues with power down transition. 
While it doesn't fix user-visible bugs on existing platforms, it ensures
unified power down sequence across all platforms that support this
register, making the code clearer than conditional handling just for NPU6.

You're right about the Fixes tag, since NPU6 support is already
upstream, I'll add one.

-Karol

      reply	other threads:[~2025-10-30  9:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28  7:06 [PATCH] accel/ivpu: Wait for CDYN de-assertion during power down sequence Karol Wachowski
2025-10-29 15:47 ` Jeff Hugo
2025-10-30  9:04   ` Karol Wachowski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ed574e3c-61d8-4dfd-81f2-5a7fc00df224@linux.intel.com \
    --to=karol.wachowski@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jeff.hugo@oss.qualcomm.com \
    --cc=lizhi.hou@amd.com \
    --cc=maciej.falkowski@linux.intel.com \
    --cc=oded.gabbay@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).