All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karol Wachowski <karol.wachowski@linux.intel.com>
To: dri-devel@lists.freedesktop.org
Cc: oded.gabbay@gmail.com, jeff.hugo@oss.qualcomm.com,
	lizhi.hou@amd.com, andrzej.kacprowski@linux.intel.com,
	dawid.osuchowski@linux.intel.com,
	Karol Wachowski <karol.wachowski@linux.intel.com>
Subject: [PATCH 0/5] accel/ivpu: Merge register headers and extend tile fuse config
Date: Mon, 12 Oct 2026 10:37:57 +0200	[thread overview]
Message-ID: <20261012083802.2778448-1-karol.wachowski@linux.intel.com> (raw)

This series removes duplication between the per-generation register
definitions and code in the ivpu driver, and adds a debug test mode.

Patch 1 adds a test mode that enables the buttress FREQ_CHANGE interrupt
and stores the buttress interrupt mask in struct ivpu_hw_info.

Patches 2-4 merge the 37xx/40xx IP register headers, the identical 37xx
and 40xx IP functions, and the MTL/LNL buttress register headers. There
is no functional change.

Patch 5 extends the tile fuse config field to 7 bits.

Karol Wachowski (5):
  accel/ivpu: Add test mode to enable the FREQ_CHANGE interrupt
  accel/ivpu: Merge NPU IP register headers
  accel/ivpu: Merge identical 37xx and 40xx IP functions
  accel/ivpu: Merge buttress register headers
  accel/ivpu: Extend tile fuse config to 7 bits

 drivers/accel/ivpu/ivpu_drv.h                 |   1 +
 drivers/accel/ivpu/ivpu_hw.c                  |   5 -
 drivers/accel/ivpu/ivpu_hw.h                  |   7 +-
 drivers/accel/ivpu/ivpu_hw_40xx_reg.h         | 195 ---------
 drivers/accel/ivpu/ivpu_hw_btrs.c             |  32 +-
 drivers/accel/ivpu/ivpu_hw_btrs.h             |   2 -
 drivers/accel/ivpu/ivpu_hw_btrs_mtl_reg.h     |  83 ----
 ...u_hw_btrs_lnl_reg.h => ivpu_hw_btrs_reg.h} |  84 +++-
 drivers/accel/ivpu/ivpu_hw_ip.c               | 396 +++---------------
 drivers/accel/ivpu/ivpu_hw_ip.h               |   3 +-
 .../{ivpu_hw_37xx_reg.h => ivpu_hw_ip_reg.h}  |  69 ++-
 11 files changed, 232 insertions(+), 645 deletions(-)
 delete mode 100644 drivers/accel/ivpu/ivpu_hw_40xx_reg.h
 delete mode 100644 drivers/accel/ivpu/ivpu_hw_btrs_mtl_reg.h
 rename drivers/accel/ivpu/{ivpu_hw_btrs_lnl_reg.h => ivpu_hw_btrs_reg.h} (58%)
 rename drivers/accel/ivpu/{ivpu_hw_37xx_reg.h => ivpu_hw_ip_reg.h} (73%)

-- 
2.43.0


             reply	other threads:[~2026-10-12  8:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12  8:37 Karol Wachowski [this message]
2026-10-12  8:37 ` [PATCH 1/5] accel/ivpu: Add test mode to enable the FREQ_CHANGE interrupt Karol Wachowski
2026-10-12  8:37 ` [PATCH 2/5] accel/ivpu: Merge NPU IP register headers Karol Wachowski
2026-10-12  8:38 ` [PATCH 3/5] accel/ivpu: Merge identical 37xx and 40xx IP functions Karol Wachowski
2026-10-12  8:38 ` [PATCH 4/5] accel/ivpu: Merge buttress register headers Karol Wachowski
2026-10-12  8:38 ` [PATCH 5/5] accel/ivpu: Extend tile fuse config to 7 bits Karol Wachowski
2026-10-12 10:44 ` [PATCH 0/5] accel/ivpu: Merge register headers and extend tile fuse config Dawid Osuchowski

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=20261012083802.2778448-1-karol.wachowski@linux.intel.com \
    --to=karol.wachowski@linux.intel.com \
    --cc=andrzej.kacprowski@linux.intel.com \
    --cc=dawid.osuchowski@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jeff.hugo@oss.qualcomm.com \
    --cc=lizhi.hou@amd.com \
    --cc=oded.gabbay@gmail.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.