intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: dim-tools@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	Maxime Ripard <mripard@kernel.org>,
	intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PULL] drm-intel-next-fixes
Date: Thu, 18 Feb 2021 17:46:25 -0500	[thread overview]
Message-ID: <YC7uQY1kt6w0tRp+@intel.com> (raw)

Hi Dave and Daniel,

Here goes drm-intel-next-fixes-2021-02-18:

- Restrict DRM_I915_DEBUG to developer builds (Chris)
- Fix return and error codes (Dan)
- Suspend/Resume fix (Chris)
- Disable atomics in L3 for gen9 (Chris)
- Flush before changing register state (Chris)
- Fix for GLK's HDMI (Ville)
- Fix ILK+'s plane strides with Xtiling (Ville)
- Correct surface base address for renderclear (Chris)

Thanks,
Rodrigo.

The following changes since commit 4c3a3292730c56591472717d8c5c0faf74f6c6bb:

  drm/amd/display: fix unused variable warning (2021-02-05 09:49:44 +1000)

are available in the Git repository at:

  git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-fixes-2021-02-18

for you to fetch changes up to 81ce8f04aa96f7f6cae05770f68b5d15be91f5a2:

  drm/i915/gt: Correct surface base address for renderclear (2021-02-17 06:19:04 -0500)

----------------------------------------------------------------
- Restrict DRM_I915_DEBUG to developer builds (Chris)
- Fix return and error codes (Dan)
- Suspend/Resume fix (Chris)
- Disable atomics in L3 for gen9 (Chris)
- Flush before changing register state (Chris)
- Fix for GLK's HDMI (Ville)
- Fix ILK+'s plane strides with Xtiling (Ville)
- Correct surface base address for renderclear (Chris)

----------------------------------------------------------------
Chris Wilson (5):
      drm/i915: Restrict DRM_I915_DEBUG to developer builds
      drm/i915/gem: Move freeze/freeze_late next to suspend/suspend_late
      drm/i915: Disable atomics in L3 for gen9
      drm/i915/gt: Flush before changing register state
      drm/i915/gt: Correct surface base address for renderclear

Dan Carpenter (2):
      drm/i915/gvt: fix uninitialized return in intel_gvt_update_reg_whitelist()
      drm/i915/gem: Fix oops in error handling code

