Panfrost heap BOs grow on demand when the GPU triggers a page fault after
accessing an address within the BO's virtual range.
We still store the sgts we get back from the shmem sparse allocation function,
since it was decided management of sparse memory SGTs should be done by client
drivers rather
Because of the alternative definition of the 'pages' field in shmem after adding
support for sparse allocations, the logic for deciding whether pages are
available must be expanded.
Signed-off-by: Adrián Larumbe
---
drivers/gpu/drm/panfrost/panfrost_gem.c | 4 +++-
drivers/gpu/drm/panthor/pantho
Switch to sg_alloc_table_from_page_array_segment() when generating an sgtable
from an array of pages. This is functionally equivalent, but a future commit
will also let us do the same from a memory page xarray.
Signed-off-by: Adrián Larumbe
---
drivers/gpu/drm/drm_prime.c | 7 ---
1 file cha
Add a new function that lets drivers allocate pages for a subset of the shmem
object's virtual address range. Expand the shmem object's definition to include
an RSS field, since it's different from the base GEM object's virtual size.
Add also new function for putting the pages of a sparse page arr
On 2/18/25 5:21 PM, Alexandre Courbot wrote:
On Wed Feb 19, 2025 at 5:51 AM JST, Timur Tabi wrote:
On Tue, 2025-02-18 at 22:16 +0900, Alexandre Courbot wrote:
...
More likely this would be something like:
let SplitU64 { high: some_u32, .. } = some_u64;
Which is still a bit verbose, but a
On 19-02-2025 08:35, Matthew Brost wrote:
On Wed, Feb 19, 2025 at 08:29:53AM +0530, Ghimiray, Himal Prasad wrote:
On 19-02-2025 03:24, Matthew Brost wrote:
On Thu, Feb 13, 2025 at 11:58:27PM +0530, Ghimiray, Himal Prasad wrote:
On 13-02-2025 07:41, Matthew Brost wrote:
Migration is imp
On Tue, Feb 18, 2025 at 11:03:53AM +0100, Jacek Lawrynowicz wrote:
> From: Tomasz Rusinowicz
>
> The `struct ttm_resource->placement` contains TTM_PL_FLAG_* flags, but
> it was incorrectly tested for XE_PL_* flags.
> This caused xe_dma_buf_pin() to always fail when invoked for
> the second time.
From: Michael Kelley
Gen 2 Hyper-V VMs boot via EFI and have a standard EFI framebuffer
device. When the kdump kernel runs in such a VM, loading the efifb
driver may hang because of accessing the framebuffer at the wrong
memory address.
The scenario occurs when the hyperv_fb driver in the origin
Hi,
On 2/18/25 6:05 PM, Sebastian Reichel wrote:
> Hi,
>
> On Tue, Feb 18, 2025 at 03:53:06PM +0100, Heiko Stübner wrote:
>> Am Dienstag, 18. Februar 2025, 15:13:07 MEZ schrieb Sebastian Reichel:
>>> On Tue, Feb 18, 2025 at 08:17:46PM +0800, Jianfeng Liu wrote:
On Tue, 18 Feb 2025 11:00:57 +
From: Saurabh Sengar Sent: Saturday, February 15,
2025 1:21 AM
>
> When a Hyper-V framebuffer device is unbind, hyperv_fb driver tries to
> release the framebuffer forcefully. If this framebuffer is in use it
> produce the following WARN and hence this framebuffer is never released.
>
> [ 44.
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on lee-leds/for-leds-next]
[also build test WARNING on linus/master v6.14-rc3 next-20250218]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use
From: Shixiong Ou
1. The device_remove_file() need to be called when driver is removing.
2. The device_remove_file() need to be called if the call to
device_create_file() fails.
Signed-off-by: Shixiong Ou
---
v1->v2:
add missing 'return error'.
call device_remove_file() in sh
On Sat, Feb 8, 2025, at 10:29, oushixiong1...@163.com wrote:
> From: Shixiong Ou
>
> 1. The device_remove_file() need to be called when driver is removing.
> 2. The device_remove_file() need to be called if the call to
>device_create_file() fails.
This should probably use device_add_group() i
Hi
Am 18.02.25 um 14:49 schrieb Aditya Garg:
[...]
This code runs in the middle of the atomic update. It's then too late to do
error handling. If these allocs fail, the display hardware will remain in
undefined state.
It is much preferable to allocate this memory in the atomic_check. To do so
On Tue, 2025-02-18 at 14:17 -0800, Matthew Brost wrote:
> On Tue, Feb 18, 2025 at 06:26:15PM +, Tvrtko Ursulin wrote:
> >
> > On 18/02/2025 12:26, Philipp Stanner wrote:
> > > Thx for the updated version. Overlooked it, I was out on Friday.
> > > See
> > > below
> > >
> > > On Fri, 2025-02-14
Hi Jonathan,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-xe/drm-xe-next]
[also build test ERROR on next-20250218]
[cannot apply to linus/master v6.14-rc3]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we
On Wed, Feb 12, 2025 at 06:10:43PM -0800, Matthew Brost wrote:
> Avoid multiple CPU page faults to the same device page racing by trying
> to lock the page in do_swap_page before taking an extra reference to the
> page. This prevents scenarios where multiple CPU page faults each take
> an extra ref
On Wed, Feb 19, 2025 at 04:36:54PM +1100, Alistair Popple wrote:
> On Wed, Feb 12, 2025 at 06:10:43PM -0800, Matthew Brost wrote:
> > Avoid multiple CPU page faults to the same device page racing by trying
> > to lock the page in do_swap_page before taking an extra reference to the
> > page. This p
On Tue, Feb 18, 2025 at 10:08:31PM -0800, Matthew Brost wrote:
> On Wed, Feb 19, 2025 at 04:36:54PM +1100, Alistair Popple wrote:
> > On Wed, Feb 12, 2025 at 06:10:43PM -0800, Matthew Brost wrote:
> > > Avoid multiple CPU page faults to the same device page racing by trying
> > > to lock the page i
Sparse DRM objects will store their backing pages in an xarray, to avoid the
overhead of preallocating a huge struct page pointer array when only a very
small range of indices might be assigned.
For now, only the definition of a sparse object as a union alternative to a
'dense' object is provided,
This patch series is a proposal for implementing sparse page allocations
for shmem objects. It was initially motivated by a kind of BO managed by
the Panfrost driver, the tiler heap, which grows on demand every time the
GPU faults on a virtual address within its drm_mm-managed ranged.
Because keep
With the future goal of preventing deadlocks with the shrinker when reclaiming
GEM-allocated memory, a variant of shmem_read_mapping_page_gfp() that does not
sleep when enough memory isn't available, therefore potentially triggering the
shrinker on same driver, is introduced.
Signed-off-by: Adrián
In preparation for a future commit that will introduce sparse allocation of
pages in DRM shmem, a scatterlist function that knows how to deal with an xarray
collection of memory pages had to be introduced.
Because the new function is identical to the existing one that deals with a page
array, the
On Wed Feb 19, 2025 at 5:51 AM JST, Timur Tabi wrote:
> On Tue, 2025-02-18 at 22:16 +0900, Alexandre Courbot wrote:
>> > A proper struct with `high` and `low` might be more verbose, but
>> > it rules out this issue.
>>
>> Mmm indeed, so we would have client code looking like:
>>
>> let SplitU64
On 19-02-2025 03:24, Matthew Brost wrote:
On Thu, Feb 13, 2025 at 11:58:27PM +0530, Ghimiray, Himal Prasad wrote:
On 13-02-2025 07:41, Matthew Brost wrote:
Migration is implemented with range granularity, with VRAM backing being
a VM private TTM BO (i.e., shares dma-resv with VM). The life
On Wed, Feb 19, 2025 at 08:29:53AM +0530, Ghimiray, Himal Prasad wrote:
>
>
> On 19-02-2025 03:24, Matthew Brost wrote:
> > On Thu, Feb 13, 2025 at 11:58:27PM +0530, Ghimiray, Himal Prasad wrote:
> > >
> > >
> > > On 13-02-2025 07:41, Matthew Brost wrote:
> > > > Migration is implemented with r
On Wed, 19 Feb 2025 at 07:39, Luis Chamberlain wrote:
>
> On Tue, Feb 18, 2025 at 06:24:43PM +0100, Danilo Krummrich wrote:
> > On Tue, Feb 18, 2025 at 06:28:53AM -0800, Luis Chamberlain wrote:
> > >
> > > What I recommend is to look into why we disable it by default, I think
> >
> > I think FW_CA
On Tue, Feb 18, 2025 at 06:26:15PM +, Tvrtko Ursulin wrote:
>
> On 18/02/2025 12:26, Philipp Stanner wrote:
> > Thx for the updated version. Overlooked it, I was out on Friday. See
> > below
> >
> > On Fri, 2025-02-14 at 10:19 +, Tvrtko Ursulin wrote:
> > > Idea is to add helpers for peek
A page fault occurs when running the IGT test:
amdgpu@amd_vrr_range@freesync-parsing-suspend with MST. Fix that by
skipping handling a stream state when stream is NULL when setting DPMS
off.
[ +7.435304] [drm] DM_MST: stopping TM on aconnector: 951db0f4 [id:
101]
[ +0.535828] BUG: unabl
On Friday, 14 February 2025 06:28:00 CST Mike Lothian wrote:
> This allows ntsync to be usuable by non-root processes out of the box
>
> Signed-off-by: Mike Lothian
> ---
> drivers/misc/ntsync.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/misc/ntsync.c b/drivers/misc/ntsync
On Thu, 13 Feb 2025 21:40:05 +0530, Akhil P Oommen wrote:
> This series adds support for A623 GPU found in QCS8300 chipsets. This
> GPU IP is very similar to A621 GPU, except for the UBWC configuration
> and the GMU firmware.
>
> Both DT patches are for Bjorn and rest of the patches for Rob Clar
On 18-02-2025 21:48, Pekka Paalanen wrote:
On Tue, 18 Feb 2025 11:13:39 +0530
"Murthy, Arun R" wrote:
On 17-02-2025 15:38, Pekka Paalanen wrote:
Hi Arun,
this whole series seems to be missing all the UAPI docs for the DRM
ReST files, e.g. drm-kms.rst. The UAPI header doc comments are not a
r
On Mon, Feb 10, 2025 at 10:49:54PM +0800, Yongbang Shi wrote:
From: Baihan Li
Add dp serdes cfg in link training process, and related adapting
and modificating. We change some init values about training,
Imperative language, please. Use 'change', not 'we change'.
because we want completely t
Hi Ian,
On Mon, Feb 10, 2025 at 11:17:27PM -0800, Ian Rogers wrote:
> DRM clients expose information through usage stats as documented in
> Documentation/gpu/drm-usage-stats.rst (available online at
> https://docs.kernel.org/gpu/drm-usage-stats.html). Add a tool like
> PMU, similar to the hwmon PM
On Mon, Feb 10, 2025 at 10:49:56PM +0800, Yongbang Shi wrote:
From: Baihan Li
This is a DP IP controller's feature. It can be used as a debug method
which can check DP controller is working good. The colorbar displaying
doesn't rely on other IPs work in the chip, like: GPU or DDR (vram) and
so
在 2025/2/19 14:47, Arnd Bergmann 写道:
On Sat, Feb 8, 2025, at 10:29, oushixiong1...@163.com wrote:
From: Shixiong Ou
1. The device_remove_file() need to be called when driver is removing.
2. The device_remove_file() need to be called if the call to
device_create_file() fails.
This should
On Mon, Feb 10, 2025 at 10:49:58PM +0800, Yongbang Shi wrote:
From: Baihan Li
We use the previous two patches as our debug functions and
generate two files. "hibmc-dp" and "color-bar".
hibmc-dp: read only, print the dp link status and dpcd version
Please define a generic DP attribute for this,
Hi
Am 18.02.25 um 21:12 schrieb Aditya Garg:
Hi
In continuation to my previous mail.
+
+static int appletbdrm_send_msg(struct appletbdrm_device *adev, u32 msg)
+{
+ struct appletbdrm_msg_simple_request *request;
+ int ret;
+
+ request = kzalloc(sizeof(*request), GFP_KERNEL);
+ if (!request)
+
On Thu, Feb 13, 2025 at 11:05:39PM +0530, Pranav Tyagi wrote:
> Hi,
>
> Just a gentle follow-up on this patch. It has been reviewed but hasn't
> been applied yet.
You may need to resend the patch, but with scripts/get_maintainer.pl
output Cc'ed so that DRM maintainers can be notified on the patch
On 2/17/2025 8:33 AM, Jacek Lawrynowicz wrote:
Hi,
On 2/14/2025 5:49 PM, Jeffrey Hugo wrote:
On 2/4/2025 1:46 AM, Jacek Lawrynowicz wrote:
From: Andrzej Kacprowski
Increment the runtime PM counter when entering
ivpu_context_abort_work_fn() to prevent the device
from suspending while the func
On 2/17/2025 8:26 AM, Jacek Lawrynowicz wrote:
Hi,
On 2/14/2025 5:41 PM, Jeffrey Hugo wrote:
On 2/4/2025 1:46 AM, Jacek Lawrynowicz wrote:
From: Andrzej Kacprowski
Multiple threads were accessing mmu cmd queue simultaneously
causing sporadic failures in ivpu_mmu_cmdq_sync() function.
Protect
On 1/22/25 19:23, Marijn Suijten wrote:
Some SoCs such as SC7280 (used in the Fairphone 5) have only a single
DSC "hard slice" encoder. The current hardcoded use of 2:2:1 topology
(2 LM and 2 DSC for a single interface) make it impossible to use
Display Stream Compression panels with mainline, w
Create a default subgroup at /config/vkms/planes/plane/possible_crtcs
that will contain symbolic links to the possible CRTCs for the plane.
Co-developed-by: Louis Chauvet
Signed-off-by: Louis Chauvet
Signed-off-by: José Expósito
---
Documentation/gpu/vkms.rst | 9
drivers/gpu/d
Create a default subgroup at /config/vkms/planes to allow to create as
many planes as required.
Co-developed-by: Louis Chauvet
Signed-off-by: Louis Chauvet
Signed-off-by: José Expósito
---
Documentation/gpu/vkms.rst | 16 -
drivers/gpu/drm/vkms/vkms_configfs.c | 101
When a plane is created, add a `type` file to allow to set the type:
- 0 overlay
- 1 primary
- 2 cursor
Co-developed-by: Louis Chauvet
Signed-off-by: Louis Chauvet
Signed-off-by: José Expósito
---
Documentation/gpu/vkms.rst | 4 +++
drivers/gpu/drm/vkms/vkms_configfs.c | 51
Implement the drm_connector_funcs.detect() callback to update the
connector status by returning the status stored in the configuration.
Signed-off-by: José Expósito
---
drivers/gpu/drm/vkms/vkms_connector.c | 19 ++-
drivers/gpu/drm/vkms/vkms_connector.h | 12 +++-
driver
Create a default subgroup at
/config/vkms/connectors to allow to create as many connectors as
required.
Co-developed-by: Louis Chauvet
Signed-off-by: Louis Chauvet
Signed-off-by: José Expósito
---
Documentation/gpu/vkms.rst | 6 ++
drivers/gpu/drm/vkms/vkms_configfs.c | 100 +++
When a connector is created, add a `status` file to allow to update the
connector status to:
- 1 connector_status_connected
- 2 connector_status_disconnected
- 3 connector_status_unknown
If the device is enabled, updating the status hot-plug or unplugs the
connector.
Signed-off-by: José Expós
Allow to store the connector status in vkms_config_connector and add a
getter and a setter functions as well a KUnit test.
This change only adds the configuration, the connector status is not
used yet.
Signed-off-by: José Expósito
---
drivers/gpu/drm/vkms/tests/vkms_config_test.c | 24 +
Create a default subgroup at /config/vkms/encoders to allow to create as
many encoders as required.
Co-developed-by: Louis Chauvet
Signed-off-by: Louis Chauvet
Signed-off-by: José Expósito
---
Documentation/gpu/vkms.rst | 6 ++
drivers/gpu/drm/vkms/vkms_configfs.c | 99 +
Create a default subgroup at
/config/vkms/encoders/encoder/possible_crtcs that will contain symbolic
links to the possible CRTCs for the encoder.
Co-developed-by: Louis Chauvet
Signed-off-by: Louis Chauvet
Signed-off-by: José Expósito
---
Documentation/gpu/vkms.rst | 2 +
drivers/gp
Remove the configfs related TODO items from the "Runtime Configuration"
section.
Signed-off-by: José Expósito
---
Documentation/gpu/vkms.rst | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/Documentation/gpu/vkms.rst b/Documentation/gpu/vkms.rst
index 3068879ce1fc..0a5
Hi everyone,
This series, to be applied on top of [1], allow to configure one or more VKMS
instances without having to reload the driver using configfs.
The series is structured in 3 blocks:
- Patches 1..11: Basic device configuration. For simplicity, I kept the
available options as minima
On Fri, Feb 14, 2025 at 08:29:22AM +0200, Svyatoslav Ryhel wrote:
> чт, 13 лют. 2025 р. о 22:34 Conor Dooley пише:
> >
> > On Thu, Feb 13, 2025 at 03:56:04PM +0200, Svyatoslav Ryhel wrote:
> > > Add bindings for Solomon SSD2825 MIPI master bridge chip that connects an
> > > application processor w
When a CRTC is created, add a `writeback` file to allow to enable or
disable writeback connector support
Co-developed-by: Louis Chauvet
Signed-off-by: Louis Chauvet
Signed-off-by: José Expósito
---
Documentation/gpu/vkms.rst | 4 +++
drivers/gpu/drm/vkms/vkms_configfs.c | 47 +++
Create a default subgroup at /config/vkms/crtcs to allow to create as
many CRTCs as required.
Co-developed-by: Louis Chauvet
Signed-off-by: Louis Chauvet
Signed-off-by: José Expósito
---
Documentation/gpu/vkms.rst | 6 ++
drivers/gpu/drm/vkms/vkms_configfs.c | 98 +++
Add a new module param to allow to create or not the default VKMS
instance. Useful when combined with configfs to avoid having additional
VKMS instances.
Signed-off-by: José Expósito
---
drivers/gpu/drm/vkms/vkms_drv.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/gpu/drm/vk
On Tue, 18 Feb 2025 11:13:39 +0530
"Murthy, Arun R" wrote:
> On 17-02-2025 15:38, Pekka Paalanen wrote:
> > Hi Arun,
> >
> > this whole series seems to be missing all the UAPI docs for the DRM
> > ReST files, e.g. drm-kms.rst. The UAPI header doc comments are not a
> > replacement for them, I wou
Hi Sumit,
On Mon, 17 Feb 2025 at 06:13, Sumit Garg wrote:
> On Fri, 14 Feb 2025 at 21:19, Boris Brezillon
> wrote:
> > I would say one heap per-profile.
>
> And then it would have a per vendor multiplication factor as each
> vendor enforces memory restriction in a platform specific manner which
ows the
+ * body, after padding to 128-bytes.
+ *
+ * Images must be 16-byte aligned.
+ */
+#define DRM_FORMAT_MOD_APPLE_TWIDDLED_COMPRESSED fourcc_mod_code(APPLE, 2)
+
/*
* AMD modifiers
*
---
base-commit: 0ed1356af8f629ae807963b7db4e501e3b580bc2
change-id: 20250218-apple-twiddled-modifiers-fde1a6f4300c
Best regards,
--
Alyssa Rosenzweig
On Tue, Feb 18, 2025 at 06:28:53AM -0800, Luis Chamberlain wrote:
>
> What I recommend is to look into why we disable it by default, I think
I think FW_CACHE is enabled by default, no?
> its sold old obscure reasoning but now suspect it was udev being dumb,
> in line with why we also try to defe
On Tue, Feb 18, 2025 at 03:23:29PM +0100, Thomas Zimmermann wrote:
> Call drm_mode_size_dumb() to compute dumb-buffer scanline pitch and
> buffer size. No alignment required.
>
> Signed-off-by: Thomas Zimmermann
> Cc: Russell King
armada_pitch() does have some special alignment (it aligns the p
Hi,
On Tue, Feb 18, 2025 at 03:53:06PM +0100, Heiko Stübner wrote:
> Am Dienstag, 18. Februar 2025, 15:13:07 MEZ schrieb Sebastian Reichel:
> > On Tue, Feb 18, 2025 at 08:17:46PM +0800, Jianfeng Liu wrote:
> > > On Tue, 18 Feb 2025 11:00:57 +0100, Heiko Stübnerwrote:
> > > >So I guess step1, check
Hi, Christian,
On Wed, 2025-02-05 at 15:02 +0100, Christian König wrote:
> Am 30.01.25 um 11:13 schrieb Thomas Hellström:
> > Provide a helper to shrink ttm_tt page-vectors on a per-page
> > basis. A ttm_backup backend could then in theory get away with
> > allocating a single temporary page for e
Svyatoslav Ryhel writes:
[...]
>> Exactly. Both chips are from the same vendor (Solomon Systech [0]) and my
>> guess is that the SSD prefix means "Solomon Systech Device" or something
>> like that.
>>
>> [0]: https://www.solomon-systech.com
>>
>
> You are correct, vendor is the same, I have not
Hi Daniel!
On Tue Feb 18, 2025 at 6:10 AM JST, Daniel Almeida wrote:
> Hi Alex,
>
>> On 17 Feb 2025, at 11:04, Alexandre Courbot wrote:
>>
>> It is common to build a u64 from its high and low parts obtained from
>> two 32-bit registers. Conversely, it is also common to split a u64 into
>> two u
On Tue Feb 18, 2025 at 5:07 PM JST, Greg KH wrote:
> On Mon, Feb 17, 2025 at 04:48:13PM +0100, Simona Vetter wrote:
>> On Mon, Feb 17, 2025 at 11:04:45PM +0900, Alexandre Courbot wrote:
>> > Hi everyone,
>> >
>> > This short RFC is based on top of Danilo's initial driver stub series
>> > [1] and h
Add bindings for the LM3533 - a complete power source for
backlight, keypad, and indicator LEDs in smartphone handsets.
The high-voltage inductive boost converter provides the
power for two series LED strings display backlight and keypad
functions.
Signed-off-by: Svyatoslav Ryhel
---
.../devicet
Add schema and add support for lm3533 mfd to use device
tree bindings.
---
Changes on switching from v1 to v2:
- added unit seffix where it is suitable
- added vendor prefixes where it is suitable
- light sensor mover out of pattern properties
- added references to common schemas
- added detailed
I am struggling with the gpio-backlight module, it starts up
with a black screen, though the devicetree states "default-on":
backlight {
compatible = "gpio-backlight";
gpios = <0x31 0x05 0x00>;
default-on;
};
After bootup, the conte
Hi Danilo,
On Tue Feb 18, 2025 at 6:33 AM JST, Danilo Krummrich wrote:
> Hi Alex,
>
> On Mon, Feb 17, 2025 at 11:04:45PM +0900, Alexandre Courbot wrote:
>> Hi everyone,
>>
>> This short RFC is based on top of Danilo's initial driver stub series
>> [1] and has for goal to initiate discussions and
Remove platform data and fully relay on OF and device tree
parsing and binding devices.
Signed-off-by: Svyatoslav Ryhel
---
drivers/iio/light/lm3533-als.c | 40 --
drivers/leds/leds-lm3533.c | 45 +--
drivers/mfd/lm3533-core.c | 199 ++--
From: Lad Prabhakar
Hi All,
This patch series adds support for the Mali-G31 GPU on the RZ/V2H(P) SoC.
The changes include updating the device tree bindings, adding the GPU node
to the SoC device tree, and enabling the GPU on the RZ/V2H evaluation kit.
Lad Prabhakar (3):
dt-bindings: gpu: mali
From: Lad Prabhakar
Add Mali-G31 GPU node to SoC DTSI.
Signed-off-by: Lad Prabhakar
---
arch/arm64/boot/dts/renesas/r9a09g057.dtsi | 51 ++
1 file changed, 51 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r9a09g057.dtsi
b/arch/arm64/boot/dts/renesas/r9a09g057.dts
From: Lad Prabhakar
Add a compatible string for the Renesas RZ/V2H(P) SoC variants that
include a Mali-G31 GPU. These variants share the same restrictions on
interrupts, clocks, and power domains as the RZ/G2L SoC, so extend
the existing schema validation accordingly.
Signed-off-by: Lad Prabhaka
From: Lad Prabhakar
Enable Mali-G31 (GPU) node on EVK board.
Signed-off-by: Lad Prabhakar
---
.../boot/dts/renesas/r9a09g057h44-rzv2h-evk.dts | 15 +++
1 file changed, 15 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r9a09g057h44-rzv2h-evk.dts
b/arch/arm64/boot/dts/ren
On Tue Feb 18, 2025 at 7:07 PM JST, Dirk Behme wrote:
> On 17/02/2025 15:04, Alexandre Courbot wrote:
>> It is common to build a u64 from its high and low parts obtained from
>> two 32-bit registers. Conversely, it is also common to split a u64 into
>> two u32s to write them into registers. Add an
Svyatoslav Ryhel writes:
> вт, 18 лют. 2025 р. о 14:36 Thomas Zimmermann пише:
>>
>> (cc'ing Javier)
>>
>> Hi
>>
>> Am 17.02.25 um 15:09 schrieb Svyatoslav Ryhel:
>> > Solomon SSD2825 is a RGB to MIPI DSI bridge used in LG Optimus 4D P880
>> > and LG Optimus Vu P895
>>
>> There's a driver for So
вт, 18 лют. 2025 р. о 15:09 Javier Martinez Canillas пише:
>
> Svyatoslav Ryhel writes:
>
> > вт, 18 лют. 2025 р. о 14:36 Thomas Zimmermann пише:
> >>
> >> (cc'ing Javier)
> >>
> >> Hi
> >>
> >> Am 17.02.25 um 15:09 schrieb Svyatoslav Ryhel:
> >> > Solomon SSD2825 is a RGB to MIPI DSI bridge use
Allow to create, enable, disable and destroy VKMS instances using
configfs.
For the moment, it is not possible to add pipeline items, so trying to
enable the device will fail printing an informative error to the log.
Co-developed-by: Louis Chauvet
Signed-off-by: Louis Chauvet
Signed-off-by: Jos
From: Maxime Ripard
[ Upstream commit bb4f929a8875b4801db95b8cf3b2c527c1e475e0 ]
Some tests have the drm pointer assigned multiple times to the same
value. Drop the redundant assignments.
Reviewed-by: Simona Vetter
Link:
https://patchwork.freedesktop.org/patch/msgid/20250129-test-kunit-v2-2-f
From: Maxime Ripard
[ Upstream commit 6b6bfd63e1626ceedc738b2a06505aa5b46c1481 ]
The tests all deviate slightly in how they assign their local pointers
to DRM entities. This makes refactoring pretty difficult, so let's just
move the assignment as soon as the entities are allocated.
Reviewed-by:
From: Maxime Ripard
[ Upstream commit 5d14c08a47460e8eedf0185a28b116420ea7f29d ]
The find_preferred_mode() functions takes the mode_config mutex, but due
to the order most tests have, is called with the crtc_ww_class_mutex
taken. This raises a warning for a circular dependency when running the
t
-Original Message-
From: Tvrtko Ursulin
Sent: Tuesday, February 18, 2025 10:39 AM
To: Simona Vetter ; Cavitt, Jonathan
Cc: intel...@lists.freedesktop.org; dri-devel@lists.freedesktop.org; Gupta,
saurabhg ; Zuo, Alex ; Lahtinen,
Joonas ; De Marchi, Lucas
; Brost, Matthew
Subject: Re:
Hi
In continuation to my previous mail.
>> +
>> +static int appletbdrm_send_msg(struct appletbdrm_device *adev, u32 msg)
>> +{
>> + struct appletbdrm_msg_simple_request *request;
>> + int ret;
>> +
>> + request = kzalloc(sizeof(*request), GFP_KERNEL);
>> + if (!request)
>> + return -ENOMEM;
>> +
Add support for userspace to query per drm client reset stats via the
query ioctl. This includes the number of engine resets the drm client
has observed, as well as a list of up to the last 50 relevant exec
queue bans and their associated causal pagefaults (if they exists).
Signed-off-by: Jonatha
Pass the drm file to the query funcs in xe_query.c. This will be
necessary for a future query.
Signed-off-by: Jonathan Cavitt
---
drivers/gpu/drm/xe/xe_query.c | 39 ---
1 file changed, 27 insertions(+), 12 deletions(-)
diff --git a/drivers/gpu/drm/xe/xe_query.c
Add additional information to drm client so it can report up to the last
50 exec queues to have been banned on it, as well as the last pagefault
seen when said exec queues were banned. Since we cannot reasonably
associate a pagefault to a specific exec queue, we currently report the
last seen page
Migrate the pagefault struct from xe_gt_pagefault.c to the
xe_gt_pagefault.h header file, along with the associated enum values.
Signed-off-by: Jonathan Cavitt
---
drivers/gpu/drm/xe/xe_gt_pagefault.c | 27 ---
drivers/gpu/drm/xe/xe_gt_pagefault.h | 28 +++
Add a counter to xe_drm_client that tracks the number of times the
engine has been reset since the drm client was created.
Signed-off-by: Jonathan Cavitt
---
drivers/gpu/drm/xe/xe_drm_client.h | 2 ++
drivers/gpu/drm/xe/xe_guc_submit.c | 4 +++-
2 files changed, 5 insertions(+), 1 deletion(-)
d
Add additional information to drm client so it can report the last 50
exec queues to have been banned on it, as well as the last pagefault
seen when said exec queues were banned. Since we cannot reasonably
associate a pagefault to a specific exec queue, we currently report the
last seen pagefault o
From: Maxime Ripard
[ Upstream commit 6b6bfd63e1626ceedc738b2a06505aa5b46c1481 ]
The tests all deviate slightly in how they assign their local pointers
to DRM entities. This makes refactoring pretty difficult, so let's just
move the assignment as soon as the entities are allocated.
Reviewed-by:
From: Maxime Ripard
[ Upstream commit bb4f929a8875b4801db95b8cf3b2c527c1e475e0 ]
Some tests have the drm pointer assigned multiple times to the same
value. Drop the redundant assignments.
Reviewed-by: Simona Vetter
Link:
https://patchwork.freedesktop.org/patch/msgid/20250129-test-kunit-v2-2-f
From: Maxime Ripard
[ Upstream commit 5d14c08a47460e8eedf0185a28b116420ea7f29d ]
The find_preferred_mode() functions takes the mode_config mutex, but due
to the order most tests have, is called with the crtc_ww_class_mutex
taken. This raises a warning for a circular dependency when running the
t
Add the exec queue id to the exec queue struct. This is useful for
performing a reverse lookup into the xef->exec_queue xarray.
Signed-off-by: Jonathan Cavitt
---
drivers/gpu/drm/xe/xe_exec_queue.c | 1 +
drivers/gpu/drm/xe/xe_exec_queue_types.h | 2 ++
2 files changed, 3 insertions(+)
d
On Tue, 2025-02-18 at 22:16 +0900, Alexandre Courbot wrote:
> > A proper struct with `high` and `low` might be more verbose, but
> > it rules out this issue.
>
> Mmm indeed, so we would have client code looking like:
>
> let SplitU64 { high, low } = some_u64.into_u32();
>
> instead of
>
>
On Thu, 2025-01-23 at 13:04 +0200, Dmitry Baryshkov wrote:
> On Thu, Jan 23, 2025 at 12:26:25PM +0200, Jani Nikula wrote:
> > On Fri, 17 Jan 2025, Dmitry Baryshkov wrote:
> > > Existing DPCD access functions return an error code or the number of
> > > bytes being read / write in case of partial ac
I've been wanting to do this for ages and just never got the time, thank you
for getting to this ♥
So this patch looks good to me, but msm isn't the only user of
drm_dp_dpcd_read_link_status() - so we would need to convert other drivers
using coccinelle or similar as well for this to not break dri
Reviewed-by: Lyude Paul
On Fri, 2025-01-17 at 10:56 +0200, Dmitry Baryshkov wrote:
> Switch drm_dp_cec.c to use new set of DPCD read / write helpers.
>
> Signed-off-by: Dmitry Baryshkov
> ---
> drivers/gpu/drm/display/drm_dp_cec.c | 37
> ++--
> 1 file changed,
On Tue, Feb 18, 2025 at 06:24:43PM +0100, Danilo Krummrich wrote:
> On Tue, Feb 18, 2025 at 06:28:53AM -0800, Luis Chamberlain wrote:
> >
> > What I recommend is to look into why we disable it by default, I think
>
> I think FW_CACHE is enabled by default, no?
>
> > its sold old obscure reasonin
1 - 100 of 243 matches
Mail list logo
