Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@kernel.org>
To: Mikko Perttunen <mperttunen@nvidia.com>
Cc: David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	 dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] Miscellaneous fixes for the Host1x driver
Date: Thu, 16 Jul 2026 20:52:55 +0200	[thread overview]
Message-ID: <alkodFCXR7fqj_X9@orome> (raw)
In-Reply-To: <20260609-b4-host1x-small-fixes-a-v1-0-7c1131c0b3ad@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 1589 bytes --]

On Tue, Jun 09, 2026 at 05:09:16PM +0900, Mikko Perttunen wrote:
> This series has a number of small miscellaneous fixes to the host1x 
> driver.
> 
> Patches 1 to 4 fix various logic issues that are unlikely to happen
> but technically possible.
> 
> Patch 5 fixes a return type from unsigned int to int -- no functional
> difference.
> 
> Patch 6 adds makes syncpoint value arithmetic explicitly wrapping, 
> mostly to help static/dynamic analysis tools.
> 
> ---
> Mikko Perttunen (6):
>       gpu: host1x: Wait for timeout worker completion on channel free
>       gpu: host1x: Avoid double device_add when clients already present
>       gpu: host1x: Fix offset calculation in trace_write_gather
>       gpu: host1x: Avoid stack over-read in debug output helpers
>       gpu: host1x: Change pin_job() return type to int
>       gpu: host1x: Annotate intentional syncpoint wrap-around
> 
>  drivers/gpu/host1x/bus.c           |  2 +-
>  drivers/gpu/host1x/cdma.c          |  3 ++-
>  drivers/gpu/host1x/debug.c         |  4 ++--
>  drivers/gpu/host1x/hw/cdma_hw.c    |  2 +-
>  drivers/gpu/host1x/hw/channel_hw.c | 15 +++++++++------
>  drivers/gpu/host1x/intr.c          |  5 +++--
>  drivers/gpu/host1x/job.c           |  2 +-
>  drivers/gpu/host1x/syncpt.c        |  7 ++++++-
>  drivers/gpu/host1x/syncpt.h        |  3 ++-
>  9 files changed, 27 insertions(+), 16 deletions(-)
> ---
> base-commit: 4549871118cf616eecdd2d939f78e3b9e1dddc48
> change-id: 20260608-b4-host1x-small-fixes-a-081cfea2c073

Applied to drm-misc-next, thanks.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2026-07-16 18:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09  8:09 [PATCH 0/6] Miscellaneous fixes for the Host1x driver Mikko Perttunen
2026-06-09  8:09 ` [PATCH 1/6] gpu: host1x: Wait for timeout worker completion on channel free Mikko Perttunen
2026-06-09  8:09 ` [PATCH 2/6] gpu: host1x: Avoid double device_add when clients already present Mikko Perttunen
2026-06-09  8:09 ` [PATCH 3/6] gpu: host1x: Fix offset calculation in trace_write_gather Mikko Perttunen
2026-06-09  8:09 ` [PATCH 4/6] gpu: host1x: Avoid stack over-read in debug output helpers Mikko Perttunen
2026-06-09  8:09 ` [PATCH 5/6] gpu: host1x: Change pin_job() return type to int Mikko Perttunen
2026-06-09  8:09 ` [PATCH 6/6] gpu: host1x: Annotate intentional syncpoint wrap-around Mikko Perttunen
2026-07-16 18:52 ` Thierry Reding [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=alkodFCXR7fqj_X9@orome \
    --to=thierry.reding@kernel.org \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mperttunen@nvidia.com \
    --cc=simona@ffwll.ch \
    /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