<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/gpu/drm/msm/msm_rd.c, branch linux-rolling-stable</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-rolling-stable</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-rolling-stable'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2025-07-05T00:48:37Z</updated>
<entry>
<title>drm/msm: rd dumping support for sparse</title>
<updated>2025-07-05T00:48:37Z</updated>
<author>
<name>Rob Clark</name>
</author>
<published>2025-06-29T20:13:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=06ebb4f043999d42916b78697eebfbc12cc1c0f8'/>
<id>urn:sha1:06ebb4f043999d42916b78697eebfbc12cc1c0f8</id>
<content type='text'>
As with devcoredump, we need to iterate the VMAs to figure out what to
dump.

Signed-off-by: Rob Clark &lt;robdclark@chromium.org&gt;
Signed-off-by: Rob Clark &lt;robin.clark@oss.qualcomm.com&gt;
Tested-by: Antonino Maniscalco &lt;antomani103@gmail.com&gt;
Reviewed-by: Antonino Maniscalco &lt;antomani103@gmail.com&gt;
Patchwork: https://patchwork.freedesktop.org/patch/661510/
</content>
</entry>
<entry>
<title>drm/msm: rd dumping prep for sparse mappings</title>
<updated>2025-07-05T00:48:37Z</updated>
<author>
<name>Rob Clark</name>
</author>
<published>2025-06-29T20:13:09Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4570dbb8a62410862528fe80cebad4ad4fdd9f5e'/>
<id>urn:sha1:4570dbb8a62410862528fe80cebad4ad4fdd9f5e</id>
<content type='text'>
Similar to the previous commit, add support for dumping partial
mappings.

Signed-off-by: Rob Clark &lt;robdclark@chromium.org&gt;
Signed-off-by: Rob Clark &lt;robin.clark@oss.qualcomm.com&gt;
Tested-by: Antonino Maniscalco &lt;antomani103@gmail.com&gt;
Reviewed-by: Antonino Maniscalco &lt;antomani103@gmail.com&gt;
Patchwork: https://patchwork.freedesktop.org/patch/661514/
</content>
</entry>
<entry>
<title>[tree-wide] finally take no_llseek out</title>
<updated>2024-09-27T15:18:43Z</updated>
<author>
<name>Al Viro</name>
</author>
<published>2024-09-27T01:56:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=cb787f4ac0c2e439ea8d7e6387b925f74576bdf8'/>
<id>urn:sha1:cb787f4ac0c2e439ea8d7e6387b925f74576bdf8</id>
<content type='text'>
no_llseek had been defined to NULL two years ago, in commit 868941b14441
("fs: remove no_llseek")

To quote that commit,

  At -rc1 we'll need do a mechanical removal of no_llseek -

  git grep -l -w no_llseek | grep -v porting.rst | while read i; do
	sed -i '/\&lt;no_llseek\&gt;/d' $i
  done

  would do it.

Unfortunately, that hadn't been done.  Linus, could you do that now, so
that we could finally put that thing to rest? All instances are of the
form
	.llseek = no_llseek,
so it's obviously safe.

Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>drm/msm: don't create GPU-related debugfs files with no GPU present</title>
<updated>2023-11-21T02:31:42Z</updated>
<author>
<name>Dmitry Baryshkov</name>
</author>
<published>2023-10-10T05:54:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f6afe4f09f6605b725b39670b3568ab2927c9b43'/>
<id>urn:sha1:f6afe4f09f6605b725b39670b3568ab2927c9b43</id>
<content type='text'>
If there is no GPU present, skip creation of the GPU-related debugfs
files, making the MSM's debugfs more usable.

Signed-off-by: Dmitry Baryshkov &lt;dmitry.baryshkov@linaro.org&gt;
Patchwork: https://patchwork.freedesktop.org/patch/561742/
Signed-off-by: Rob Clark &lt;robdclark@chromium.org&gt;
</content>
</entry>
<entry>
<title>drm/msm: Use drm_gem_object in submit bos table</title>
<updated>2023-08-10T17:44:02Z</updated>
<author>
<name>Rob Clark</name>
</author>
<published>2023-08-02T22:21:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6ba5daa5d5ad54b78aeac8912092f986e8d4c38f'/>
<id>urn:sha1:6ba5daa5d5ad54b78aeac8912092f986e8d4c38f</id>
<content type='text'>
Basically everywhere wants the base ptr type.  So store that instead of
msm_gem_object.

