From: Jani Nikula <jani.nikula@intel.com> To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel.vetter@ffwll.ch> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>, dim-tools@lists.freedesktop.org, dri-devel@lists.freedesktop.org, Thomas Zimmermann <tzimmermann@suse.de>, Rodrigo Vivi <rodrigo.vivi@intel.com>, intel-gfx@lists.freedesktop.org Subject: [PULL] drm-intel-next-fixes Date: Mon, 27 Feb 2023 12:17:32 +0200 [thread overview] Message-ID: <87cz5v2z0j.fsf@intel.com> (raw) Hi Dave & Daniel - Some more fixes for v6.3-rc1. drm-intel-next-fixes-2023-02-27: drm/i915 fixes for v6.3-rc1: - Don't use stolen memory or BAR mappings for ring buffers with LLC - Add inverted backlight quirk for HP 14-r206nv - Fix GSI offset for MCR lookups - GVT fixes (memleak, debugfs attributes, kconfig, typos) BR, Jani. The following changes since commit 8038510b1fe443ffbc0e356db5f47cbb8678a594: drm/i915: Fix system suspend without fbdev being initialized (2023-02-15 17:33:07 +0200) are available in the Git repository at: git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-fixes-2023-02-27 for you to fetch changes up to 5d2fdb255c52989e95704b5556dbf0ad833bddd2: Merge tag 'gvt-next-fixes-2023-02-23' of https://github.com/intel/gvt-linux into drm-intel-next-fixes (2023-02-23 14:05:43 +0200) ---------------------------------------------------------------- drm/i915 fixes for v6.3-rc1: - Don't use stolen memory or BAR mappings for ring buffers with LLC - Add inverted backlight quirk for HP 14-r206nv - Fix GSI offset for MCR lookups - GVT fixes (memleak, debugfs attributes, kconfig, typos) ---------------------------------------------------------------- Colin Ian King (1): i915/gvt: Fix spelling mistake "vender" -> "vendor" Deepak R Varma (2): drm/i915/gvt: Avoid full proxy f_ops for debugfs attributes drm/i915/gvt: Remove extra semicolon Greg Kroah-Hartman (1): i915: fix memory leak with using debugfs_lookup() Jani Nikula (1): Merge tag 'gvt-next-fixes-2023-02-23' of https://github.com/intel/gvt-linux into drm-intel-next-fixes John Harrison (2): drm/i915: Don't use stolen memory for ring buffers with LLC drm/i915: Don't use BAR mappings for ring buffers with LLC Matt Roper (1): drm/i915/xelpmp: Consider GSI offset when doing MCR lookups Mavroudis Chatzilaridis (1): drm/i915/quirks: Add inverted backlight quirk for HP 14-r206nv Randy Dunlap (1): drm/i915: move a Kconfig symbol to unbreak the menu presentation drivers/gpu/drm/i915/Kconfig | 6 +++--- drivers/gpu/drm/i915/display/intel_quirks.c | 2 ++ drivers/gpu/drm/i915/gt/intel_gt_mcr.c | 5 ++++- drivers/gpu/drm/i915/gt/intel_ring.c | 6 +++--- drivers/gpu/drm/i915/gvt/debugfs.c | 16 ++++++++-------- drivers/gpu/drm/i915/gvt/firmware.c | 2 +- drivers/gpu/drm/i915/gvt/kvmgt.c | 2 +- drivers/gpu/drm/i915/gvt/vgpu.c | 2 +- 8 files changed, 23 insertions(+), 18 deletions(-) -- Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@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>, Thomas Zimmermann <tzimmermann@suse.de>, Rodrigo Vivi <rodrigo.vivi@intel.com>, intel-gfx@lists.freedesktop.org Subject: [Intel-gfx] [PULL] drm-intel-next-fixes Date: Mon, 27 Feb 2023 12:17:32 +0200 [thread overview] Message-ID: <87cz5v2z0j.fsf@intel.com> (raw) Hi Dave & Daniel - Some more fixes for v6.3-rc1. drm-intel-next-fixes-2023-02-27: drm/i915 fixes for v6.3-rc1: - Don't use stolen memory or BAR mappings for ring buffers with LLC - Add inverted backlight quirk for HP 14-r206nv - Fix GSI offset for MCR lookups - GVT fixes (memleak, debugfs attributes, kconfig, typos) BR, Jani. The following changes since commit 8038510b1fe443ffbc0e356db5f47cbb8678a594: drm/i915: Fix system suspend without fbdev being initialized (2023-02-15 17:33:07 +0200) are available in the Git repository at: git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-fixes-2023-02-27 for you to fetch changes up to 5d2fdb255c52989e95704b5556dbf0ad833bddd2: Merge tag 'gvt-next-fixes-2023-02-23' of https://github.com/intel/gvt-linux into drm-intel-next-fixes (2023-02-23 14:05:43 +0200) ---------------------------------------------------------------- drm/i915 fixes for v6.3-rc1: - Don't use stolen memory or BAR mappings for ring buffers with LLC - Add inverted backlight quirk for HP 14-r206nv - Fix GSI offset for MCR lookups - GVT fixes (memleak, debugfs attributes, kconfig, typos) ---------------------------------------------------------------- Colin Ian King (1): i915/gvt: Fix spelling mistake "vender" -> "vendor" Deepak R Varma (2): drm/i915/gvt: Avoid full proxy f_ops for debugfs attributes drm/i915/gvt: Remove extra semicolon Greg Kroah-Hartman (1): i915: fix memory leak with using debugfs_lookup() Jani Nikula (1): Merge tag 'gvt-next-fixes-2023-02-23' of https://github.com/intel/gvt-linux into drm-intel-next-fixes John Harrison (2): drm/i915: Don't use stolen memory for ring buffers with LLC drm/i915: Don't use BAR mappings for ring buffers with LLC Matt Roper (1): drm/i915/xelpmp: Consider GSI offset when doing MCR lookups Mavroudis Chatzilaridis (1): drm/i915/quirks: Add inverted backlight quirk for HP 14-r206nv Randy Dunlap (1): drm/i915: move a Kconfig symbol to unbreak the menu presentation drivers/gpu/drm/i915/Kconfig | 6 +++--- drivers/gpu/drm/i915/display/intel_quirks.c | 2 ++ drivers/gpu/drm/i915/gt/intel_gt_mcr.c | 5 ++++- drivers/gpu/drm/i915/gt/intel_ring.c | 6 +++--- drivers/gpu/drm/i915/gvt/debugfs.c | 16 ++++++++-------- drivers/gpu/drm/i915/gvt/firmware.c | 2 +- drivers/gpu/drm/i915/gvt/kvmgt.c | 2 +- drivers/gpu/drm/i915/gvt/vgpu.c | 2 +- 8 files changed, 23 insertions(+), 18 deletions(-) -- Jani Nikula, Intel Open Source Graphics Center
next reply other threads:[~2023-02-27 10:17 UTC|newest] Thread overview: 129+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-27 10:17 Jani Nikula [this message] 2023-02-27 10:17 ` [Intel-gfx] [PULL] drm-intel-next-fixes Jani Nikula -- strict thread matches above, loose matches on Subject: below -- 2024-01-19 8:30 Joonas Lahtinen 2024-01-19 8:30 ` Joonas Lahtinen 2024-01-11 10:51 Joonas Lahtinen 2024-01-11 10:51 ` Joonas Lahtinen 2023-11-08 14:04 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-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-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-02-25 14:43 Rodrigo Vivi 2021-02-18 22:46 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-22 15:55 Joonas Lahtinen 2019-11-20 20:40 Joonas Lahtinen 2019-11-22 12:08 ` Joonas Lahtinen 2019-11-14 8:52 Joonas Lahtinen 2019-11-07 14:50 Joonas Lahtinen 2019-09-27 19:49 Rodrigo Vivi 2019-09-19 14:16 Rodrigo Vivi 2019-09-11 23:33 Rodrigo Vivi 2019-05-15 7:48 Joonas Lahtinen 2019-05-09 10:01 Joonas Lahtinen 2019-05-02 13:40 Joonas Lahtinen 2019-04-30 7:08 Joonas Lahtinen 2019-04-25 6:13 Joonas Lahtinen 2019-03-12 20:55 Rodrigo Vivi 2018-12-27 7:40 Jani Nikula 2018-10-25 13:18 Joonas Lahtinen 2018-10-19 10:37 Joonas Lahtinen 2018-10-19 12:34 ` Daniel Vetter 2018-10-18 16:57 Joonas Lahtinen 2018-10-18 19:32 ` Daniel Vetter 2018-10-19 6:59 ` Joonas Lahtinen 2018-10-19 7:05 ` Daniel Vetter 2018-10-19 9:41 ` Joonas Lahtinen 2018-10-04 13:37 Joonas Lahtinen 2018-08-24 21:48 Rodrigo Vivi 2018-08-16 19:03 Rodrigo Vivi 2018-08-06 23:30 Rodrigo Vivi 2018-04-19 9:30 Joonas Lahtinen 2018-03-27 14:58 Joonas Lahtinen 2018-03-22 14:35 Joonas Lahtinen 2018-02-07 20:44 Rodrigo Vivi 2018-02-02 0:45 Rodrigo Vivi 2017-11-23 9:34 Jani Nikula 2017-11-10 13:21 Jani Nikula 2017-07-11 13:07 Jani Nikula 2017-06-27 8:28 Daniel Vetter 2017-02-17 9:46 Jani Nikula 2017-02-15 14:06 Jani Nikula 2016-12-22 10:22 Jani Nikula 2016-12-07 19:45 Jani Nikula 2016-10-11 14:09 Jani Nikula 2016-08-05 13:27 Jani Nikula 2016-07-25 6:41 Daniel Vetter 2016-05-25 8:57 Jani Nikula 2016-03-16 11:04 Jani Nikula 2016-01-14 20:06 Jani Nikula 2015-11-06 13:43 Jani Nikula 2015-10-22 8:28 Daniel Vetter 2015-09-02 11:49 Jani Nikula 2015-08-28 12:44 Jani Nikula 2015-08-16 18:13 Daniel Vetter 2015-07-02 11:26 Jani Nikula 2015-06-22 10:33 Jani Nikula 2015-06-18 6:04 Jani Nikula 2015-06-19 3:48 ` Dave Airlie 2015-06-19 15:24 ` Daniel Vetter 2015-06-22 7:59 ` Ander Conselvan De Oliveira 2015-06-22 8:12 ` Jani Nikula 2015-06-22 8:13 ` Dave Airlie 2015-06-11 8:40 Jani Nikula 2015-05-29 17:39 Daniel Vetter 2015-04-24 21:46 Jani Nikula 2015-04-15 12:21 Jani Nikula 2015-02-11 11:09 Jani Nikula 2015-02-11 11:48 ` Daniel Vetter 2014-12-30 12:47 Jani Nikula 2014-12-17 12:16 Jani Nikula 2014-12-11 13:43 Jani Nikula 2014-12-04 9:56 Daniel Vetter
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=87cz5v2z0j.fsf@intel.com \ --to=jani.nikula@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=rodrigo.vivi@intel.com \ --cc=tvrtko.ursulin@linux.intel.com \ --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: linkBe 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.