From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: "Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Oded Gabbay" <ogabbay@kernel.org>,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, dim-tools@lists.freedesktop.org
Subject: [PULL] drm-intel-fixes
Date: Wed, 8 May 2024 15:32:36 -0400 [thread overview]
Message-ID: <ZjvTVEmQeVKVB2jx@intel.com> (raw)
Hi Dave and Sima,
Here goes our last fixes for v6.9.
drm-intel-fixes-2024-05-08:
- Automate CCS Mode setting during engine resets (Andi)
- Fix audio time stamp programming for DP (Chaitanya)
- Fix parsing backlight BDB data (Karthikeyan)
The following changes since commit dd5a440a31fae6e459c0d6271dddd62825505361:
Linux 6.9-rc7 (2024-05-05 14:06:01 -0700)
are available in the Git repository at:
https://anongit.freedesktop.org/git/drm/drm-intel tags/drm-intel-fixes-2024-05-08
for you to fetch changes up to 43b26bdd2ee5cfca80939be910d5b23a50cd7f9d:
drm/i915/bios: Fix parsing backlight BDB data (2024-05-07 09:42:27 -0400)
----------------------------------------------------------------
- Automate CCS Mode setting during engine resets (Andi)
- Fix audio time stamp programming for DP (Chaitanya)
- Fix parsing backlight BDB data (Karthikeyan)
----------------------------------------------------------------
Andi Shyti (1):
drm/i915/gt: Automate CCS Mode setting during engine resets
Chaitanya Kumar Borah (1):
drm/i915/audio: Fix audio time stamp programming for DP
Karthikeyan Ramasubramanian (1):
drm/i915/bios: Fix parsing backlight BDB data
drivers/gpu/drm/i915/display/intel_audio.c | 113 ++------------------------
drivers/gpu/drm/i915/display/intel_bios.c | 19 +----
drivers/gpu/drm/i915/display/intel_vbt_defs.h | 5 --
drivers/gpu/drm/i915/gt/intel_gt_ccs_mode.c | 6 +-
drivers/gpu/drm/i915/gt/intel_gt_ccs_mode.h | 2 +-
drivers/gpu/drm/i915/gt/intel_workarounds.c | 4 +-
6 files changed, 19 insertions(+), 130 deletions(-)
next reply other threads:[~2024-05-08 19:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 19:32 Rodrigo Vivi [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-10 21:51 [PULL] drm-intel-fixes Rodrigo Vivi
2024-04-04 17:45 Rodrigo Vivi
2024-03-29 1:32 Rodrigo Vivi
2024-03-29 10:23 ` Musial, Ewelina
2024-03-29 13:25 ` Rodrigo Vivi
2024-03-07 8:19 Joonas Lahtinen
2024-03-01 8:14 Joonas Lahtinen
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=ZjvTVEmQeVKVB2jx@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ogabbay@kernel.org \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).