Signed-off-by: Rob Clark &lt;robdclark@chromium.org&gt;
Patchwork: https://patchwork.freedesktop.org/patch/551021/
</content>
</entry>
<entry>
<title>drm/msm: Move cmdstream dumping out of sched kthread</title>
<updated>2023-06-10T13:46:12Z</updated>
<author>
<name>Rob Clark</name>
</author>
<published>2023-04-17T22:55:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=171f580e32096e0cbd19e458d704b9330197d627'/>
<id>urn:sha1:171f580e32096e0cbd19e458d704b9330197d627</id>
<content type='text'>
This is something that can block for arbitrary amounts of time as
userspace consumes from the FIFO.  So we don't really want this to
be in the fence signaling path.

Signed-off-by: Rob Clark &lt;robdclark@chromium.org&gt;
Patchwork: https://patchwork.freedesktop.org/patch/532617/
</content>
</entry>
<entry>
<title>drm/msm/rd: Fix FIFO-full deadlock</title>
<updated>2022-08-15T17:19:53Z</updated>
<author>
<name>Rob Clark</name>
</author>
<published>2022-08-07T16:09:01Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=174974d8463b77c2b4065e98513adb204e64de7d'/>
<id>urn:sha1:174974d8463b77c2b4065e98513adb204e64de7d</id>
<content type='text'>
If the previous thing cat'ing $debugfs/rd left the FIFO full, then
subsequent open could deadlock in rd_write() (because open is blocked,
not giving a chance for read() to consume any data in the FIFO).  Also
it is generally a good idea to clear out old data from the FIFO.

Signed-off-by: Rob Clark &lt;robdclark@chromium.org&gt;
Patchwork: https://patchwork.freedesktop.org/patch/496706/
Link: https://lore.kernel.org/r/20220807160901.2353471-2-robdclark@gmail.com
</content>
</entry>
<entry>
<title>drm/msm: Add support for pointer params</title>
<updated>2022-04-21T22:01:08Z</updated>
<author>
<name>Rob Clark</name>
</author>
<published>2022-03-17T16:51:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4bfba71640f8578b3daadb551d6bce12a2d436d8'/>
<id>urn:sha1:4bfba71640f8578b3daadb551d6bce12a2d436d8</id>
<content type='text'>
The 64b value field is already suffient to hold a pointer instead of
immediate, but we also need a length field.

Signed-off-by: Rob Clark &lt;robdclark@chromium.org&gt;
Link: https://lore.kernel.org/r/20220317165144.222101-2-robdclark@gmail.com
Signed-off-by: Rob Clark &lt;robdclark@chromium.org&gt;
</content>
</entry>
<entry>
<title>drm/msm/gpu: Add ctx to get_param()</title>
<updated>2022-02-20T17:44:43Z</updated>
<author>
<name>Rob Clark</name>
</author>
<published>2022-02-01T16:16:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f98f915b7e0f83fd108bcf716c77f316ee27f484'/>
<id>urn:sha1:f98f915b7e0f83fd108bcf716c77f316ee27f484</id>
<content type='text'>
Prep work for next patch.

Signed-off-by: Rob Clark &lt;robdclark@chromium.org&gt;
Link: https://lore.kernel.org/r/20220201161618.778455-2-robdclark@gmail.com
Reviewed-by: Emma Anholt &lt;emma@anholt.net&gt;
Signed-off-by: Rob Clark &lt;robdclark@chromium.org&gt;
</content>
</entry>
<entry>
<title>drm/msm/rd: Add chip-id</title>
<updated>2022-02-18T15:32:52Z</updated>
<author>
<name>Rob Clark</name>
</author>
<published>2022-01-14T18:57:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=cfdc428d81a06d1b14dcbbe7aad285e076c9b917'/>
<id>urn:sha1:cfdc428d81a06d1b14dcbbe7aad285e076c9b917</id>
<content type='text'>
For newer devices which deprecate gpu-id and do matching based on
chip-id, we need this information in cmdstream dumps so that the
decoding tools know how to decode them.

Signed-off-by: Rob Clark &lt;robdclark@chromium.org&gt;
Reviewed-by: Dmitry Baryshkov &lt;dmitry.baryshkov@linaro.org&gt;
Link: https://lore.kernel.org/r/20220114185742.283539-1-robdclark@gmail.com
Signed-off-by: Dmitry Baryshkov &lt;dmitry.baryshkov@linaro.org&gt;
</content>
</entry>
</feed>