Ville Syrjälä (2):
      drm/i915: Reject 446-480MHz HDMI clock on GLK
      drm/i915: Disallow plane x+w>stride on ilk+ with X-tiling

 drivers/gpu/drm/i915/Kconfig.debug           |  2 ++
 drivers/gpu/drm/i915/display/i9xx_plane.c    | 27 ++++++++++++++++++
 drivers/gpu/drm/i915/display/intel_display.c | 12 ++++----
 drivers/gpu/drm/i915/display/intel_display.h |  6 ++++
 drivers/gpu/drm/i915/display/intel_hdmi.c    |  6 +++-
 drivers/gpu/drm/i915/gem/i915_gem_pm.c       | 41 ++++++++++++++++++++++++++++
 drivers/gpu/drm/i915/gem/i915_gem_pm.h       |  3 ++
 drivers/gpu/drm/i915/gem/i915_gem_stolen.c   | 12 +++-----
 drivers/gpu/drm/i915/gt/gen7_renderclear.c   |  3 +-
 drivers/gpu/drm/i915/gt/intel_workarounds.c  |  8 ++++++
 drivers/gpu/drm/i915/gvt/cmd_parser.c        |  3 +-
 drivers/gpu/drm/i915/i915_drv.c              |  1 +
 drivers/gpu/drm/i915/i915_drv.h              |  2 --
 drivers/gpu/drm/i915/i915_gem.c              | 41 ----------------------------
 drivers/gpu/drm/i915/i915_reg.h              |  7 +++++
 drivers/gpu/drm/i915/selftests/i915_gem.c    |  1 +
 16 files changed, 115 insertions(+), 60 deletions(-)
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2021-02-18 22:46 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18 22:46 Rodrigo Vivi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-08 14:04 [Intel-gfx] [PULL] drm-intel-next-fixes Jani Nikula
2023-11-10 15:48 ` Daniel Vetter
2023-08-31 21:28 Rodrigo Vivi
2023-08-24 12:34 Rodrigo Vivi
2023-07-06  8:24 Tvrtko Ursulin
2023-06-29 10:02 Tvrtko Ursulin
2023-06-21  9:54 Tvrtko Ursulin
2023-05-04 13:01 Joonas Lahtinen
2023-04-27 11:23 Joonas Lahtinen
2023-04-20  8:12 Joonas Lahtinen
2023-04-13 12:12 Joonas Lahtinen
2023-04-13 18:47 ` Daniel Vetter
2023-02-27 10:17 Jani Nikula
2023-02-17 12:24 Jani Nikula
2022-12-15 20:36 Rodrigo Vivi
2022-12-01 16:40 Rodrigo Vivi
2022-10-13 12:56 Tvrtko Ursulin
2022-10-06 10:18 Tvrtko Ursulin
2022-09-29 14:26 Tvrtko Ursulin
2022-08-11 21:03 Rodrigo Vivi
2022-08-04 17:33 Rodrigo Vivi
2022-08-05  8:46 ` Mauro Carvalho Chehab
2022-08-05 14:39   ` Rodrigo Vivi
2022-08-05 15:25     ` Mauro Carvalho Chehab
2022-08-05 20:39       ` Rodrigo Vivi
2022-05-24 13:59 Jani Nikula
2022-03-24  8:44 Tvrtko Ursulin
2022-03-17  7:47 Joonas Lahtinen
2022-03-10  7:58 Joonas Lahtinen
2022-01-20 10:13 Tvrtko Ursulin
2022-01-13  9:33 Tvrtko Ursulin
2022-01-14 13:23 ` Daniel Vetter
2021-11-09 23:17 Rodrigo Vivi
2021-08-26  9:03 Jani Nikula
2021-07-07 15:09 Rodrigo Vivi
2021-06-29 18:54 Rodrigo Vivi
2021-06-30 10:05 ` Jani Nikula
2021-06-30 19:04   ` Rodrigo Vivi
2021-07-01  8:57     ` Jani Nikula
2021-07-01 19:30       ` Rodrigo Vivi
2021-02-25 14:43 Rodrigo Vivi
2020-12-18 15:04 Jani Nikula
2020-12-18 15:42 ` Daniel Vetter
2020-10-22 20:56 Rodrigo Vivi
2020-10-15 18:14 Rodrigo Vivi
2020-10-02 18:26 Rodrigo Vivi
2020-07-30 16:26 Joonas Lahtinen
2020-08-10  7:31 ` Dave Airlie
2020-08-12 12:49   ` Jani Nikula
2020-06-10  9:37 Joonas Lahtinen
2020-06-10 11:19 ` Joonas Lahtinen
2020-06-04 15:04 Joonas Lahtinen
2020-05-28 14:40 Joonas Lahtinen
2020-05-20 12:32 Joonas Lahtinen
2020-04-08 21:59 Rodrigo Vivi
2020-04-02 21:30 Rodrigo Vivi
2020-03-27  8:16 Rodrigo Vivi
2019-12-05  9:24 Joonas Lahtinen
2019-11-28 14:15 Joonas Lahtinen
2019-11-28 14:15 ` [Intel-gfx] " Joonas Lahtinen
2019-11-22 15:55 Joonas Lahtinen
2019-11-22 15:55 ` [Intel-gfx] " Joonas Lahtinen
2019-11-20 20:40 Joonas Lahtinen
2019-11-20 20:40 ` [Intel-gfx] " Joonas Lahtinen
2019-11-22 12:08 ` Joonas Lahtinen
2019-11-22 12:08   ` [Intel-gfx] " Joonas Lahtinen
2019-11-14  8:52 Joonas Lahtinen
2019-11-14  8:52 ` [Intel-gfx] " Joonas Lahtinen
2019-11-07 14:50 Joonas Lahtinen
2019-11-07 14:50 ` [Intel-gfx] " 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=YC7uQY1kt6w0tRp+@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=mripard@kernel.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;
as well as URLs for NNTP newsgroup(s).