From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>, Dave Airlie <airlied@gmail.com>
Cc: dim-tools@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
"Oded Gabbay" <ogabbay@kernel.org>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Jani Nikula" <jani.nikula@linux.intel.com>
Subject: [PULL] drm-misc-fixes
Date: Fri, 7 Jun 2024 00:09:57 +0200 [thread overview]
Message-ID: <d5645d00-a8cf-47d9-a2a0-4ff55842fc7d@linux.intel.com> (raw)
Hi Dave, Sima,
Lots of fixes for vmwgfx all over the place, and one fix for sitronix panel.
Cheers,
Maarten
drm-misc-fixes-2024-06-07:
drm-misc-fixes for v6.10-rc3:
- Robustness fixes for vmwgfx.
- Error check for of_drm_get_panel_orientation failing in
sitronix-st7789v.
The following changes since commit bb195358806847217efba98de62b7decec3b371f:
drm/msm: remove python 3.9 dependency for compiling msm (2024-05-30
18:49:23 +0200)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/misc/kernel.git
tags/drm-misc-fixes-2024-06-07
for you to fetch changes up to 5703fc058efdafcdd6b70776ee562478f0753acb:
drm/vmwgfx: Don't memcmp equivalent pointers (2024-06-05 22:38:40 -0400)
----------------------------------------------------------------
drm-misc-fixes for v6.10-rc3:
- Robustness fixes for vmwgfx.
- Error check for of_drm_get_panel_orientation failing in
sitronix-st7789v.
----------------------------------------------------------------
Chen Ni (1):
drm/panel: sitronix-st7789v: Add check for
of_drm_get_panel_orientation
Dr. David Alan Gilbert (1):
drm/vmwgfx: remove unused struct 'vmw_stdu_dma'
Ian Forbes (6):
drm/vmwgfx: Filter modes which exceed graphics memory
drm/vmwgfx: 3D disabled should not effect STDU memory limits
drm/vmwgfx: Remove STDU logic from generic mode_valid function
drm/vmwgfx: Standardize use of kibibytes when logging
drm/vmwgfx: Don't destroy Screen Target when CRTC is enabled but
inactive
drm/vmwgfx: Don't memcmp equivalent pointers
drivers/gpu/drm/panel/panel-sitronix-st7789v.c | 4 +-
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 19 +++-----
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 3 --
drivers/gpu/drm/vmwgfx/vmwgfx_gmrid_manager.c | 4 +-
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 28 +++++-------
drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c | 60
+++++++++++++++++++++++---
6 files changed, 74 insertions(+), 44 deletions(-)
next reply other threads:[~2024-06-06 22:09 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 22:09 Maarten Lankhorst [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-20 15:13 [PULL] drm-misc-fixes Thomas Zimmermann
2025-11-13 13:23 Thomas Zimmermann
2025-11-06 13:12 Thomas Zimmermann
2025-10-30 19:56 Thomas Zimmermann
2025-10-31 18:10 ` Simona Vetter
2025-10-23 8:34 Thomas Zimmermann
2025-10-24 11:36 ` Simona Vetter
2025-10-16 14:16 Thomas Zimmermann
2025-10-09 12:00 Thomas Zimmermann
2025-09-25 11:32 Maxime Ripard
2025-09-18 8:24 Maxime Ripard
2025-09-11 16:04 Maxime Ripard
2025-09-03 7:57 Maxime Ripard
2025-08-28 6:32 Maxime Ripard
2025-08-21 8:12 Maxime Ripard
2025-07-23 9:18 Maarten Lankhorst
2025-07-16 7:42 Maarten Lankhorst
2025-07-10 8:59 Maarten Lankhorst
2025-07-11 12:15 ` Simona Vetter
2025-07-03 15:26 Maarten Lankhorst
2025-06-27 7:04 Maarten Lankhorst
2025-06-19 8:12 Maarten Lankhorst
2025-06-12 11:53 Maarten Lankhorst
2025-06-06 7:28 Thomas Zimmermann
2025-06-06 13:03 ` Simona Vetter
2025-05-28 15:35 Thomas Zimmermann
2025-06-06 12:38 ` Simona Vetter
2025-05-22 11:49 Thomas Zimmermann
2025-05-15 12:55 Thomas Zimmermann
2025-05-08 10:49 Thomas Zimmermann
2025-04-30 8:24 Maxime Ripard
2025-04-22 15:12 Thomas Zimmermann
2025-04-17 8:40 Thomas Zimmermann
2025-04-10 12:24 Thomas Zimmermann
2025-03-20 8:38 Maxime Ripard
2025-03-13 7:36 Maxime Ripard
2025-03-06 10:32 Maxime Ripard
2025-02-27 14:10 Maxime Ripard
2025-02-20 8:30 Maxime Ripard
2025-02-13 15:30 Maxime Ripard
2025-02-06 9:15 Maxime Ripard
2025-01-24 8:29 Thomas Zimmermann
2025-01-24 10:42 ` Simona Vetter
2025-01-15 9:22 Maarten Lankhorst
2025-01-02 8:47 Maarten Lankhorst
2024-12-19 18:10 Maarten Lankhorst
2024-12-05 19:48 Maarten Lankhorst
2024-11-28 13:59 Thomas Zimmermann
2024-11-21 13:18 Thomas Zimmermann
2024-11-14 14:22 Thomas Zimmermann
2024-11-08 8:50 Thomas Zimmermann
2024-10-31 14:43 Thomas Zimmermann
2024-10-24 12:49 Thomas Zimmermann
2024-10-17 11:55 Thomas Zimmermann
2024-10-10 13:37 Thomas Zimmermann
2024-10-02 15:15 Thomas Zimmermann
2024-09-26 12:10 Thomas Zimmermann
2024-09-12 8:49 Maxime Ripard
2024-09-05 14:19 Maxime Ripard
2024-08-29 14:51 Maxime Ripard
2024-08-22 12:39 Thomas Zimmermann
2024-08-15 13:17 Thomas Zimmermann
2024-08-08 7:48 Maxime Ripard
2024-08-01 9:00 Maxime Ripard
2024-07-11 9:51 Maarten Lankhorst
2024-07-04 12:27 Maarten Lankhorst
2024-07-04 14:49 ` Daniel Vetter
2024-06-26 15:35 Maarten Lankhorst
2024-06-14 8:13 Maarten Lankhorst
2024-05-30 19:23 Thomas Zimmermann
2024-05-23 18:47 Thomas Zimmermann
2024-05-16 7:26 Thomas Zimmermann
2024-05-10 7:20 Thomas Zimmermann
2024-05-02 19:21 Thomas Zimmermann
2024-04-25 10:24 Thomas Zimmermann
2024-04-18 7:22 Thomas Zimmermann
2024-04-11 7:34 Thomas Zimmermann
2024-04-04 10:48 Thomas Zimmermann
2024-03-28 13:44 Thomas Zimmermann
2024-03-07 8:44 Maxime Ripard
2024-02-29 13:37 Maxime Ripard
2024-02-29 13:54 ` Matthew Auld
2024-03-06 14:26 ` Maxime Ripard
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=d5645d00-a8cf-47d9-a2a0-4ff55842fc7d@linux.intel.com \
--to=maarten.lankhorst@linux.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=mripard@kernel.org \
--cc=ogabbay@kernel.org \
--cc=rodrigo.vivi@intel.com \
--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 NNTP newsgroup(s).