dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
To: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>,
	dri-devel@lists.freedesktop.org
Cc: Karol Wachowski <karol.wachowski@linux.intel.com>,
	Oded Gabbay <ogabbay@kernel.org>,
	Jeffrey Hugo <quic_jhugo@quicinc.com>
Subject: Re: [PATCH 2/2] accel/ivpu: Clear specific interrupt status bits on C0
Date: Wed, 5 Jul 2023 10:26:59 +0200	[thread overview]
Message-ID: <273900af-6501-0675-4b73-1112c1019e71@linux.intel.com> (raw)
In-Reply-To: <20230703080725.2065635-2-stanislaw.gruszka@linux.intel.com>

Reviewed-by: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>

On 03.07.2023 10:07, Stanislaw Gruszka wrote:
> From: Karol Wachowski <karol.wachowski@linux.intel.com>
> 
> MTL C0 stepping fixed issue related to butrress interrupt status clearing,
> to clear an interrupt status it is required to write 1 to specific
> status bit field. This allows to execute read, modify and write routine.
> 
> Writing 0 will not clear the interrupt and will cause interrupt storm.
> 
> Fixes: 35b137630f08 ("accel/ivpu: Introduce a new DRM driver for Intel VPU")
> Cc: stable@vger.kernel.org # 6.3.x
> Signed-off-by: Karol Wachowski <karol.wachowski@linux.intel.com>
> Signed-off-by: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
> ---
>  drivers/accel/ivpu/ivpu_drv.h    |  1 +
>  drivers/accel/ivpu/ivpu_hw_mtl.c | 18 ++++++++++++------
>  2 files changed, 13 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/accel/ivpu/ivpu_drv.h b/drivers/accel/ivpu/ivpu_drv.h
> index 315180dd72ce..8fe8cda2e39d 100644
> --- a/drivers/accel/ivpu/ivpu_drv.h
> +++ b/drivers/accel/ivpu/ivpu_drv.h
> @@ -75,6 +75,7 @@ struct ivpu_wa_table {
>  	bool punit_disabled;
>  	bool clear_runtime_mem;
>  	bool d3hot_after_power_off;
> +	bool interrupt_clear_with_0;
>  };
>  
>  struct ivpu_hw_info;
> diff --git a/drivers/accel/ivpu/ivpu_hw_mtl.c b/drivers/accel/ivpu/ivpu_hw_mtl.c
> index d3ba633daaa0..f1211e74017d 100644
> --- a/drivers/accel/ivpu/ivpu_hw_mtl.c
> +++ b/drivers/accel/ivpu/ivpu_hw_mtl.c
> @@ -101,6 +101,9 @@ static void ivpu_hw_wa_init(struct ivpu_device *vdev)
>  	vdev->wa.punit_disabled = ivpu_is_fpga(vdev);
>  	vdev->wa.clear_runtime_mem = false;
>  	vdev->wa.d3hot_after_power_off = true;
> +
> +	if (ivpu_device_id(vdev) == PCI_DEVICE_ID_MTL && ivpu_revision(vdev) < 4)
> +		vdev->wa.interrupt_clear_with_0 = true;
>  }
>  
>  static void ivpu_hw_timeouts_init(struct ivpu_device *vdev)
> @@ -962,12 +965,15 @@ static u32 ivpu_hw_mtl_irqb_handler(struct ivpu_device *vdev, int irq)
>  		schedule_recovery = true;
>  	}
>  
> -	/*
> -	 * Clear local interrupt status by writing 0 to all bits.
> -	 * This must be done after interrupts are cleared at the source.
> -	 * Writing 1 triggers an interrupt, so we can't perform read update write.
> -	 */
> -	REGB_WR32(MTL_BUTTRESS_INTERRUPT_STAT, 0x0);
> +	/* This must be done after interrupts are cleared at the source. */
> +	if (IVPU_WA(interrupt_clear_with_0))
> +		/*
> +		 * Writing 1 triggers an interrupt, so we can't perform read update write.
> +		 * Clear local interrupt status by writing 0 to all bits.
> +		 */
> +		REGB_WR32(MTL_BUTTRESS_INTERRUPT_STAT, 0x0);
> +	else
> +		REGB_WR32(MTL_BUTTRESS_INTERRUPT_STAT, status);
>  
>  	/* Re-enable global interrupt */
>  	REGB_WR32(MTL_BUTTRESS_GLOBAL_INT_MASK, 0x0);

  reply	other threads:[~2023-07-05  8:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03  8:07 [PATCH 1/2] accel/ivpu: Fix VPU register access in irq disable Stanislaw Gruszka
2023-07-03  8:07 ` [PATCH 2/2] accel/ivpu: Clear specific interrupt status bits on C0 Stanislaw Gruszka
2023-07-05  8:26   ` Jacek Lawrynowicz [this message]
2023-07-05  8:26 ` [PATCH 1/2] accel/ivpu: Fix VPU register access in irq disable Jacek Lawrynowicz
2023-07-05 10:38 ` Stanislaw Gruszka

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=273900af-6501-0675-4b73-1112c1019e71@linux.intel.com \
    --to=jacek.lawrynowicz@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=karol.wachowski@linux.intel.com \
    --cc=ogabbay@kernel.org \
    --cc=quic_jhugo@quicinc.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox