All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
To: dri-devel@lists.freedesktop.org
Cc: quic_jhugo@quicinc.com, lizhi.hou@amd.com, stable@vger.kernel.org
Subject: Re: [PATCH] accel/ivpu: Increase state dump msg timeout
Date: Wed, 30 Apr 2025 11:54:26 +0200	[thread overview]
Message-ID: <07c8be10-3454-42db-b787-99a764520924@linux.intel.com> (raw)
In-Reply-To: <20250425092822.2194465-1-jacek.lawrynowicz@linux.intel.com>

Applied to drm-misc-fixes

On 4/25/2025 11:28 AM, Jacek Lawrynowicz wrote:
> Increase JMS message state dump command timeout to 100 ms. On some
> platforms, the FW may take a bit longer than 50 ms to dump its state
> to the log buffer and we don't want to miss any debug info during TDR.
> 
> Fixes: 5e162f872d7a ("accel/ivpu: Add FW state dump on TDR")
> Cc: <stable@vger.kernel.org> # v6.13+
> Signed-off-by: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
> ---
>  drivers/accel/ivpu/ivpu_hw.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/accel/ivpu/ivpu_hw.c b/drivers/accel/ivpu/ivpu_hw.c
> index ec9a3629da3a9..633160470c939 100644
> --- a/drivers/accel/ivpu/ivpu_hw.c
> +++ b/drivers/accel/ivpu/ivpu_hw.c
> @@ -119,7 +119,7 @@ static void timeouts_init(struct ivpu_device *vdev)
>  		else
>  			vdev->timeout.autosuspend = 100;
>  		vdev->timeout.d0i3_entry_msg = 5;
> -		vdev->timeout.state_dump_msg = 10;
> +		vdev->timeout.state_dump_msg = 100;
>  	}
>  }
>  


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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-25  9:28 [PATCH] accel/ivpu: Increase state dump msg timeout Jacek Lawrynowicz
2025-04-25 17:09 ` Jeff Hugo
2025-04-30  9:54 ` Jacek Lawrynowicz [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=07c8be10-3454-42db-b787-99a764520924@linux.intel.com \
    --to=jacek.lawrynowicz@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=lizhi.hou@amd.com \
    --cc=quic_jhugo@quicinc.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 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.