dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
To: Karol Wachowski <karol.wachowski@linux.intel.com>,
	dri-devel@lists.freedesktop.org
Cc: oded.gabbay@gmail.com, jeff.hugo@oss.qualcomm.com,
	lizhi.hou@amd.com, andrzej.kacprowski@linux.intel.com,
	Tomasz Rusinowicz <tomasz.rusinowicz@intel.com>
Subject: Re: [PATCH v3] accel/ivpu: Move register poll timeouts to vdev->timeout
Date: Tue, 15 Sep 2026 11:46:07 +0200	[thread overview]
Message-ID: <b0c7d83e-84d5-4340-9e8a-252e6377b6b8@linux.intel.com> (raw)
In-Reply-To: <20260915083651.950890-1-karol.wachowski@linux.intel.com>

On 2026-09-15 10:36 AM, Karol Wachowski wrote:
> From: Tomasz Rusinowicz <tomasz.rusinowicz@intel.com>
> 
> Use the vdev->timeout structure for register poll timeouts. This allows
> adjusting those timeouts depending on the platform type.
> For FPGA set MMU timeouts to 10x.
> 
> Register poll timeouts are expressed in microseconds and are passed to
> read_poll_timeout(), which disables a timeout when it is 0, unlike the
> millisecond timeouts that are disabled with a negative value.
> 
> Also initialize state_dump_msg in the IVPU_TEST_MODE_DISABLE_TIMEOUTS
> branch, which was missed when the field was added. Unlike the other
> fields, it is a fixed delay passed to msleep() rather than a timeout, so
> it has to keep a finite value. It is only reachable with this debug test
> mode enabled, so there is no need for backporting.
> 

Reviewed-by: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>

> Signed-off-by: Tomasz Rusinowicz <tomasz.rusinowicz@intel.com>
> Signed-off-by: Karol Wachowski <karol.wachowski@linux.intel.com>
> ---
> Changes in v3:
>   - Address Sashiko AI review comment: disable the microsecond register
>     poll timeouts with 0 instead of -1. read_poll_timeout() treats 0 as
>     "never timeout", while -1 is converted to 0xffffffff and results in
>     a finite ~71.6 minute timeout
>     Review: https://sashiko.dev/#/patchset/20260914082649.891871-1-karol.wachowski@linux.intel.com?part=1
>   - Initialize state_dump_msg in the IVPU_TEST_MODE_DISABLE_TIMEOUTS
>     branch, it is a fixed msleep() delay and has to remain finite
>   - Explain the timeout semantics in the commit message
>   - Link to v2: https://lore.kernel.org/dri-devel/20260914084503.895042-1-karol.wachowski@linux.intel.com/T/#u
> 
> Changes in v2:
>   - Add Signed-off-by: Karol Wachowski
>   - Link to v1: https://lore.kernel.org/dri-devel/20260914082649.891871-1-karol.wachowski@linux.intel.com/T/#u
> ---
>   drivers/accel/ivpu/ivpu_drv.h   |  3 +++
>   drivers/accel/ivpu/ivpu_hw.c    | 22 ++++++++++++++++++++++
>   drivers/accel/ivpu/ivpu_hw_ip.c |  6 ++----
>   drivers/accel/ivpu/ivpu_mmu.c   | 12 ++++--------
>   4 files changed, 31 insertions(+), 12 deletions(-)

  reply	other threads:[~2026-09-15  9:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15  8:36 [PATCH v3] accel/ivpu: Move register poll timeouts to vdev->timeout Karol Wachowski
2026-09-15  9:46 ` Dawid Osuchowski [this message]
2026-09-15  9:49 ` Andrzej Kacprowski
2026-09-17  7:39   ` Wachowski, Karol

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=b0c7d83e-84d5-4340-9e8a-252e6377b6b8@linux.intel.com \
    --to=dawid.osuchowski@linux.intel.com \
    --cc=andrzej.kacprowski@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jeff.hugo@oss.qualcomm.com \
    --cc=karol.wachowski@linux.intel.com \
    --cc=lizhi.hou@amd.com \
    --cc=oded.gabbay@gmail.com \
    --cc=tomasz.rusinowicz@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