[PATCH 0/2] Convert Rockchip CDN DP binding to yaml

2025-05-07 Thread Chaoyi Chen
From: Chaoyi Chen This series convert cdn-dp-rockchip.txt to yaml. PATCH 1 try to improve coding style on the existing rk3399 cdn-dp node. PATCH 2 try to convert cdn-dp-rockchip.txt to yaml. Tested with: 1. make ARCH=arm64 dt_binding_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/dis

[PATCH 1/2] arm64: dts: rockchip: Improve coding style for rk3399 cdn_dp

2025-05-07 Thread Chaoyi Chen
From: Chaoyi Chen Let's make the ports nodes of cdn_dp in the same style as the other display interface, and match the style of ports's yaml. Signed-off-by: Chaoyi Chen --- arch/arm64/boot/dts/rockchip/rk3399-base.dtsi | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git

[PATCH 2/2] dt-bindings: display: rockchip: Convert cdn-dp-rockchip.txt to yaml

2025-05-07 Thread Chaoyi Chen
From: Chaoyi Chen Convert cdn-dp-rockchip.txt to yaml. Tested with: 1. make ARCH=arm64 dt_binding_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/display/rockchip/rockchip,cdn-dp.yaml 2. make ARCH=arm64 dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/display/rockchip/roc

Re: [PATCH v2] drm: drm_fourcc: add 10/12/16bit software decoder YCbCr formats

2025-05-07 Thread Daniel Stone
Hey there, On Thu, 1 May 2025 at 12:22, Robert Mader wrote: > Unlike formats typically used by hardware decoders the 10/12bit formats > use a LSB alignment. In order to allow fast implementations in GL > and Vulkan the padding must contain only zeros, so the float > representation can be calculat

Re: [RFC v7 00/23] DRM scheduling cgroup controller

2025-05-07 Thread Matthew Brost
On Fri, May 02, 2025 at 01:32:33PM +0100, Tvrtko Ursulin wrote: > Hi all, > > This is another respin of this old work^1 but this version is a total rewrite > and completely changes how the control is done. > > This time round the work builds upon the "fair" DRM scheduler work I have > posted > r

[PULL] drm-intel-gt-next

2025-05-07 Thread Joonas Lahtinen
Hi Dave & Sima, Here goes the drm-intel-gt-next PR towards 6.16. No new features, just fixes. SLPC wait boost fix for DG1/DG2, engine reset fix for HSW. Move to usleep_range for <20ms timeouts and fix splats on early probe errors. The rest is usual cleanups and improvements to selftests. Regard

Re: [PATCH 3/4] dt-bindings: display/msm: add stream 1 pixel clock binding

2025-05-07 Thread Krzysztof Kozlowski
On 23/04/2025 04:46, Abhinav Kumar wrote: > Hi Krzysztof > > On 12/3/2024 12:04 AM, Krzysztof Kozlowski wrote: >> On 03/12/2024 04:31, Abhinav Kumar wrote: >>> On some chipsets the display port controller can support more >> >> Which chipsets? >> > > From the current list of chipsets which suppo

RE: [RFC 2/9] mei: late_bind: add late binding component driver

