<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/git/next/linux-next.git/drivers/gpu/drm/xe, branch master</title>
<subtitle>The linux-next integration testing tree</subtitle>
<id>https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/atom?h=master</id>
<link rel='self' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/'/>
<updated>2026-09-17T19:18:01+00:00</updated>
<entry>
<title>Merge branch 'drm-xe-next' of https://gitlab.freedesktop.org/drm/xe/kernel.git</title>
<updated>2026-09-17T19:18:01+00:00</updated>
<author>
<name>Mark Brown</name>
<email>broonie@kernel.org</email>
</author>
<published>2026-09-17T19:18:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=e4750f789aa8f13b55958b927d6863cf97a0450a'/>
<id>urn:sha1:e4750f789aa8f13b55958b927d6863cf97a0450a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'for-linux-next' of https://gitlab.freedesktop.org/drm/i915/kernel.git</title>
<updated>2026-09-17T19:17:59+00:00</updated>
<author>
<name>Mark Brown</name>
<email>broonie@kernel.org</email>
</author>
<published>2026-09-17T19:17:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=b594cdde9a0d4b81fffc74dddd7c4ff6118b7820'/>
<id>urn:sha1:b594cdde9a0d4b81fffc74dddd7c4ff6118b7820</id>
<content type='text'>
# Conflicts:
#	drivers/gpu/drm/i915/display/intel_cursor.c
#	drivers/gpu/drm/i915/display/skl_universal_plane.c
</content>
</entry>
<entry>
<title>Merge branch 'drm-next' of https://gitlab.freedesktop.org/drm/kernel.git</title>
<updated>2026-09-17T16:01:31+00:00</updated>
<author>
<name>Mark Brown</name>
<email>broonie@kernel.org</email>
</author>
<published>2026-09-17T16:01:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=d0679747b6a12cef796cd6a22544ab2936e186f5'/>
<id>urn:sha1:d0679747b6a12cef796cd6a22544ab2936e186f5</id>
<content type='text'>
# Conflicts:
#	drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
#	drivers/gpu/drm/xe/xe_pagefault.c
</content>
</entry>
<entry>
<title>drm/i915/display: stop using the configurable fence timeout</title>
<updated>2026-09-17T12:18:38+00:00</updated>
<author>
<name>Jani Nikula</name>
<email>jani.nikula@intel.com</email>
</author>
<published>2026-09-10T19:42:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=552e0bb24d5e6bf4bee6dcaade3e1c1ca89a6f58'/>
<id>urn:sha1:552e0bb24d5e6bf4bee6dcaade3e1c1ca89a6f58</id>
<content type='text'>
i915 has the Kconfig option DRM_I915_FENCE_TIMEOUT, defaulting to 10
seconds. xe doesn't use it, instead defaulting to
MAX_SCHEDULE_TIMEOUT. Unify the behaviour by switching to
dma_fence_wait() which defaults to MAX_SCHEDULE_TIMEOUT.

As dma_fence_wait() returns 0 when the fence was signaled, update the
return value check.

