From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH 0/4] drm/i915: add dedicated lock for each sideband
Date: Wed, 2 Oct 2024 20:30:27 +0300 [thread overview]
Message-ID: <cover.1727890136.git.jani.nikula@intel.com> (raw)
It's misleading to use the same sideband mutex for LPT/WPT IOSF, VLV/CHV
IOSF, and punit. Add dedicated locks for clarity.
Jani Nikula (4):
drm/i915/sbi: add intel_sbi_{lock,unlock}()
drm/i915/sbi: add a dedicated mutex for LPT/WPT IOSF sideband
drm/i915: add a dedicated mutex for VLV/CHV IOSF sideband
drm/i915: hide VLV PUNIT IOSF sideband qos handling better
.../gpu/drm/i915/display/intel_pch_refclk.c | 26 ++++++++---------
drivers/gpu/drm/i915/i915_driver.c | 8 ++++--
drivers/gpu/drm/i915/i915_drv.h | 10 ++++++-
drivers/gpu/drm/i915/intel_sbi.c | 22 ++++++++++++++-
drivers/gpu/drm/i915/intel_sbi.h | 4 +++
drivers/gpu/drm/i915/vlv_sideband.c | 28 +++++++++++++++----
drivers/gpu/drm/i915/vlv_sideband.h | 3 ++
7 files changed, 79 insertions(+), 22 deletions(-)
--
2.39.5
next reply other threads:[~2024-10-02 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 17:30 Jani Nikula [this message]
2024-10-02 17:30 ` [PATCH 1/4] drm/i915/sbi: add intel_sbi_{lock,unlock}() Jani Nikula
2024-10-02 17:30 ` [PATCH 2/4] drm/i915/sbi: add a dedicated mutex for LPT/WPT IOSF sideband Jani Nikula
2024-10-02 17:30 ` [PATCH 3/4] drm/i915: add a dedicated mutex for VLV/CHV " Jani Nikula
2024-10-02 17:30 ` [PATCH 4/4] drm/i915: hide VLV PUNIT IOSF sideband qos handling better Jani Nikula
2024-10-02 18:15 ` ✗ Fi.CI.SPARSE: warning for drm/i915: add dedicated lock for each sideband Patchwork
2024-10-02 18:33 ` ✓ Fi.CI.BAT: success " Patchwork
2024-10-04 0:47 ` ✗ Fi.CI.IGT: failure " Patchwork
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=cover.1727890136.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox