From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com, ville.syrjala@linux.intel.com
Subject: [PATCH 0/6] drm/i915/pps: pass dev_priv explicitly to PPS regs
Date: Mon, 27 May 2024 13:41:56 +0300 [thread overview]
Message-ID: <cover.1716806471.git.jani.nikula@intel.com> (raw)
Continue avoiding the implicit dev_priv local variable.
Jani Nikula (6):
drm/i915: pass dev_priv explicitly to _MMIO_PPS
drm/i915: pass dev_priv explicitly to PP_STATUS
drm/i915: pass dev_priv explicitly to PP_CONTROL
drm/i915: pass dev_priv explicitly to PP_ON_DELAYS
drm/i915: pass dev_priv explicitly to PP_OFF_DELAYS
drm/i915: pass dev_priv explicitly to PP_DIVISOR
.../drm/i915/display/intel_display_power.c | 2 +-
drivers/gpu/drm/i915/display/intel_dsi_vbt.c | 4 +--
drivers/gpu/drm/i915/display/intel_lvds.c | 29 +++++++++---------
drivers/gpu/drm/i915/display/intel_pps.c | 30 +++++++++----------
drivers/gpu/drm/i915/display/intel_pps_regs.h | 16 +++++-----
5 files changed, 41 insertions(+), 40 deletions(-)
--
2.39.2
next reply other threads:[~2024-05-27 10:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 10:41 Jani Nikula [this message]
2024-05-27 10:41 ` [PATCH 1/6] drm/i915: pass dev_priv explicitly to _MMIO_PPS Jani Nikula
2024-05-27 10:41 ` [PATCH 2/6] drm/i915: pass dev_priv explicitly to PP_STATUS Jani Nikula
2024-05-27 10:41 ` [PATCH 3/6] drm/i915: pass dev_priv explicitly to PP_CONTROL Jani Nikula
2024-05-27 10:42 ` [PATCH 4/6] drm/i915: pass dev_priv explicitly to PP_ON_DELAYS Jani Nikula
2024-05-27 10:42 ` [PATCH 5/6] drm/i915: pass dev_priv explicitly to PP_OFF_DELAYS Jani Nikula
2024-05-27 10:42 ` [PATCH 6/6] drm/i915: pass dev_priv explicitly to PP_DIVISOR Jani Nikula
2024-05-27 13:30 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/pps: pass dev_priv explicitly to PPS regs Patchwork
2024-05-27 13:40 ` ✓ Fi.CI.BAT: success " Patchwork
2024-05-27 22:11 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-05-28 5:55 ` [PATCH 0/6] " Borah, Chaitanya Kumar
2024-05-28 8:11 ` Jani Nikula
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.1716806471.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.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 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.