<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/gpu/drm/i915/soc, branch linux-rolling-lts</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-rolling-lts</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-rolling-lts'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2025-09-09T06:32:01Z</updated>
<entry>
<title>drm/i915/display: add intel_display_device_present()</title>
<updated>2025-09-09T06:32:01Z</updated>
<author>
<name>Jani Nikula</name>
</author>
<published>2025-09-03T09:04:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f985e105ced10304abd3b2d822994b87c88145f8'/>
<id>urn:sha1:f985e105ced10304abd3b2d822994b87c88145f8</id>
<content type='text'>
Add a proper function for display &amp;&amp; HAS_DISPLAY(display) to hide
indirect struct intel_display access via the macro from a number of
places outside of display. This makes struct intel_display * an opaque
pointer in these places. All HAS_DISPLAY() usage is now constrained
within display.

Reviewed-by: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Link: https://lore.kernel.org/r/20250903090408.3492875-1-jani.nikula@intel.com
Signed-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
</content>
</entry>
<entry>
<title>drm/i915/dram: Print memory details even if something went wrong</title>
<updated>2025-09-05T11:37:32Z</updated>
<author>
<name>Ville Syrjälä</name>
</author>
<published>2025-09-02T13:31:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0d4a57f08b8320f7f65b54e4ff3ca1f55c6d70b1'/>
<id>urn:sha1:0d4a57f08b8320f7f65b54e4ff3ca1f55c6d70b1</id>
<content type='text'>
Print the memory details even if the detection failed in some way
but we continued the driver initialization anyway. It'll be easier
to debug issues if we at least know what the final results were.

And while at it also print the number of PSF GV points. Previously
we only printed the QGV points.

Signed-off-by: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20250902133113.18778-9-ville.syrjala@linux.intel.com
Reviewed-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
</content>
</entry>
<entry>
<title>drm/i915/dram: Don't call skl_get_dram_info()/skl_get_dram_type() on icl</title>
<updated>2025-09-05T11:37:32Z</updated>
<author>
<name>Ville Syrjälä</name>
</author>
<published>2025-09-02T13:31:12Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a6d31e18c01211b041d416661b9ccfd75475e01b'/>
<id>urn:sha1:a6d31e18c01211b041d416661b9ccfd75475e01b</id>
<content type='text'>
Currently the icl codepaths first determine the memory type from the
memory controller registers (via skl_get_dram_info()-&gt;skl_get_dram_type())
and then overwrite the results with icl_pcode_read_mem_global_info().
Get rid of the pointless (and potentially incorrect) skl_get_dram_type()
stuff.

Signed-off-by: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20250902133113.18778-8-ville.syrjala@linux.intel.com
Reviewed-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
</content>
</entry>
<entry>
<title>drm/i915/dram: Move 16Gb DIMM detection fully to the skl/icl codepaths</title>
<updated>2025-09-05T11:37:32Z</updated>
<author>
<name>Ville Syrjälä</name>
</author>
<published>2025-09-02T13:31:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=84b72b545c0fe1fc3ecbe80a499f27da1de9a9e5'/>
<id>urn:sha1:84b72b545c0fe1fc3ecbe80a499f27da1de9a9e5</id>
<content type='text'>
We are incorrectly applying the 16Gb DIMM w/a (adding 1 extra
usec to WM0 latency) on MTL+ even though the w/a is only needed
for SKL/ICL.

The current way of setting this is up is a bit of a disaster:
1. always set has_16gb_dimms=true for all platforms except BXT/GLK
2. has_16gb_dimms potentially gets overwritten with something else
 * BXT/GLK don't do anything since we never set has_16gb_dimms to
   begin with
 * skl_get_dram_info() overwrites has_16gb_dimms with the actual
   detection results for SKL/ICL/derivatives
 * gen12_get_dram_info() (correctly) resets has_16gb_dimms
   for TGL/ADL/derivatives
 * xelpdp_get_dram_info() doesn't do anything, leaving
   has_16gb_dimms incorrectly set for MTL+

Clean up the whole mess by only setting has_16gb_dimms in the
SKL/ICL codepaths where we have the actual detection code for
it. This avois applying the w/a incorrectly on MTL+.

v2: Rewrite commit msg (Jani)

Signed-off-by: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20250902133113.18778-6-ville.syrjala@linux.intel.com
Reviewed-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
</content>
</entry>
<entry>
<title>drm/i915/dram: s/wm_lv0.../has_16gb_dimms/</title>
<updated>2025-09-05T11:37:32Z</updated>
<author>
<name>Ville Syrjälä</name>
</author>
<published>2025-09-02T13:31:09Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=115cebc303db60ed7df85366aa10ef2a1780e3b1'/>
<id>urn:sha1:115cebc303db60ed7df85366aa10ef2a1780e3b1</id>
<content type='text'>
The DRAM code shouldn't know anything about watermarks. Rename
wm_lv_0_adjust_needed to has_16gb_dimms. How this gets used is
up to the watermark code.