This should be possible now that commit 3aef9c94c02b ("drm/i915: Perform
full wedge on display reset") has been merged, and we no longer rely on
the timeout.

v3: Try this again with full wedge

v2: Use dma_fence_wait(), fix return value check (Maarten)

Reviewed-by: Maarten Lankhorst &lt;dev@lankhorst.se&gt;
Cc: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Link: https://patch.msgid.link/1880e49c9270049d5dfd944a1cbf712d664d02aa.1789069102.git.jani.nikula@intel.com
Signed-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
</content>
</entry>
<entry>
<title>drm/i915/xe: plug the pme_enabed implementation for xe</title>
<updated>2026-09-16T14:15:02+00:00</updated>
<author>
<name>Vinod Govindapillai</name>
<email>vinod.govindapillai@intel.com</email>
</author>
<published>2026-09-15T09:25:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=e468a2117f413bea664b096b21521c5faa9606ea'/>
<id>urn:sha1:e468a2117f413bea664b096b21521c5faa9606ea</id>
<content type='text'>
Plug the pme_enabled query for xe. It will return the current
PME status for the device. For supported platforms, PME is
enabled during runtime suspend calls if the device is PME is capable.

v2: use the xe_pm_pme_enabled()

Assisted-by: GitHub_Copilot:claude-opus-5
Signed-off-by: Vinod Govindapillai &lt;vinod.govindapillai@intel.com&gt;
Reviewed-by: Jouni Högander &lt;jouni.hogander@intel.com&gt;
Link: https://patch.msgid.link/20260915092518.639448-4-vinod.govindapillai@intel.com
Signed-off-by: Rodrigo Vivi &lt;rodrigo.vivi@intel.com&gt;
</content>
</entry>
<entry>
<title>drm/xe/pm: introduce PM PME support</title>
<updated>2026-09-16T14:15:00+00:00</updated>
<author>
<name>Vinod Govindapillai</name>
<email>vinod.govindapillai@intel.com</email>
</author>
<published>2026-09-15T09:25:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=41dae8ac5a3e1709ccba9dc5bac184826711c03f'/>
<id>urn:sha1:41dae8ac5a3e1709ccba9dc5bac184826711c03f</id>
<content type='text'>
Introduce PME support for PME capable devices. Whether device is
PME capable is assessed during PCI probe routine. And the whether
PME is enabled for a specific context is assessed during the PM
runtime suspend call if the device is PME capable.

If the PME is enabled, HPDs can generate PME which in turn call
the runtime resume call and do the wakeup routines. Till now
the driver was relying on HPD polling to wakeup in case of any
HPDs. HPD polling can be avoided in platforms with PME support
and instead rely on this PCI PME for HPD induced wakeup.

v2: access functions for xe.pme.enabled status and clear the pme.
    enabled in case of error in xe_pm_runtime_suspend()

v3: use the local pme_enabled flag to clear the device wakeup
    incase of error

v4: call the devm_device_init_wakeup() only if device is PME
    capable to avoid false wakeup capable reporting in platforms
    where PME is not supported.
    Squash the patch which handled the lockdep deadlock handling

Bspec: 52979, 52980, 68857, 68867, 68970
Assisted-by: GitHub_Copilot:claude-opus-5
Signed-off-by: Vinod Govindapillai &lt;vinod.govindapillai@intel.com&gt;
Reviewed-by: Jouni Högander &lt;jouni.hogander@intel.com&gt;
Link: https://patch.msgid.link/20260915092518.639448-2-vinod.govindapillai@intel.com
Signed-off-by: Rodrigo Vivi &lt;rodrigo.vivi@intel.com&gt;
</content>
</entry>
<entry>
<title>drm/xe/nvm: add system controller region</title>
<updated>2026-09-16T12:45:32+00:00</updated>
<author>
<name>Alexander Usyskin</name>
<email>alexander.usyskin@intel.com</email>
</author>
<published>2026-09-14T13:18:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=baafc300cd079a5210c1e70e5ea3d93518e40b38'/>
<id>urn:sha1:baafc300cd079a5210c1e70e5ea3d93518e40b38</id>
<content type='text'>
Add region 5 (System Controller) to the list of regions
available on device.

Signed-off-by: Alexander Usyskin &lt;alexander.usyskin@intel.com&gt;
Reviewed-by: Rodrigo Vivi &lt;rodrigo.vivi@intel.com&gt;
Link: https://patch.msgid.link/20260914-nvm_add_sysctl_region-v1-1-75d710daf5d0@intel.com
Signed-off-by: Rodrigo Vivi &lt;rodrigo.vivi@intel.com&gt;
</content>
</entry>
<entry>
<title>drm/xe/pf: Add _locked variant of the fair sched config function</title>
<updated>2026-09-14T16:50:28+00:00</updated>
<author>
<name>Michal Wajdeczko</name>
<email>michal.wajdeczko@intel.com</email>
</author>
<published>2026-09-11T18:32:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=9c8ed392385177546fdd65e4463e292f0f647c6c'/>
<id>urn:sha1:9c8ed392385177546fdd65e4463e292f0f647c6c</id>
<content type='text'>
We will soon want to auto provision all VFs in a single step, while
already holding the master mutex. Split existing function into two.

Signed-off-by: Michal Wajdeczko &lt;michal.wajdeczko@intel.com&gt;
Reviewed-by: Piotr Piórkowski &lt;piotr.piorkowski@intel.com&gt;
Link: https://patch.msgid.link/20260911183257.14999-4-michal.wajdeczko@intel.com
</content>
</entry>
<entry>
<title>drm/xe/pf: Add _locked variant of the release config function</title>
<updated>2026-09-14T16:50:27+00:00</updated>
<author>
<name>Michal Wajdeczko</name>
<email>michal.wajdeczko@intel.com</email>
</author>
<published>2026-09-11T18:32:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=d38c9c9437c802724f0dd1a37ed7fb8f0e34f2fd'/>
<id>urn:sha1:d38c9c9437c802724f0dd1a37ed7fb8f0e34f2fd</id>
<content type='text'>
We will soon want to unprovision all VFs in a single step, while
already holding the master mutex. Split existing function into two.

Signed-off-by: Michal Wajdeczko &lt;michal.wajdeczko@intel.com&gt;
Reviewed-by: Piotr Piórkowski &lt;piotr.piorkowski@intel.com&gt;
Link: https://patch.msgid.link/20260911183257.14999-3-michal.wajdeczko@intel.com
</content>
</entry>
<entry>
<title>drm/xe/pf: Add _locked variant of the priority config function</title>
<updated>2026-09-14T16:50:26+00:00</updated>
<author>
<name>Michal Wajdeczko</name>
<email>michal.wajdeczko@intel.com</email>
</author>
<published>2026-09-11T18:32:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=8968890fcccb6032b1f85afa73850f9b690ee350'/>
<id>urn:sha1:8968890fcccb6032b1f85afa73850f9b690ee350</id>
<content type='text'>
We will soon want to provision VFs in a single step, while already
holding the master mutex. Split existing function into two.

Signed-off-by: Michal Wajdeczko &lt;michal.wajdeczko@intel.com&gt;
Reviewed-by: Piotr Piórkowski &lt;piotr.piorkowski@intel.com&gt;
Link: https://patch.msgid.link/20260911183257.14999-2-michal.wajdeczko@intel.com
</content>
</entry>
</feed>
