Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/4] drm/i915/dsb: A bit of polish
Date: Fri, 31 May 2024 14:40:57 +0300	[thread overview]
Message-ID: <20240531114101.19994-1-ville.syrjala@linux.intel.com> (raw)

From: Ville Syrjälä <ville.syrjala@linux.intel.com>

Apply a bit of polish to the DSB interface.

Ville Syrjälä (4):
  drm/i915/dsb: Polish the DSB ID enum
  drm/i915/dsb: Move DSB ID definition to the header
  drm/i915/dsb: Pass DSB engine ID to intel_dsb_prepare()
  drm/i915/dsb: Use intel_color_uses_dsb()

 drivers/gpu/drm/i915/display/intel_color.c  |  2 +-
 drivers/gpu/drm/i915/display/intel_dsb.c    | 20 +++++++-------------
 drivers/gpu/drm/i915/display/intel_dsb.h    |  9 +++++++++
 drivers/gpu/drm/i915/display/intel_vblank.c |  4 +++-
 4 files changed, 20 insertions(+), 15 deletions(-)

-- 
2.44.1


             reply	other threads:[~2024-05-31 11:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31 11:40 Ville Syrjala [this message]
2024-05-31 11:40 ` [PATCH 1/4] drm/i915/dsb: Polish the DSB ID enum Ville Syrjala
2024-06-06 18:57   ` Manna, Animesh
2024-05-31 11:40 ` [PATCH 2/4] drm/i915/dsb: Move DSB ID definition to the header Ville Syrjala
2024-06-06 18:56   ` Manna, Animesh
2024-05-31 11:41 ` [PATCH 3/4] drm/i915/dsb: Pass DSB engine ID to intel_dsb_prepare() Ville Syrjala
2024-06-06 18:56   ` Manna, Animesh
2024-05-31 11:41 ` [PATCH 4/4] drm/i915/dsb: Use intel_color_uses_dsb() Ville Syrjala
2024-06-06 18:56   ` Manna, Animesh
2024-05-31 12:13 ` [PATCH 0/4] drm/i915/dsb: A bit of polish Rodrigo Vivi
2024-05-31 12:33 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2024-05-31 12:50 ` ✓ Fi.CI.BAT: success " Patchwork
2024-06-01 14:46 ` ✗ 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=20240531114101.19994-1-ville.syrjala@linux.intel.com \
    --to=ville.syrjala@linux.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