2025-05-07 Thread Usyskin, Alexander
> > > > diff --git a/include/drm/intel/xe_late_bind_mei_interface.h > b/include/drm/intel/xe_late_bind_mei_interface.h > > new file mode 100644 > > index ..4005c4c6184f > > --- /dev/null > > +++ b/include/drm/intel/xe_late_bind_mei_interface.h > > @@ -0,0 +1,49 @@ > > +/* SPDX-License

Re: [PATCH] dt-bindings: display/msm: hdmi: Fix constraints on additional 'port' properties

2025-05-07 Thread Dmitry Baryshkov
On Wed, May 07, 2025 at 04:59:12PM -0500, Rob Herring (Arm) wrote: > The MSM HDMI port nodes are missing any restrictions on additional > properties. The $ref should be to "/properties/port" rather than > "/$defs/port-base" as there are not additional properties in the nodes > to define. > > Signe

Re: [PATCH v8 10/10] ref_tracker: eliminate the ref_tracker_dir name field

2025-05-07 Thread Jakub Kicinski
On Wed, 07 May 2025 09:06:35 -0400 Jeff Layton wrote: > + * @quarantime_count: max number of entries to be tracked quarantime ^ :( -- pw-bot: cr

RE: [PATCH] drm/dp: Fix Write_Status_Update_Request AUX request format

2025-05-07 Thread Lin, Wayne
[AMD Official Use Only - AMD Internal Distribution Only] Thanks for the feedback! I'll adjust it and give v2 soon. Thanks, Wayne > -Original Message- > From: Limonciello, Mario > Sent: Tuesday, May 6, 2025 4:22 AM > To: Lin, Wayne ; dri-devel@lists.freedesktop.org > Cc: ville.syrj...@li

Re: [RFC 5/9] drm/xe/xe_late_bind_fw: Load late binding firmware

2025-05-07 Thread Daniele Ceraolo Spurio
On 4/29/2025 9:09 AM, Badal Nilawar wrote: Load late binding firmware Signed-off-by: Badal Nilawar --- drivers/gpu/drm/xe/xe_device.c | 2 + drivers/gpu/drm/xe/xe_late_bind_fw.c | 91 +++- drivers/gpu/drm/xe/xe_late_bind_fw.h | 1 + 3 files changed, 92 in

Re: [RFC 4/9] drm/xe/xe_late_bind_fw: Initialize late binding firmware

2025-05-07 Thread Daniele Ceraolo Spurio
On 4/29/2025 9:09 AM, Badal Nilawar wrote: Search for late binding firmware binaries and populate the meta data of firmware structures. Signed-off-by: Badal Nilawar --- drivers/gpu/drm/xe/xe_device.c | 2 + drivers/gpu/drm/xe/xe_late_bind_fw.c | 101 ++- d

Re: [PATCH] dt-bindings: display/msm: hdmi: Fix constraints on additional 'port' properties

2025-05-07 Thread Rob Herring (Arm)
On Wed, 07 May 2025 16:59:12 -0500, Rob Herring (Arm) wrote: > The MSM HDMI port nodes are missing any restrictions on additional > properties. The $ref should be to "/properties/port" rather than > "/$defs/port-base" as there are not additional properties in the nodes > to define. > > Signed-of

[PATCH v5 4/4] drm/msm/dp: Introduce link training per-segment for LTTPRs

2025-05-07 Thread Aleksandrs Vinarskis
DisplayPort requires per-segment link training when LTTPR are switched to non-transparent mode, starting with LTTPR closest to the source. Only when each segment is trained individually, source can link train to sink. Implement per-segment link traning when LTTPR(s) are detected, to support extern

[PATCH v5 2/4] drm/msm/dp: Account for LTTPRs capabilities

2025-05-07 Thread Aleksandrs Vinarskis
Take into account LTTPR capabilities when selecting maximum allowed link rate, number of data lines. Fixes: 72d0af4accd9 ("drm/msm/dp: Add support for LTTPR handling") Reviewed-by: Abel Vesa Reviewed-by: Abhinav Kumar Reviewed-by: Dmitry Baryshkov Signed-off-by: Aleksandrs Vinarskis Tested-by

[PATCH v5 3/4] drm/msm/dp: Prepare for link training per-segment for LTTPRs

2025-05-07 Thread Aleksandrs Vinarskis
Per-segment link training requires knowing the number of LTTPRs (if any) present. Store the count during LTTPRs' initialization. Fixes: 72d0af4accd9 ("drm/msm/dp: Add support for LTTPR handling") Reviewed-by: Abel Vesa Reviewed-by: Abhinav Kumar Reviewed-by: Dmitry Baryshkov Signed-off-by: Ale

[PATCH v5 0/4] drm/msm/dp: Introduce link training per-segment for LTTPRs

2025-05-07 Thread Aleksandrs Vinarskis
Recently added Initial LTTPR support in msm/dp has configured LTTPR(s) to non-transparent mode to enable video output on X1E-based devices that come with LTTPR on the motherboards. However, video would not work if additional LTTPR(s) are present between sink and source, which is the case for USB Ty

[PATCH v5 1/4] drm/msm/dp: Fix support of LTTPR initialization

2025-05-07 Thread Aleksandrs Vinarskis
Initialize LTTPR before msm_dp_panel_read_sink_caps, as DPTX shall (re)read DPRX caps after LTTPR detection, as required by DP 2.1a, Section 3.6.7.6.1. Fixes: 72d0af4accd9 ("drm/msm/dp: Add support for LTTPR handling") Reviewed-by: Abhinav Kumar Reviewed-by: Dmitry Baryshkov Signed-off-by: Alek

Re: [PATCH] drm/msm: mdss: use devres version of interface to populate children devices

2025-05-07 Thread Vladimir Zapolskiy
On 5/8/25 00:24, Dmitry Baryshkov wrote: On Wed, May 07, 2025 at 10:35:38PM +0300, Vladimir Zapolskiy wrote: Trivial change, there is a managed device resource version of of_platform_populate(), and its usage simplifies the code a bit. Signed-off-by: Vladimir Zapolskiy --- drivers/gpu/drm/ms

Re: [RFC 2/9] mei: late_bind: add late binding component driver

2025-05-07 Thread Daniele Ceraolo Spurio
diff --git a/include/drm/intel/xe_late_bind_mei_interface.h b/include/drm/intel/xe_late_bind_mei_interface.h new file mode 100644 index ..4005c4c6184f --- /dev/null +++ b/include/drm/intel/xe_late_bind_mei_interface.h @@ -0,0 +1,49 @@ +/* SPDX-License-Identifier: MIT */ +/* + * Copy

Re: [PATCH v4 4/4] drm/msm/dp: Introduce link training per-segment for LTTPRs

2025-05-07 Thread Aleksandrs Vinarskis
On Thu, 8 May 2025 at 00:08, Abhinav Kumar wrote: > > Hi Alex > > > On 5/7/2025 3:01 PM, Aleksandrs Vinarskis wrote: > > On Tue, 6 May 2025 at 01:41, Abhinav Kumar > > wrote: > >> > >> Hi Alex > >> > >> On 5/4/2025 3:06 PM, Aleksandrs Vinarskis wrote: > >>> On Sun, 4 May 2025 at 05:02, Abhinav K

Re: [rfc] drm/ttm/memcg: simplest initial memcg/ttm integration (v2)

2025-05-07 Thread Dave Airlie
On Thu, 8 May 2025 at 08:03, Dave Airlie wrote: > > On Thu, 8 May 2025 at 03:52, Johannes Weiner wrote: > > > > Hello Dave, > > > > On Fri, May 02, 2025 at 01:35:59PM +1000, Dave Airlie wrote: > > > Hey all, > > > > > > This is my second attempt at adding the initial simple memcg/ttm > > > integr

Re: [PATCH v4 4/4] drm/msm/dp: Introduce link training per-segment for LTTPRs

2025-05-07 Thread Abhinav Kumar
Hi Alex On 5/7/2025 3:01 PM, Aleksandrs Vinarskis wrote: On Tue, 6 May 2025 at 01:41, Abhinav Kumar wrote: Hi Alex On 5/4/2025 3:06 PM, Aleksandrs Vinarskis wrote: On Sun, 4 May 2025 at 05:02, Abhinav Kumar wrote: Hi Alex Thanks for the response. My updates below. I also had one quest

Re: [RFC 9/9] {fwctl,drm}/xe/pcode: Introduce xe_pcode_fwctl

2025-05-07 Thread Jason Gunthorpe
On Wed, May 07, 2025 at 03:49:15PM -0400, Rodrigo Vivi wrote: > One last thing since I have your attention here. Was any time in the previous > fwctl discussions talked about the possibility of some extra usages for like > FW flashing or in-field-repair/tests where big data needs to filled bypassi

Re: [rfc] drm/ttm/memcg: simplest initial memcg/ttm integration (v2)

2025-05-07 Thread Dave Airlie
On Thu, 8 May 2025 at 03:52, Johannes Weiner wrote: > > Hello Dave, > > On Fri, May 02, 2025 at 01:35:59PM +1000, Dave Airlie wrote: > > Hey all, > > > > This is my second attempt at adding the initial simple memcg/ttm > > integration. > > > > This varies from the first attempt in two major ways:

Re: [PATCH v4 4/4] drm/msm/dp: Introduce link training per-segment for LTTPRs

2025-05-07 Thread Aleksandrs Vinarskis
On Tue, 6 May 2025 at 01:41, Abhinav Kumar wrote: > > Hi Alex > > On 5/4/2025 3:06 PM, Aleksandrs Vinarskis wrote: > > On Sun, 4 May 2025 at 05:02, Abhinav Kumar > > wrote: > >> > >> Hi Alex > >> > >> Thanks for the response. > >> > >> My updates below. I also had one question for Abel below. >

[PATCH] dt-bindings: display/msm: hdmi: Fix constraints on additional 'port' properties

2025-05-07 Thread Rob Herring (Arm)
The MSM HDMI port nodes are missing any restrictions on additional properties. The $ref should be to "/properties/port" rather than "/$defs/port-base" as there are not additional properties in the nodes to define. Signed-off-by: Rob Herring (Arm) --- Documentation/devicetree/bindings/display/msm

Re: [RFC 3/9] drm/xe/late_bind_fw: Introducing late_bind_fw

2025-05-07 Thread Daniele Ceraolo Spurio
On 4/29/2025 9:09 AM, Badal Nilawar wrote: Introducing late_bind_fw to enable firmware loading for the devices, such as the fan controller and voltage regulator, during the driver probe. Typically, firmware for these devices are part of IFWI flash image but can be replaced at probe after OEM t

Re: [PATCH] drm/msm: mdss: use devres version of interface to populate children devices

2025-05-07 Thread Dmitry Baryshkov
On Wed, May 07, 2025 at 10:35:38PM +0300, Vladimir Zapolskiy wrote: > Trivial change, there is a managed device resource version of > of_platform_populate(), and its usage simplifies the code a bit. > > Signed-off-by: Vladimir Zapolskiy > --- > drivers/gpu/drm/msm/msm_mdss.c | 4 +--- > 1 file c

Re: [PATCH V9 00/24] drm: sun4i: add Display Engine 3.3 (DE33) support

2025-05-07 Thread Rob Herring
On Wed, May 7, 2025 at 3:22 PM Chris Morgan wrote: > > From: Chris Morgan > > I've spoken with Ryan and he agreed to let me take over this series to > get the display engine working on the Allwinner H616. I've taken his > previous patch series for Display Engine 3.3 and combined it with the > LCD

[PATCH V9 15/24] dt-bindings: display: sun4i: Add compatible strings for H616 DE

2025-05-07 Thread Chris Morgan
From: Chris Morgan Add compatible strings for allwinner,sun50i-h616-display-engine. The device is functionally identical to the allwinner,sun50i-h6-display-engine. Signed-off-by: Chris Morgan --- .../allwinner,sun4i-a10-display-engine.yaml | 39 +++ 1 file changed, 22 inserti

[PATCH V9 10/24] clk: sunxi-ng: ccu: add Display Engine 3.3 (DE33) support

2025-05-07 Thread Chris Morgan
From: Chris Morgan The DE33 is a newer version of the Allwinner Display Engine IP block, found in the H616, H618, H700 and T507 SoCs. DE2 and DE3 are already supported by the mainline driver. The DE33 in the H616 has mixer0 and writeback units. The clocks and resets required are identical to the

[PATCH V9 06/24] drm: sun4i: de2/de3: use generic register reference function for layer configuration

2025-05-07 Thread Chris Morgan
From: Chris Morgan Use the new blender register lookup function where required in the layer commit and update code. Signed-off-by: Jernej Skrabec Signed-off-by: Ryan Walklin Signed-off-by: Chris Morgan --- Changelog v2..v3: - Refactor for 6.11 layer init/modesetting changes --- drivers/gpu/d

[PATCH V9 14/24] dt-bindings: allwinner: Add TCON_TOP and TCON_LCD clock/reset defines

2025-05-07 Thread Chris Morgan
From: Chris Morgan The Allwinner H700 exposes RGB and LVDS pins as well as a HDMI connector. This requires additional clocks for the TCON_TOP and clock and resets for the TCON_LCD LCD controllers to be defined as per the T507 datasheet (which shares the same die). Signed-off-by: Ryan Walklin Si

[PATCH V9 24/24] arm64: dts: allwinner: rg35xx: Enable LCD output

2025-05-07 Thread Chris Morgan
From: Chris Morgan The RG35XX has a 640x480 RGB/SPI LCD panel, supported by the SoC display pipeline and an NV3052C controller. The H616 SOC's GPIO bank D contains the muxed display pins for RGB and LVDS output support. Enable the display engine and LCD timing controller, configure the panel, an

[PATCH V9 23/24] arm64: dts: allwinner: rg35xx: Add GPIO backlight control

2025-05-07 Thread Chris Morgan
From: Chris Morgan The LCD backlight for this device can be exposed as a simple GPIO- controlled device. It would be more accurately modelled using PWM to enable brightness control, however the PWM driver design for the H616 is not yet upstreamed. Add a GPIO backlight node to the DTS. Signed-of

[PATCH V9 09/24] dt-bindings: allwinner: add H616 DE33 mixer binding

2025-05-07 Thread Chris Morgan
From: Chris Morgan The Allwinner H616 and variants have a new display engine revision (DE33). The mixer configuration registers are significantly different to the DE3 and DE2 revisions, being split into separate top and display blocks, therefore a fallback for the mixer compatible is not provide

[PATCH V9 13/24] drm: sun4i: de33: mixer: add mixer configuration for the H616

2025-05-07 Thread Chris Morgan
From: Chris Morgan The H616 (and related SoC packages sharing the same die) carry the new DE33 display engine. Add the mixer configuration and a compatible string for the H616 to the mixer. Signed-off-by: Jernej Skrabec Signed-off-by: Ryan Walklin Signed-off-by: Chris Morgan --- Changelog v7

[PATCH V9 11/24] drm: sun4i: de33: vi_scaler: add Display Engine 3.3 (DE33) support

2025-05-07 Thread Chris Morgan
From: Chris Morgan The vi_scaler appears to be used in preference to the ui_scaler module for hardware video scaling in the DE33. Enable support for this scaler. Signed-off-by: Jernej Skrabec Signed-off-by: Ryan Walklin Signed-off-by: Chris Morgan --- drivers/gpu/drm/sun4i/sun8i_ui_layer.c

[PATCH V9 21/24] arm64: dts: allwinner: h616: Add TCON nodes to H616 DTSI

2025-05-07 Thread Chris Morgan
From: Chris Morgan The Allwinner H616 has a display pipeline similar to other Allwinner devices, specifically the A10, but using a newer display engine revision (DE33). Not all output pins are exposed on all package variants, for example only the H700 and T507 have LCD pins exposed, but all vari

[PATCH V9 00/24] drm: sun4i: add Display Engine 3.3 (DE33) support

2025-05-07 Thread Chris Morgan
From: Chris Morgan I've spoken with Ryan and he agreed to let me take over this series to get the display engine working on the Allwinner H616. I've taken his previous patch series for Display Engine 3.3 and combined it with the LCD controller patch series. I've also fixed a few additional bugs a

[PATCH V9 22/24] arm64: dts: allwinner: h616: add LCD and LVDS pins

2025-05-07 Thread Chris Morgan
From: Chris Morgan The Allwinner H616 (and its H618, H700 and T507 package variants with the same die) have 28 video output pins for RGB/SPI and LVDS display. These are in GPIO Bank D and are multiplexed. In RGB mode, pins PD0-PD23 are for 24-bit RGB pixel output, pins PD24-PD27 are for clock, D

[PATCH V9 17/24] dt-bindings: sram: sunxi-sram: Add H616 SRAM C compatible

2025-05-07 Thread Chris Morgan
From: Chris Morgan Add a compatible string for the H616 SRAM C region which is functionally similar to the A64 SRAM C region. Signed-off-by: Chris Morgan --- .../bindings/sram/allwinner,sun4i-a10-system-control.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Do

[PATCH V9 20/24] arm64: dts: allwinner: h616: add display engine, bus and mixer nodes

2025-05-07 Thread Chris Morgan
From: Chris Morgan The Allwinner H616 and variants (H618, H700 and T507) have a new display engine variant (DE33). Support has been added to the existing DE2/DE3 sun4i driver in a previous patch series (x). The variant is selected via the appropriate mixer device tree compatible string. Add the

[PATCH V9 12/24] drm: sun4i: de33: mixer: add Display Engine 3.3 (DE33) support

2025-05-07 Thread Chris Morgan
From: Chris Morgan The DE33 is a newer version of the Allwinner Display Engine IP block, found in the H616, H618, H700 and T507 SoCs. DE2 and DE3 are already supported by the mainline driver. Notable features (from the H616 datasheet and implemented): - 4096 x 2048 (4K) output support Other fea

[PATCH V9 18/24] dt-bindings: display: Add R40 and H616 display engine compatibles

2025-05-07 Thread Chris Morgan
From: Chris Morgan Add display engine compatible for the R40 LCD controller, and for the H616 TV and LCD controller which is functionally identical to the R40. Signed-off-by: Chris Morgan --- .../bindings/display/allwinner,sun4i-a10-tcon.yaml | 10 ++ 1 file changed, 10 insertions(

[PATCH V9 07/24] dt-bindings: allwinner: add H616 DE33 bus binding

2025-05-07 Thread Chris Morgan
From: Chris Morgan The Allwinner H616 and variants have a new display engine revision (DE33). Add a display engine bus binding for the DE33. Note that the DE33 requires 3 register blocks instead of 1. To keep things simple remove the maxItems value for registers for the child nodes and instead r

[PATCH V9 19/24] drm/sun4i: tcon: Add support for R40 LCD

2025-05-07 Thread Chris Morgan
From: Chris Morgan The Allwinner H616 and related SOCs have an LCD timing controller (TCON) which is compatible with the R40 SOC's controller and existing sun4i driver. The H616 does not expose this controller but the H700 and T507 (based on the same die) do. The controller supports LVDS and RGB

[PATCH V9 16/24] dt-bindings: display: sun4i: Add compatible strings for H616 TCON TOP

2025-05-07 Thread Chris Morgan
From: Chris Morgan Add compatible string for allwinner,sun50i-h616-tcon-top with a fallback string of allwinner,sun50i-h6-tcon-top. Signed-off-by: Chris Morgan --- .../display/allwinner,sun8i-r40-tcon-top.yaml | 13 + 1 file changed, 9 insertions(+), 4 deletions(-) diff --gi

[PATCH V9 05/24] drm: sun4i: de2/de3: add generic blender register reference function

2025-05-07 Thread Chris Morgan
From: Chris Morgan The DE2 and DE3 engines have a blender register range within the mixer engine register map, whereas the DE33 separates this out into a separate display group. Prepare for this by adding a function to look the blender reference up, with a subsequent patch to add a conditional b

[PATCH V9 08/24] dt-bindings: allwinner: add H616 DE33 clock binding

2025-05-07 Thread Chris Morgan
From: Chris Morgan The Allwinner H616 and variants have a new display engine revision (DE33). Add a clock binding for the DE33. Signed-off-by: Ryan Walklin Signed-off-by: Chris Morgan Acked-by: Conor Dooley Reviewed-by: Chen-Yu Tsai --- Changelog v2..v3: - Separate content into three patche

[PATCH V9 01/24] dt-bindings: clock: sun50i-h616-ccu: Add LVDS reset

2025-05-07 Thread Chris Morgan
From: Chris Morgan Add the required LVDS reset binding for the LCD TCON. Signed-off-by: Chris Morgan Signed-off-by: Ryan Walklin --- include/dt-bindings/reset/sun50i-h616-ccu.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/dt-bindings/reset/sun50i-h616-ccu.h b/include/dt-bindin

[PATCH V9 02/24] clk: sunxi-ng: h616: Add LVDS reset for LCD TCON

2025-05-07 Thread Chris Morgan
From: Chris Morgan Add the required LVDS reset for the LCD TCON. Note that while this reset is exposed for the T507, H616, and H700 only the H700 has an LCD controller. Signed-off-by: Chris Morgan Signed-off-by: Ryan Walklin --- drivers/clk/sunxi-ng/ccu-sun50i-h616.c | 1 + 1 file changed, 1

[PATCH V9 03/24] drm: sun4i: de2/de3: add mixer version enum

2025-05-07 Thread Chris Morgan
From: Chris Morgan The Allwinner DE2 and DE3 display engine mixers are currently identified by a simple boolean flag. This will not scale to support additional DE variants. Convert the boolean flag to an enum. Signed-off-by: Jernej Skrabec Signed-off-by: Ryan Walklin Signed-off-by: Chris Morg

[PATCH V9 04/24] drm: sun4i: de2/de3: refactor mixer initialisation

2025-05-07 Thread Chris Morgan
From: Chris Morgan Now that the DE variant can be selected by enum, take the oppportunity to factor out some common initialisation code to a separate function. Signed-off-by: Jernej Skrabec Signed-off-by: Ryan Walklin Signed-off-by: Chris Morgan Reviewed-by: Andre Przywara --- Changelog v1..

Re: [PATCH v3 0/7] drm/panthor: Add performance counters with manual sampling mode

2025-05-07 Thread Adrián Larumbe
Hi Lukas, I wanted to review this series for quite some time but lately have found myself caught up in quite a few other things. I've had a look into it last week, but before I delve into it any further, I was wondering whether you could take some time to go over the questions and comments I le

Re: [RFC 2/2] drm/amd: Use suspend and hibernate post freeze notifications

2025-05-07 Thread Rafael J. Wysocki
On Wed, May 7, 2025 at 9:45 PM Mario Limonciello wrote: > > On 5/7/2025 2:39 PM, Rafael J. Wysocki wrote: > > On Wed, May 7, 2025 at 9:17 PM Mario Limonciello wrote: > >> > >> On 5/7/2025 2:14 PM, Rafael J. Wysocki wrote: > >>> On Thu, May 1, 2025 at 11:17 PM Mario Limonciello > >>> wrote: > >>

Re: [RFC 9/9] {fwctl,drm}/xe/pcode: Introduce xe_pcode_fwctl

2025-05-07 Thread Rodrigo Vivi
On Tue, May 06, 2025 at 03:13:53PM -0300, Jason Gunthorpe wrote: Hi Jason, first of all, thank you so much for creating this and for the review here. > On Tue, Apr 29, 2025 at 09:39:56PM +0530, Badal Nilawar wrote: > > > diff --git a/drivers/gpu/drm/xe/xe_pcode_fwctl.c > > b/drivers/gpu/drm/xe

Re: [RFC 2/2] drm/amd: Use suspend and hibernate post freeze notifications

2025-05-07 Thread Rafael J. Wysocki
On Wed, May 7, 2025 at 9:17 PM Mario Limonciello wrote: > > On 5/7/2025 2:14 PM, Rafael J. Wysocki wrote: > > On Thu, May 1, 2025 at 11:17 PM Mario Limonciello > > wrote: > >> > >> From: Mario Limonciello > >> > >> commit 2965e6355dcd ("drm/amd: Add Suspend/Hibernate notification > >> callback

Re: [RFC 2/2] drm/amd: Use suspend and hibernate post freeze notifications

2025-05-07 Thread Mario Limonciello
On 5/7/2025 2:39 PM, Rafael J. Wysocki wrote: On Wed, May 7, 2025 at 9:17 PM Mario Limonciello wrote: On 5/7/2025 2:14 PM, Rafael J. Wysocki wrote: On Thu, May 1, 2025 at 11:17 PM Mario Limonciello wrote: From: Mario Limonciello commit 2965e6355dcd ("drm/amd: Add Suspend/Hibernate notifi

Re: [PATCH v24 3/5] drm/xe/uapi: Define drm_xe_vm_get_property

2025-05-07 Thread ivan.briano
On Wed, May 07, 2025 at 12:32:49PM -0700, Cavitt, Jonathan wrote: > -Original Message- > From: Vivi, Rodrigo > Sent: Wednesday, May 7, 2025 12:24 PM > To: Cavitt, Jonathan > Cc: intel...@lists.freedesktop.org; Gupta, saurabhg > ; Zuo, Alex ; > joonas.lahti...@linux.intel.com; Brost, Ma

Re: [RFC 2/2] drm/amd: Use suspend and hibernate post freeze notifications

2025-05-07 Thread Alex Deucher
On Wed, May 7, 2025 at 3:39 PM Rafael J. Wysocki wrote: > > On Wed, May 7, 2025 at 9:17 PM Mario Limonciello wrote: > > > > On 5/7/2025 2:14 PM, Rafael J. Wysocki wrote: > > > On Thu, May 1, 2025 at 11:17 PM Mario Limonciello > > > wrote: > > >> > > >> From: Mario Limonciello > > >> > > >> com

[PATCH] drm/msm: mdss: use devres version of interface to populate children devices

2025-05-07 Thread Vladimir Zapolskiy
Trivial change, there is a managed device resource version of of_platform_populate(), and its usage simplifies the code a bit. Signed-off-by: Vladimir Zapolskiy --- drivers/gpu/drm/msm/msm_mdss.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/gpu/drm/msm/msm_mdss.

RE: [PATCH v24 3/5] drm/xe/uapi: Define drm_xe_vm_get_property

2025-05-07 Thread Cavitt, Jonathan
-Original Message- From: Vivi, Rodrigo Sent: Wednesday, May 7, 2025 12:24 PM To: Cavitt, Jonathan Cc: intel...@lists.freedesktop.org; Gupta, saurabhg ; Zuo, Alex ; joonas.lahti...@linux.intel.com; Brost, Matthew ; Zhang, Jianxun ; Lin, Shuicheng ; dri-devel@lists.freedesktop.org; Waj

Re: [PATCH v24 5/5] drm/xe/xe_vm: Implement xe_vm_get_property_ioctl

2025-05-07 Thread Rodrigo Vivi
On Wed, May 07, 2025 at 03:57:26PM +, Jonathan Cavitt wrote: > Add support for userspace to request a list of observed faults > from a specified VM. > > v2: > - Only allow querying of failed pagefaults (Matt Brost) > > v3: > - Remove unnecessary size parameter from helper function, as it >

Re: [PATCH v24 3/5] drm/xe/uapi: Define drm_xe_vm_get_property

2025-05-07 Thread Rodrigo Vivi
On Wed, May 07, 2025 at 03:57:24PM +, Jonathan Cavitt wrote: > Add initial declarations for the drm_xe_vm_get_property ioctl. > > v2: > - Expand kernel docs for drm_xe_vm_get_property (Jianxun) > > v3: > - Remove address type external definitions (Jianxun) > - Add fault type to xe_drm_fault s

Re: [RFC 2/2] drm/amd: Use suspend and hibernate post freeze notifications

2025-05-07 Thread Mario Limonciello
On 5/7/2025 2:14 PM, Rafael J. Wysocki wrote: On Thu, May 1, 2025 at 11:17 PM Mario Limonciello wrote: From: Mario Limonciello commit 2965e6355dcd ("drm/amd: Add Suspend/Hibernate notification callback support") introduced a VRAM eviction earlier in the PM sequences when swap was still avail

Re: [RFC 2/2] drm/amd: Use suspend and hibernate post freeze notifications

2025-05-07 Thread Rafael J. Wysocki
On Thu, May 1, 2025 at 11:17 PM Mario Limonciello wrote: > > From: Mario Limonciello > > commit 2965e6355dcd ("drm/amd: Add Suspend/Hibernate notification > callback support") introduced a VRAM eviction earlier in the PM > sequences when swap was still available for evicting to. This helped > to

Re: [PATCH] drm/msm/adreno: Remove MODULE_FIRMWARE()'s

2025-05-07 Thread Konrad Dybcio
On 5/7/25 5:47 PM, Rob Clark wrote: > From: Rob Clark > > The driver handles the case where gpu fw is not in the initrd. OTOH it > doesn't always handle the case where _some_ fw is in the initrd, but > others are not. In particular the zap fw tends to be signed with an OEM > specific key, so th

[PATCH v25 2/5] drm/xe/xe_gt_pagefault: Move pagefault struct to header

2025-05-07 Thread Jonathan Cavitt
Move the pagefault struct from xe_gt_pagefault.c to the xe_gt_pagefault_types.h header file, and move the associated enum values into the regs folder under xe_guc_pagefault_desc.h Since xe_guc_pagefault_desc.h is being initialized here, also move the xe_guc_pagefault_desc hardware formats to the n

[PATCH v25 3/5] drm/xe/uapi: Define drm_xe_vm_get_property

2025-05-07 Thread Jonathan Cavitt
Add initial declarations for the drm_xe_vm_get_property ioctl. v2: - Expand kernel docs for drm_xe_vm_get_property (Jianxun) v3: - Remove address type external definitions (Jianxun) - Add fault type to xe_drm_fault struct (Jianxun) v4: - Remove engine class and instance (Ivan) v5: - Add declare

[PATCH v25 4/5] drm/xe/xe_vm: Add per VM fault info

2025-05-07 Thread Jonathan Cavitt
Add additional information to each VM so they can report up to the first 50 seen faults. Only pagefaults are saved this way currently, though in the future, all faults should be tracked by the VM for future reporting. Additionally, of the pagefaults reported, only failed pagefaults are saved this

[PATCH v25 0/5] drm/xe/xe_vm: Implement xe_vm_get_property_ioctl

2025-05-07 Thread Jonathan Cavitt
Add additional information to each VM so they can report up to the first 50 seen faults. Only pagefaults are saved this way currently, though in the future, all faults should be tracked by the VM for future reporting. Additionally, of the pagefaults reported, only failed pagefaults are saved this

[PATCH v25 5/5] drm/xe/xe_vm: Implement xe_vm_get_property_ioctl

2025-05-07 Thread Jonathan Cavitt
Add support for userspace to request a list of observed faults from a specified VM. v2: - Only allow querying of failed pagefaults (Matt Brost) v3: - Remove unnecessary size parameter from helper function, as it is a property of the arguments. (jcavitt) - Remove unnecessary copy_from_user (Jain

[PATCH v25 1/5] drm/xe/xe_gt_pagefault: Disallow writes to read-only VMAs

2025-05-07 Thread Jonathan Cavitt
The page fault handler should reject write/atomic access to read only VMAs. Add code to handle this in handle_pagefault after the VMA lookup. Fixes: 3d420e9fa848 ("drm/xe: Rework GPU page fault handling") Signed-off-by: Jonathan Cavitt Suggested-by: Matthew Brost Reviewed-by: Shuicheng Lin Rev

Re: [PATCH 1/3] drm/panfrost: Add BO labelling to Panfrost

2025-05-07 Thread Boris Brezillon
On Wed, 7 May 2025 14:01:04 +0100 Adrián Larumbe wrote: > On 06.05.2025 08:54, Boris Brezillon wrote: > > On Thu, 24 Apr 2025 03:21:30 +0100 > > Adrián Larumbe wrote: > > > > > Unlike in Panthor, from where this change is based on, there is no need > > > to support tagging of BO's other than U

[PATCH v6 2/3] drm/tidss: Update infrastructure to support K3 DSS cut-down versions

2025-05-07 Thread Devarsh Thakkar
SoCs like AM62Lx support cut-down version of K3 DSS where although same register space is supported as in other K3 DSS supported SoCs such as AM65x, AM62x, AM62Ax but some of the resources such as planes and corresponding register spaces are truncated. For e.g. AM62Lx has only single VIDL pipeline

[PATCH v6 1/3] dt-bindings: display: ti, am65x-dss: Add support for AM62L DSS

2025-05-07 Thread Devarsh Thakkar
The DSS controller on TI's AM62L SoC is an update from that on TI's AM625/AM65x/AM62A7 SoC. The AM62L DSS [1] only supports a single display pipeline using a single overlay manager, single video port and a single video lite pipeline which does not support scaling. The output of video port is route

[PATCH v6 0/3] Add support for AM62L DSS

2025-05-07 Thread Devarsh Thakkar
This adds support for DSS subsystem present in TI's AM62L SoC which supports single display pipeline with DPI output which is also routed to DSI Tx controller within the SoC. Change Log: V6: - Move hw_id indexing logic to skip uninstantiated planes to internal functions dealing with relevant re

[PATCH v6 3/3] drm/tidss: Add support for AM62L display subsystem

2025-05-07 Thread Devarsh Thakkar
Enable display for AM62L DSS [1] which supports only a single display pipeline using a single overlay manager, single video port and a single video lite pipeline which does not support scaling. The output of video port is routed to SoC boundary via DPI interface and the DPI signals from the video

Re: [rfc] drm/ttm/memcg: simplest initial memcg/ttm integration (v2)

2025-05-07 Thread Johannes Weiner
Hello Dave, On Fri, May 02, 2025 at 01:35:59PM +1000, Dave Airlie wrote: > Hey all, > > This is my second attempt at adding the initial simple memcg/ttm > integration. > > This varies from the first attempt in two major ways: > > 1. Instead of using __GFP_ACCOUNT and direct calling kmem charges

Re: [PATCH bpf-next v3 2/5] bpf: Add dmabuf iterator

2025-05-07 Thread T.J. Mercier
On Wed, May 7, 2025 at 7:14 AM Alexei Starovoitov wrote: > > On Tue, May 6, 2025 at 5:10 PM T.J. Mercier wrote: > > > > +/** > > + * get_first_dmabuf - begin iteration through global list of DMA-bufs > > + * > > + * Returns the first buffer in the global list of DMA-bufs that's not in > > the >

Re: [PATCH bpf-next v3 2/5] bpf: Add dmabuf iterator

2025-05-07 Thread T.J. Mercier
On Wed, May 7, 2025 at 1:15 AM Christian König wrote: > > On 5/7/25 02:10, T.J. Mercier wrote: > > The dmabuf iterator traverses the list of all DMA buffers. > > > > DMA buffers are refcounted through their associated struct file. A > > reference is taken on each buffer as the list is iterated to

Re: [PATCH V1] accel/amdxdna: Support submit commands without arguments

2025-05-07 Thread Lizhi Hou
On 5/7/25 09:29, Mario Limonciello wrote: On 5/7/2025 11:15 AM, Lizhi Hou wrote: The latest userspace runtime allows generating commands which do not have any argument. Remove the corresponding check in driver IOCTL to enable this use case. Signed-off-by: Lizhi Hou Can the userspace handle

Re: [PATCH v2 10/11] drm/msm: enable separate binding of GPU and display devices

2025-05-07 Thread Dmitry Baryshkov
On Wed, 7 May 2025 at 19:43, Rob Clark wrote: > > On Sat, May 3, 2025 at 12:17 AM Dmitry Baryshkov > wrote: > > > > There are cases when we want to have separate DRM devices for GPU and > > display pipelines. > > One example is development, when it is beneficial to be able to bind the > > GPU dri

[PATCH 0/3] AMD gpu deadcoding (S more)

2025-05-07 Thread linux
From: "Dr. David Alan Gilbert" Hi, A few more AMD deadcoding patches spinning out of the questions I asked, and Kenneth answered. See: https://lore.kernel.org/all/dm4pr12mb5165d85bd85bc8fc8bf7a3b48e...@dm4pr12mb5165.namprd12.prod.outlook.com/ Dave Signed-off-by: Dr. David Alan Gilbert

[PATCH 1/3] drm/amd/pm/smu13: Remove unused smu_v13_0_init_display_count

2025-05-07 Thread linux
From: "Dr. David Alan Gilbert" smu_v13_0_init_display_count() was added in 2020 by commit c05d1c401572 ("drm/amd/swsmu: add aldebaran smu13 ip support (v3)") but is unused. See discussion on: https://lore.kernel.org/all/dm4pr12mb5165d85bd85bc8fc8bf7a3b48e...@dm4pr12mb5165.namprd12.prod.outlook.c

[PATCH 3/3] drm/amd/pm: Remove remainder of mode2_reset_is_support

2025-05-07 Thread linux
From: "Dr. David Alan Gilbert" The previous patch removed smu_mode2_reset_is_support() which was the only function to call through the mode2_reset_is_support() method pointer. Remove the remaining functions that were assigned to it and the pointer itself. See discussion at: https://lore.kernel.

[PATCH 2/3] drm/amd/pm: Remove unused smu_mode2_reset_is_support

2025-05-07 Thread linux
From: "Dr. David Alan Gilbert" smu_mode2_reset_is_support() was added in 2020 by commit 5c03e5843e6b ("drm/amdgpu:add smu mode1/2 support for aldebaran") but has remained unused. See discussion at: https://lore.kernel.org/all/dm4pr12mb5165d85bd85bc8fc8bf7a3b48e...@dm4pr12mb5165.namprd12.prod.out

RE: [PATCH v23 2/5] drm/xe/xe_gt_pagefault: Move pagefault struct to header

2025-05-07 Thread Cavitt, Jonathan
-Original Message- From: Wajdeczko, Michal Sent: Wednesday, May 7, 2025 9:34 AM To: Hirschfeld, Dafna ; Cavitt, Jonathan Cc: intel...@lists.freedesktop.org; Gupta, saurabhg ; Zuo, Alex ; joonas.lahti...@linux.intel.com; Brost, Matthew ; Zhang, Jianxun ; Lin, Shuicheng ; dri-devel@lis

Re: [PATCH v2 11/11] drm/msm: make it possible to disable GPU support

2025-05-07 Thread Rob Clark
On Sat, May 3, 2025 at 12:17 AM Dmitry Baryshkov wrote: > > Some of the platforms don't have onboard GPU or don't provide support > for the GPU in the drm/msm driver. Make it possible to disable the GPU > part of the driver and build the KMS-only part. > > Signed-off-by: Dmitry Baryshkov > --- >

Re: [PATCH v2 10/11] drm/msm: enable separate binding of GPU and display devices

2025-05-07 Thread Rob Clark
On Sat, May 3, 2025 at 12:17 AM Dmitry Baryshkov wrote: > > There are cases when we want to have separate DRM devices for GPU and > display pipelines. > One example is development, when it is beneficial to be able to bind the > GPU driver separately, without the display pipeline (and without the >

Re: [PATCH v23 2/5] drm/xe/xe_gt_pagefault: Move pagefault struct to header

2025-05-07 Thread Michal Wajdeczko
On 29.04.2025 16:22, Dafna Hirschfeld wrote: > On 24.04.2025 20:49, Jonathan Cavitt wrote: >> Move the pagefault struct from xe_gt_pagefault.c to the >> xe_gt_pagefault_types.h header file, and move the associated enum values >> into the regs folder under xe_pagefault_desc.h >> >> Since xe_pagef

Re: [PATCH v8 11/14] tee: add tee_shm_alloc_cma_phys_mem()

2025-05-07 Thread Jens Wiklander
Hi, On Fri, May 2, 2025 at 5:11 PM Robin Murphy wrote: > > On 02/05/2025 10:59 am, Jens Wiklander wrote: > > Add tee_shm_alloc_cma_phys_mem() to allocate a physical memory using > > from the default CMA pool. The memory is represented by a tee_shm object > > using the new flag TEE_SHM_CMA_BUF to

Re: [PATCH V1] accel/amdxdna: Support submit commands without arguments

2025-05-07 Thread Mario Limonciello
On 5/7/2025 11:15 AM, Lizhi Hou wrote: The latest userspace runtime allows generating commands which do not have any argument. Remove the corresponding check in driver IOCTL to enable this use case. Signed-off-by: Lizhi Hou Can the userspace handle discovery of the difference? Or does this n

[PATCH v2] drm/bridge: cdns-dsi: Replace deprecated UNIVERSAL_DEV_PM_OPS()

2025-05-07 Thread Vitor Soares
From: Vitor Soares The deprecated UNIVERSAL_DEV_PM_OPS() macro uses the provided callbacks for both runtime PM and system sleep. This causes the DSI clocks to be disabled twice: once during runtime suspend and again during system suspend, resulting in a WARN message from the clock framework when

[PATCH V1] accel/amdxdna: Support submit commands without arguments

2025-05-07 Thread Lizhi Hou
The latest userspace runtime allows generating commands which do not have any argument. Remove the corresponding check in driver IOCTL to enable this use case. Signed-off-by: Lizhi Hou --- drivers/accel/amdxdna/amdxdna_ctx.c | 22 -- 1 file changed, 12 insertions(+), 10 delet

RE: [PATCH v24 0/5] drm/xe/xe_vm: Implement xe_vm_get_property_ioctl

2025-05-07 Thread Cavitt, Jonathan
Ignore this one: I misspelt the name of a recipient -Jonathan Cavitt -Original Message- From: Cavitt, Jonathan Sent: Wednesday, May 7, 2025 8:57 AM To: intel...@lists.freedesktop.org Cc: Gupta, saurabhg ; Zuo, Alex ; Cavitt, Jonathan ; joonas.lahti...@linux.intel.com; Brost, Matthew ;

RE: [PATCH] drm/tegra: rgb: Fix the unbound reference count

2025-05-07 Thread Biju Das
Hi Thierry, > -Original Message- > From: Thierry Reding > Sent: 07 May 2025 17:00 > To: Biju Das > Subject: Re: [PATCH] drm/tegra: rgb: Fix the unbound reference count > > On Wed, Feb 05, 2025 at 11:21:35AM +, Biju Das wrote: > > The of_get_child_by_name() increments the refcount in

  1   2   3   >