From: "Falkowski, Maciej" <maciej.falkowski@linux.intel.com>
To: Jeff Hugo <jeff.hugo@oss.qualcomm.com>, dri-devel@lists.freedesktop.org
Cc: oded.gabbay@gmail.com, jacek.lawrynowicz@linux.intel.com,
lizhi.hou@amd.com, Karol Wachowski <karol.wachowski@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] accel/ivpu: Reorder doorbell unregister and command queue destruction
Date: Thu, 5 Jun 2025 18:24:41 +0200 [thread overview]
Message-ID: <22209cdb-db72-4515-852d-9df1f4091402@linux.intel.com> (raw)
In-Reply-To: <0423ac43-0a12-4f0f-ade3-61364d4abf93@oss.qualcomm.com>
On 6/4/2025 6:18 PM, Jeff Hugo wrote:
> On 6/4/2025 9:44 AM, Maciej Falkowski wrote:
>> From: Karol Wachowski <karol.wachowski@intel.com>
>>
>> Refactor ivpu_cmdq_unregister() to ensure the doorbell is unregistered
>> before destroying the command queue. The NPU firmware requires doorbells
>> to be unregistered prior to command queue destruction.
>>
>> If doorbell remains registered when command queue destroy command is
>> sent
>> firmware will automatically unregister the doorbell, making subsequent
>> unregister attempts no-operations (NOPs).
>>
>> Ensure compliance with firmware expectations by moving the doorbell
>> unregister call ahead of the command queue destruction logic,
>> thus preventing unnecessary NOP operation.
>>
>> Fixes: 2a18ceff9482 ("accel/ivpu: Implement support for hardware
>> scheduler")
>> Cc: <stable@vger.kernel.org> # v6.11+
>> Signed-off-by: Karol Wachowski <karol.wachowski@intel.com>
>> Signed-off-by: Maciej Falkowski <maciej.falkowski@linux.intel.com>
>
> Huh? This was posted to the list on May 15th, and Jacek applied it to
> drm-misc-fixes on May 28th.
My apologies, you are right. I accidentally included it while checking
latest changes.
Best regards,
Maciej
>
> -Jeff
prev parent reply other threads:[~2025-06-05 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 15:44 [PATCH] accel/ivpu: Reorder doorbell unregister and command queue destruction Maciej Falkowski
2025-06-04 16:18 ` Jeff Hugo
2025-06-05 16:24 ` Falkowski, Maciej [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=22209cdb-db72-4515-852d-9df1f4091402@linux.intel.com \
--to=maciej.falkowski@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=karol.wachowski@intel.com \
--cc=lizhi.hou@amd.com \
--cc=oded.gabbay@gmail.com \
--cc=stable@vger.kernel.org \
/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