From: Greg KH <gregkh@linuxfoundation.org>
To: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
Cc: stable@vger.kernel.org,
Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>,
Karol Wachowski <karol.wachowski@linux.intel.com>
Subject: Re: [PATCH 6.5] accel/ivpu/37xx: Fix missing VPUIP interrupts
Date: Tue, 31 Oct 2023 12:53:44 +0100 [thread overview]
Message-ID: <2023103135-tattoo-feminize-9cff@gregkh> (raw)
In-Reply-To: <20231028175320.6791-1-stanislaw.gruszka@linux.intel.com>
On Sat, Oct 28, 2023 at 07:53:20PM +0200, Stanislaw Gruszka wrote:
> From: Karol Wachowski <karol.wachowski@linux.intel.com>
>
> commit b132ac51d7a50c37683be56c96ff64f8c887930f upstream.
>
> Move sequence of masking and unmasking global interrupts from buttress
> interrupt handler to generic one that handles both VPUIP and BTRS
> interrupts. Unmasking global interrupts will re-trigger MSI for any
> pending interrupts.
>
> Lack of this sequence will cause the driver to miss any
> VPUIP interrupt that comes after reading VPU_37XX_HOST_SS_ICB_STATUS_0
> and before clearing all active interrupt sources.
>
> Fixes: 35b137630f08 ("accel/ivpu: Introduce a new DRM driver for Intel VPU")
> Cc: stable@vger.kernel.org
> Signed-off-by: Karol Wachowski <karol.wachowski@linux.intel.com>
> Reviewed-by: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
> Signed-off-by: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
> Link: https://patchwork.freedesktop.org/patch/msgid/20231024161952.759914-1-stanislaw.gruszka@linux.intel.com
> ---
> drivers/accel/ivpu/ivpu_hw_mtl.c | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-10-31 11:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 17:53 [PATCH 6.5] accel/ivpu/37xx: Fix missing VPUIP interrupts Stanislaw Gruszka
2023-10-31 11:53 ` Greg KH [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=2023103135-tattoo-feminize-9cff@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=karol.wachowski@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=stanislaw.gruszka@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.