Signed-off-by: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20250902133113.18778-5-ville.syrjala@linux.intel.com
Reviewed-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
</content>
</entry>
<entry>
<title>drm/i915/dram: Pack dram_info better</title>
<updated>2025-09-05T11:37:32Z</updated>
<author>
<name>Ville Syrjälä</name>
</author>
<published>2025-09-02T13:31:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=da548f7e781d3abc6ecbc08cc8b18ffaa3211653'/>
<id>urn:sha1:da548f7e781d3abc6ecbc08cc8b18ffaa3211653</id>
<content type='text'>
struct dram_info has two holes in the middle. Shuffle things
around to plug them.

Signed-off-by: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20250902133113.18778-4-ville.syrjala@linux.intel.com
Reviewed-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
</content>
</entry>
<entry>
<title>drm/i915/dram: Use intel_dram_type_str() for pnv</title>
<updated>2025-09-05T11:37:32Z</updated>
<author>
<name>Ville Syrjälä</name>
</author>
<published>2025-09-02T13:31:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=413439008ca409da8d46957cf598a125aa32fdd4'/>
<id>urn:sha1:413439008ca409da8d46957cf598a125aa32fdd4</id>
<content type='text'>
Replace the hand rolled PNV memory type printk string
stuff with intel_dram_type_str().

Signed-off-by: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20250902133113.18778-3-ville.syrjala@linux.intel.com
Reviewed-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
</content>
</entry>
<entry>
<title>drm/i915/dram: Populate PNV memory type accurately</title>
<updated>2025-09-05T11:37:32Z</updated>
<author>
<name>Ville Syrjälä</name>
</author>
<published>2025-09-02T13:31:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3a64c199634457f0e159690510321e4778fb45a0'/>
<id>urn:sha1:3a64c199634457f0e159690510321e4778fb45a0</id>
<content type='text'>
If PNV doesn't have DDR3 then it has DDR2. Add the appropriate memory
type for it.

No functional change since we currently only care about the
DDR3 vs. not difference.

Signed-off-by: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20250902133113.18778-2-ville.syrjala@linux.intel.com
Reviewed-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
</content>
</entry>
<entry>
<title>drm/i915/dram: move fsb_freq and mem_freq to dram info</title>
<updated>2025-08-19T08:20:40Z</updated>
<author>
<name>Jani Nikula</name>
</author>
<published>2025-08-18T10:07:28Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0492e13eb819008e0ce7570a7e152559e9a89a4e'/>
<id>urn:sha1:0492e13eb819008e0ce7570a7e152559e9a89a4e</id>
<content type='text'>
Store fsb_freq and mem_freq in dram info the same way we do for other
memory info on later platforms for a slightly more unified approach.

This allows us to remove fsb_freq, mem_freq and is_ddr3 members from
struct drm_i915_private and struct xe_device.

Reviewed-by: Rodrigo Vivi &lt;rodrigo.vivi@intel.com&gt;
Link: https://lore.kernel.org/r/a38c4b105ba9098fa0b128cb86cd4eb63bcc27e8.1755511595.git.jani.nikula@intel.com
Signed-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
</content>
</entry>
<entry>
<title>drm/i915/dram: bypass fsb/mem freq detection on dg2 and no display</title>
<updated>2025-08-19T08:20:40Z</updated>
<author>
<name>Jani Nikula</name>
</author>
<published>2025-08-18T10:07:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=10e656f8c4a6b99f905bf024712c4d56882bb6a9'/>
<id>urn:sha1:10e656f8c4a6b99f905bf024712c4d56882bb6a9</id>
<content type='text'>
Non-display now calls the intel_fsb_freq() and intel_mem_freq()
functions, so we don't have to have the frequencies initialized for dg2
or non-display cases.

This is in preparation for unifying the pre-gen9 handling in dram info.

DG2 remains a special case as described in commit 5eb6bf0b44e7
("drm/i915/dg2: Don't read DRAM info").

v2: Rebase

Reviewed-by: Rodrigo Vivi &lt;rodrigo.vivi@intel.com&gt;
Link: https://lore.kernel.org/r/7bfed06d431354f3918ea73d43a2ec8ed9426a76.1755511595.git.jani.nikula@intel.com
Signed-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
</content>
</entry>
</feed>
