Re: [PATCH RFT 0/2] drm/bridge: Use per-client debugfs entry

2025-01-26 Thread Wolfram Sang
Hi Dmitry, thanks for the review! > > The I2C core now offers a debugfs-directory per client. Use it and > > remove the custom handling in drm bridge drivers. I don't have the > > hardware, so I hope I can find people willing to test here. Build bots > > are happy. And for it6505, it even fixes a

Re: [PATCH v2 0/5] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2025-01-26 Thread Vignesh Raman
Hi Leo, On 24/01/25 13:42, Laurent Pinchart wrote: On Fri, Jan 24, 2025 at 02:11:26AM -0300, Leonardo Brás wrote: On Thu, 2025-01-23 at 19:23 +0530, Vignesh Raman wrote: This patch series introduces "kci-gitlab," a GitLab CI pipeline specifically designed for kernel testing. It provides kernel

Re: [PATCH v2] drm/virtio: Align host mapping request to maximum platform page size

2025-01-26 Thread Thomas Zimmermann
Hi Am 25.01.25 um 22:08 schrieb Sasha Finkelstein via B4 Relay: From: Sasha Finkelstein This allows running different page sizes between host and guest on platforms that support mixed page sizes. Signed-off-by: Sasha Finkelstein --- Changes in v2: - Aligned all object sizes to MAX_PAGE_SIZE

RE: [PATCH v3 2/5] drm/plane: Expose function to create format/modifier blob

2025-01-26 Thread Borah, Chaitanya Kumar
Hello Ville, > -Original Message- > From: Intel-xe On Behalf Of Murthy, > Arun R > Sent: Saturday, January 25, 2025 12:25 PM > To: Ville Syrjälä > Cc: dri-devel@lists.freedesktop.org; intel-...@lists.freedesktop.org; intel- > x...@lists.freedesktop.org > Subject: RE: [PATCH v3 2/5] drm/p

[PATCH] drm/hisilicon/hibmc: select CONFIG_DRM_DISPLAY_DP_HELPER

2025-01-26 Thread Arnd Bergmann
From: Arnd Bergmann Without the DP helper code, the newly added displayport support causes a link failure: x86_64-linux-ld: drivers/gpu/drm/hisilicon/hibmc/dp/dp_aux.o: in function `hibmc_dp_aux_init': dp_aux.c:(.text+0x37e): undefined reference to `drm_dp_aux_init' x86_64-linux-ld: drivers/gpu

Re: [PATCH v2 0/5] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2025-01-26 Thread Mauro Carvalho Chehab
Em Mon, 27 Jan 2025 08:07:38 +0200 Laurent Pinchart escreveu: > On Fri, Jan 24, 2025 at 06:12:24PM -0300, Leonardo Brás wrote: > > On Fri, 2025-01-24 at 10:45 -0500, Nicolas Dufresne wrote: > > > Le vendredi 24 janvier 2025 à 15:00 +0200, Laurent Pinchart a écrit : > > > > On Fri, Jan 24, 202

Re: [PATCH v2 0/5] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2025-01-26 Thread Mauro Carvalho Chehab
Em Fri, 24 Jan 2025 16:49:30 -0300 Helen Mae Koike Fornazier escreveu: > Hi Mauro, > > > > On Fri, 24 Jan 2025 12:29:16 -0300 Mauro Carvalho Chehab wrote --- > > > Em Fri, 24 Jan 2025 09:26:33 -0500 > > Nicolas Dufresne nicolas.dufre...@collabora.com> escreveu: > > > > > Hi,

Re: [PATCH v2 0/5] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2025-01-26 Thread Laurent Pinchart
On Fri, Jan 24, 2025 at 06:12:24PM -0300, Leonardo Brás wrote: > On Fri, 2025-01-24 at 10:45 -0500, Nicolas Dufresne wrote: > > Le vendredi 24 janvier 2025 à 15:00 +0200, Laurent Pinchart a écrit : > > > On Fri, Jan 24, 2025 at 01:52:03PM +0100, Mauro Carvalho Chehab wrote: > > > > Em Fri, 24 Jan 2

[PATCH v2 4/5] misc: fastrpc: Add polling mode support for fastRPC driver

2025-01-26 Thread Ekansh Gupta
For any remote call to DSP, after sending an invocation message, fastRPC driver waits for glink response and during this time the CPU can go into low power modes. Adding a polling mode support with which fastRPC driver will poll continuously on a memory after sending a message to remote subsystem w

[PATCH v2 2/5] misc: fastrpc: Introduce context params structure

2025-01-26 Thread Ekansh Gupta
Add structure to invoke context parameterms. This structure is meant to carry invoke context specific data. This structure is passed to internal invocation call to save the data in context. Examples of data intended to part of this structure are: CRC user memory address, poll timeout for invoke cal

[PATCH v2 3/5] misc: fastrpc: Add CRC support using invokeV2 request

2025-01-26 Thread Ekansh Gupta
InvokeV2 request is intended to support multiple enhanced invoke requests like CRC check, performance counter enablement and polling mode for RPC invocations. CRC check is getting enabled as part of this patch. CRC check for input and output argument helps in ensuring data consistency over a remote

[PATCH v2 5/5] misc: fastrpc: Modify context id mask to support polling mode

2025-01-26 Thread Ekansh Gupta
DSP needs last 4 bits of context id to be 0 for polling mode to be supported as setting of last 8 is intended for async mode(not yet supported on upstream driver) and setting these bits restrics writing to poll memory from DSP. Modify context id mask to ensure polling mode is supported. Signed-off

[PATCH v2 1/5] misc: fastrpc: Move fdlist to invoke context structure

2025-01-26 Thread Ekansh Gupta
FD list is part of meta buffer which is calulated during put args. Move fdlist to invoke context structure for better maintenance and to avoid code duplicacy for calculation of critcal meta buffer contents that are used by fastrpc driver. Signed-off-by: Ekansh Gupta --- drivers/misc/fastrpc.c |

[PATCH v2 0/5] misc: fastrpc: Add invokeV2 to support new features

2025-01-26 Thread Ekansh Gupta
This patch series adds the listed features that have been missing in upstream fastRPC driver. - Add changes to support new enhanced invocation ioctl request. - Add support for CRC check. - Add polling mode support. Userspace change: https://github.com/quic/fastrpc/pull/134 Patch [v1]: https://lo

Re: [PATCH v2 3/5] kci-gitlab: Add drm scenario

2025-01-26 Thread Vignesh Raman
Hi Sima, On 24/01/25 21:01, Simona Vetter wrote: On Fri, Jan 24, 2025 at 09:37:13AM -0300, Helen Mae Koike Fornazier wrote: Hi Simona, Thank you for your comments, On Thu, 23 Jan 2025 17:06:15 -0300 Simona Vetter wrote --- > On Thu, Jan 23, 2025 at 07:23:33PM +0530, Vignesh Raman wr

RE: [PATCH v2] drm/i915: Fix page cleanup on DMA remap failure

2025-01-26 Thread Srinivas, Vidya
> -Original Message- > From: Brian Geffon > Sent: 24 January 2025 20:50 > To: Srinivas, Vidya > Cc: intel-...@lists.freedesktop.org; Wilson, Chris P > ; Saarinen, Jani ; > Mistat, Tomasz ; ville.syrj...@linux.intel.com; > jani.nik...@linux.intel.com; linux-ker...@vger.kernel.org; dri- >

Re: [PATCH v2 5/5] kci-gitlab: docs: Add images

2025-01-26 Thread Vignesh Raman
Hi Linus, On 23/01/25 21:16, Linus Torvalds wrote: On Thu, 23 Jan 2025 at 05:56, Vignesh Raman wrote: Documentation/ci/gitlab-ci/images/drm-vkms.png | Bin 0 -> 73810 bytes .../ci/gitlab-ci/images/job-matrix.png | Bin 0 -> 2 bytes .../ci/gitlab-ci/images/new-project-runner.pn

[PATCH v1 drm-dp 1/4] drm/hisilicon/hibmc: Add dp phy cfg to adjust serdes rate, voltage and pre-emphasis

2025-01-26 Thread Yongbang Shi
From: Baihan Li This phy is inited and configured for dp, and integrating them into dp init and dp link training process. Signed-off-by: Baihan Li Signed-off-by: Yongbang Shi --- drivers/gpu/drm/hisilicon/hibmc/Makefile | 2 +- drivers/gpu/drm/hisilicon/hibmc/dp/dp_comm.h | 1 + .../g

[PATCH v1 drm-dp 3/4] drm/hisilicon/hibmc: Add debugfs interface to enable colorbar feature and get link status

2025-01-26 Thread Yongbang Shi
From: Baihan Li Create 3 files in drm debugfs: colorbar-cfg: Get/Set colorbar cfg hibmc-dp: Get dp link status hibmc-dp-edid: Print edid information Signed-off-by: Baihan Li Signed-off-by: Yongbang Shi --- drivers/gpu/drm/hisilicon/hibmc/Makefile | 3 +- drivers/gpu/drm/hisilicon/hibmc

[PATCH v1 drm-dp 4/4] drm/hisilicon/hibmc: Enable this hot plug detect of irq feature

2025-01-26 Thread Yongbang Shi
From: Baihan Li This is a series of functions about getting dp connector status function, registering irq function, interrupt handler function, and hpd event process function to realize DP HPD feature. Signed-off-by: Baihan Li Signed-off-by: Yongbang Shi --- .../gpu/drm/hisilicon/hibmc/dp/dp_

[PATCH v1 drm-dp 2/4] drm/hisilicon/hibmc: Getting connector info and edid by using aux channel

2025-01-26 Thread Yongbang Shi
From: Baihan Li Registering drm_aux and using it to get connector edid with drm functions. Refactoring some structs to fit aux's register framework. Signed-off-by: Baihan Li Signed-off-by: Yongbang Shi --- drivers/gpu/drm/hisilicon/hibmc/dp/dp_aux.c | 16 +--- drivers/gpu/drm/hisilicon/

[PATCH v1 drm-dp 0/4] Add HPD, getting EDID, colorbar features in DP function

2025-01-26 Thread Yongbang Shi
From: Baihan Li To support DP HPD, edid printing, and colorbar display features based on the Hisislcon DP devices. Baihan Li (4): drm/hisilicon/hibmc: Add dp phy cfg to adjust serdes rate, voltage and pre-emphasis drm/hisilicon/hibmc: Getting connector info and edid by using aux cha

[PATCH v1 2/2] drm/panel: panel-himax-hx83102: support for csot-pna957qt1-1 MIPI-DSI panel

2025-01-26 Thread Langyan Ye
The csot-pna957qt1-1 is a 10.95" TFT panel. The MIPI controller on this panel is the same as the other panels here, so add this panel to this driver. From the datasheet, MIPI needs to keep the LP11 state before the lcm_reset pin is pulled high, so increase lp11_before_reset flag. Signed-off-by: La

[PATCH v1 0/2] support for csot-pna957qt1-1 MIPI-DSI panel

2025-01-26 Thread Langyan Ye
The csot-pna957qt1-1 panel uses HX83102 IC, so add the compatible to the hx83102 binding files and add this panel to panel-himax-hx83102.c. Langyan Ye (2): dt-bindings: display: panel: Add compatible for CSOT PNA957QT1-1 drm/panel: panel-himax-hx83102: support for csot-pna957qt1-1 MIPI-DSI

[PATCH v1 1/2] dt-bindings: display: panel: Add compatible for CSOT PNA957QT1-1

2025-01-26 Thread Langyan Ye
Add a new compatible for the panel CSOT PNA957QT1-1. This panel uses HX83102 IC, so add the compatible to the hx83102 binding files. Signed-off-by: Langyan Ye --- .../devicetree/bindings/display/panel/himax,hx83102.yaml| 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/d

Re: [PATCH v8 12/13] drm/atomic-helper: Re-order bridge chain pre-enable and post-disable

2025-01-26 Thread Dmitry Baryshkov
On Mon, Jan 27, 2025 at 12:45:50AM +0530, Aradhya Bhatia wrote: > Move the bridge pre_enable call before crtc enable, and the bridge > post_disable call after the crtc disable. > > The sequence of enable after this patch will look like: > > bridge[n]_pre_enable > ... > bridge[1]

Re: [PATCH v8 11/13] drm/atomic-helper: Separate out bridge pre_enable/post_disable from enable/disable

2025-01-26 Thread Dmitry Baryshkov
On Mon, Jan 27, 2025 at 12:45:49AM +0530, Aradhya Bhatia wrote: > The encoder-bridge ops occur by looping over the new connector states of > the display pipelines. The enable sequence runs as follows - > > - pre_enable(bridge), > - enable(encoder), > - enable(bridge), > > while

Re: [PATCH v8 10/13] drm/atomic-helper: Refactor crtc & encoder-bridge op loops into separate functions

2025-01-26 Thread Dmitry Baryshkov
On Mon, Jan 27, 2025 at 12:45:48AM +0530, Aradhya Bhatia wrote: > From: Aradhya Bhatia > > The way any singular display pipeline, in need of a modeset, gets > enabled is as follows - > > crtc enable > (all) bridge pre-enable > encoder enable > (all) bridge enable > > - a

Re: [PATCH v8 02/13] drm/bridge: cdns-dsi: Fix phy de-init and flag it so

2025-01-26 Thread Dmitry Baryshkov
On Mon, Jan 27, 2025 at 12:45:40AM +0530, Aradhya Bhatia wrote: > From: Aradhya Bhatia > > The driver code doesn't have a Phy de-initialization path as yet, and so > it does not clear the phy_initialized flag while suspending. This is a > problem because after resume the driver looks at this flag

Re: [PATCH v8 01/13] drm/bridge: cdns-dsi: Fix connecting to next bridge

2025-01-26 Thread Dmitry Baryshkov
On Mon, Jan 27, 2025 at 12:45:39AM +0530, Aradhya Bhatia wrote: > From: Aradhya Bhatia > > Fix the OF node pointer passed to the of_drm_find_bridge() call to find > the next bridge in the display chain. > > The code to find the next panel (and create its panel-bridge) works > fine, but to find t

Re: [PATCH] gpu: cdns-mhdp8546: fix call balance of mhdp->clk handling routines

2025-01-26 Thread Dmitry Baryshkov
On Fri, Jan 24, 2025 at 08:00:09PM +0300, Vitalii Mordan wrote: > If the clock mhdp->clk was not enabled in cdns_mhdp_probe(), it should not > be disabled in any path. > > Found by Linux Verification Center (linuxtesting.org) with Klever. > > Fixes: fb43aa0acdfd ("drm: bridge: Add support for Cad

[PATCH v1] drm/virtio: Extend blob UAPI with deferred-mapping hinting

2025-01-26 Thread Dmitry Osipenko
If userspace never maps GEM object, then BO wastes hostmem space because VirtIO-GPU driver maps VRAM BO at the BO's creating time. Make mappings on-demand by adding new RESOURCE_CREATE_BLOB IOCTL/UAPI hinting flag telling that host mapping should be deferred until first mapping is made when the fl

[PATCH v8 06/13] drm/bridge: cdns-dsi: Move to devm_drm_of_get_bridge()

2025-01-26 Thread Aradhya Bhatia
From: Aradhya Bhatia Instead of manually finding the next bridge/panel, and maintaining the panel-bridge (in-case the next entity is a panel), switch to using the automatically managing devm_drm_of_get_bridge() API. Drop the drm_panel support completely from the driver while at it. Reviewed-by:

[PATCH v8 01/13] drm/bridge: cdns-dsi: Fix connecting to next bridge

2025-01-26 Thread Aradhya Bhatia
From: Aradhya Bhatia Fix the OF node pointer passed to the of_drm_find_bridge() call to find the next bridge in the display chain. The code to find the next panel (and create its panel-bridge) works fine, but to find the next (non-panel) bridge does not. To find the next bridge in the pipeline,

[PATCH v8 13/13] drm/bridge: cdns-dsi: Use pre_enable/post_disable to enable/disable

2025-01-26 Thread Aradhya Bhatia
From: Aradhya Bhatia The cdns-dsi controller requires that it be turned on completely before the input DPI's source has begun streaming[0]. Not having that, allows for a small window before cdns-dsi enable and after cdns-dsi disable where the previous entity (in this case tidss's videoport) to co

[PATCH v8 12/13] drm/atomic-helper: Re-order bridge chain pre-enable and post-disable

2025-01-26 Thread Aradhya Bhatia
Move the bridge pre_enable call before crtc enable, and the bridge post_disable call after the crtc disable. The sequence of enable after this patch will look like: bridge[n]_pre_enable ... bridge[1]_pre_enable crtc_enable encoder_enable bridge[1]

[PATCH v8 11/13] drm/atomic-helper: Separate out bridge pre_enable/post_disable from enable/disable

2025-01-26 Thread Aradhya Bhatia
The encoder-bridge ops occur by looping over the new connector states of the display pipelines. The enable sequence runs as follows - - pre_enable(bridge), - enable(encoder), - enable(bridge), while the disable sequnce runs as follows - - disable(bridge),

[PATCH v8 10/13] drm/atomic-helper: Refactor crtc & encoder-bridge op loops into separate functions

2025-01-26 Thread Aradhya Bhatia
From: Aradhya Bhatia The way any singular display pipeline, in need of a modeset, gets enabled is as follows - crtc enable (all) bridge pre-enable encoder enable (all) bridge enable - and the disable sequence is exactly the reverse of this. The crtc operations o

[PATCH v8 09/13] drm/bridge: cdns-dsi: Move DSI mode check to _atomic_check()

2025-01-26 Thread Aradhya Bhatia
From: Aradhya Bhatia At present, the DSI mode configuration check happens during the _atomic_enable() phase, which is not really the best place for this. Moreover, if the mode is not valid, the driver gives a warning and continues the hardware configuration. Move the DSI mode configuration check

[PATCH v8 08/13] drm/bridge: cdns-dsi: Support atomic bridge APIs

2025-01-26 Thread Aradhya Bhatia
From: Aradhya Bhatia Change the existing (and deprecated) bridge hooks, to the bridge atomic APIs. Add drm helpers for duplicate_state, destroy_state, and bridge_reset bridge hooks. Further add support for the input format negotiation hook. Reviewed-by: Dmitry Baryshkov Reviewed-by: Tomi Valk

[PATCH v8 07/13] drm/mipi-dsi: Add helper to find input format

2025-01-26 Thread Aradhya Bhatia
From: Aradhya Bhatia Add a helper API that can be used by the DSI hosts to find the required input bus format for the given output dsi pixel format. Reviewed-by: Dmitry Baryshkov Reviewed-by: Tomi Valkeinen Signed-off-by: Aradhya Bhatia Signed-off-by: Aradhya Bhatia --- drivers/gpu/drm/drm_

[PATCH v8 05/13] drm/bridge: cdns-dsi: Wait for Clk and Data Lanes to be ready

2025-01-26 Thread Aradhya Bhatia
From: Aradhya Bhatia Once the DSI Link and DSI Phy are initialized, the code needs to wait for Clk and Data Lanes to be ready, before continuing configuration. This is in accordance with the DSI Start-up procedure, found in the Technical Reference Manual of Texas Instrument's J721E SoC[0] which h

[PATCH v8 04/13] drm/bridge: cdns-dsi: Check return value when getting default PHY config

2025-01-26 Thread Aradhya Bhatia
From: Aradhya Bhatia Check for the return value of the phy_mipi_dphy_get_default_config() call, and incase of an error, return back the same. Fixes: fced5a364dee ("drm/bridge: cdns: Convert to phy framework") Cc: Stable List Reviewed-by: Tomi Valkeinen Reviewed-by: Dmitry Baryshkov Signed-off

[PATCH v8 03/13] drm/bridge: cdns-dsi: Fix the clock variable for mode_valid()

2025-01-26 Thread Aradhya Bhatia
From: Aradhya Bhatia The crtc_* mode parameters do not get generated (duplicated in this case) from the regular parameters before the mode validation phase begins. The rest of the code conditionally uses the crtc_* parameters only during the bridge enable phase, but sticks to the regular paramet

[PATCH v8 02/13] drm/bridge: cdns-dsi: Fix phy de-init and flag it so

2025-01-26 Thread Aradhya Bhatia
From: Aradhya Bhatia The driver code doesn't have a Phy de-initialization path as yet, and so it does not clear the phy_initialized flag while suspending. This is a problem because after resume the driver looks at this flag to determine if a Phy re-initialization is required or not. It is in fact

[PATCH v8 00/13] drm/bridge: cdns-dsi: Fix the color-shift issue

2025-01-26 Thread Aradhya Bhatia
Hello all, This series provides some crucial fixes and improvements for the Cadence's DSI TX (cdns-dsi) controller found commonly in Texas Instruments' J7 family of SoCs, as well as in Sitara AM62P and AM62L SoCs. Along with that, this series aims to fix the color-shift issue that has been going

Re: [PATCH v16 5/7] drm/vkms: Create KUnit tests for YUV conversions

2025-01-26 Thread Maxime Ripard
On Tue, Jan 21, 2025 at 11:48:06AM +0100, Louis Chauvet wrote: > +static struct yuv_u8_to_argb_u16_case yuv_u8_to_argb_u16_cases[] = { > + /* > + * colour.RGB_to_YCbCr(, > + * K=colour.WEIGHTS_YCBCR["ITU-R BT.601"], > + * in_bits = 16, > +

[PATCH AUTOSEL 6.6 2/3] fbdev: omap: use threaded IRQ for LCD DMA

2025-01-26 Thread Sasha Levin
From: Aaro Koskinen [ Upstream commit e4b6b665df815b4841e71b72f06446884e8aad40 ] When using touchscreen and framebuffer, Nokia 770 crashes easily with: BUG: scheduling while atomic: irq/144-ads7846/82/0x0001 Modules linked in: usb_f_ecm g_ether usb_f_rndis u_ether libcomposite conf

[BUG,BISECTED] WARNING dcn20_find_secondary_pipe

2025-01-26 Thread Chris Bainbridge
Hardware is HP Pavilion Aero 13 laptop with Dell WD19 dock and three external monitors. I get a warning with recent kernel builds when enabling the external monitors with xrandr after initial boot: 16:57:49 kernel: WARNING: CPU: 4 PID: 1347 at drivers/gpu/drm/amd/amdgpu/../display/dc/resource/dcn

[PATCH AUTOSEL 6.1 2/2] fbdev: omap: use threaded IRQ for LCD DMA

2025-01-26 Thread Sasha Levin
From: Aaro Koskinen [ Upstream commit e4b6b665df815b4841e71b72f06446884e8aad40 ] When using touchscreen and framebuffer, Nokia 770 crashes easily with: BUG: scheduling while atomic: irq/144-ads7846/82/0x0001 Modules linked in: usb_f_ecm g_ether usb_f_rndis u_ether libcomposite conf

[PATCH AUTOSEL 6.12 4/7] fbdev: omap: use threaded IRQ for LCD DMA

2025-01-26 Thread Sasha Levin
From: Aaro Koskinen [ Upstream commit e4b6b665df815b4841e71b72f06446884e8aad40 ] When using touchscreen and framebuffer, Nokia 770 crashes easily with: BUG: scheduling while atomic: irq/144-ads7846/82/0x0001 Modules linked in: usb_f_ecm g_ether usb_f_rndis u_ether libcomposite conf

[PATCH AUTOSEL 6.13 5/8] fbdev: omap: use threaded IRQ for LCD DMA

2025-01-26 Thread Sasha Levin
From: Aaro Koskinen [ Upstream commit e4b6b665df815b4841e71b72f06446884e8aad40 ] When using touchscreen and framebuffer, Nokia 770 crashes easily with: BUG: scheduling while atomic: irq/144-ads7846/82/0x0001 Modules linked in: usb_f_ecm g_ether usb_f_rndis u_ether libcomposite conf

Re: [PATCH v6 2/7] drm/msm/hdmi: program HDMI timings during atomic_pre_enable

2025-01-26 Thread Maxime Ripard
On Fri, Jan 24, 2025 at 11:47:42PM +0200, Dmitry Baryshkov wrote: > The mode_set callback is deprecated, it doesn't get the > drm_bridge_state, just mode-related argumetns. Also Abhinav pointed out > that HDMI timings should be programmed after setting up HDMI PHY and > PLL. Rework the code to prog

Re: [PATCH] cgroup/dmem: Don't clobber pool in dmem_cgroup_calculate_protection

2025-01-26 Thread Friedrich Vock
On 24.01.25 10:56, Michal Koutný wrote: On Fri, Jan 17, 2025 at 08:02:55PM +0100, Friedrich Vock wrote: Yeah, there are pools for the whole path between limit_pool and test_pool, but the issue is that we traverse the entire tree of cgroups, and we don't always stay on the path between limit_po

Re: [PATCH v2] drm/bridge: Use devm_platform_get_and_ioremap_resource()

2025-01-26 Thread Maxime Ripard
On Wed, Jan 22, 2025 at 10:56:00AM +0800, oushixiong1...@163.com wrote: > From: Shixiong Ou > > Convert platform_get_resource(), devm_ioremap_resource() to a single call to > devm_platform_get_and_ioremap_resource(). > > Signed-off-by: Shixiong Ou > --- > V1 -> V2: Add Missing commit message. >

Re: [PATCH AUTOSEL 6.12 02/31] drm: Add panel backlight quirks

2025-01-26 Thread Thomas Weißschuh
Hi Sasha, On 2025-01-26 09:54:18-0500, Sasha Levin wrote: > From: Thomas Weißschuh > > [ Upstream commit 22e5c7ae12145af13785e3ff138395d5b1a22116 ] > > Panels using a PWM-controlled backlight source do not have a standard > way to communicate their valid PWM ranges. > On x86 the ranges are read

[PATCH AUTOSEL 6.13 25/34] drm/amdkfd: Queue interrupt work to different CPU

2025-01-26 Thread Sasha Levin
From: Philip Yang [ Upstream commit 34db5a32617d102e8042151bb87590e43c97132e ] For CPX mode, each KFD node has interrupt worker to process ih_fifo to send events to user space. Currently all interrupt workers of same adev queue to same CPU, all workers execution are actually serialized and this

[PATCH v2 0/5] Handheld gaming PC panel orientation quirks

2025-01-26 Thread John Edwards
Hello. I am submitting a small number of patches to add panel rotation quirks for a few handheld gaming PCs. These patches were created by the SteamFork team and are in daily use by us and/or members of our community. The following devices are covered by these patches: 1: AYANEO 2S 2: AYANEO Fli

[PATCH AUTOSEL 6.13 13/34] drm/msm/dpu: filter out too wide modes if no 3dmux is present

2025-01-26 Thread Sasha Levin
From: Abhinav Kumar [ Upstream commit dbc7bb1a93f41c533fe31ddc97bdf777d7a61faa ] On chipsets such as QCS615, there is no 3dmux present. In such a case, a layer exceeding the max_mixer_width cannot be split, hence cannot be supported. Filter out the modes which exceed the max_mixer_width when th

[PATCH AUTOSEL 6.6 10/17] drm/vc4: hdmi: use eld_mutex to protect access to connector->eld

2025-01-26 Thread Sasha Levin
From: Dmitry Baryshkov [ Upstream commit 81a9a93b169a273ccc4a9a1ee56f17e9981d3f98 ] Reading access to connector->eld can happen at the same time the drm_edid_to_eld() updates the data. Take the newly added eld_mutex in order to protect connector->eld from concurrent access. Reviewed-by: Maxime

[PATCH AUTOSEL 6.6 07/17] drm/exynos: hdmi: use eld_mutex to protect access to connector->eld

2025-01-26 Thread Sasha Levin
From: Dmitry Baryshkov [ Upstream commit 5e8436d334ed7f6785416447c50b42077c6503e0 ] Reading access to connector->eld can happen at the same time the drm_edid_to_eld() updates the data. Take the newly added eld_mutex in order to protect connector->eld from concurrent access. Reviewed-by: Maxime

[PATCH AUTOSEL 6.13 09/34] drm/tests: hdmi: return meaningful value from set_connector_edid()

2025-01-26 Thread Sasha Levin
From: Dmitry Baryshkov [ Upstream commit a8403be6eea91e4f5d8ad5dbc463dd08339eaece ] The set_connector_edid() function returns a bogus 0, performing the check on the connector->funcs->fill_modes() result internally. Make the function pass the fill_modes()'s return value to the caller and move cor

[PATCH AUTOSEL 6.12 04/31] drm: panel-backlight-quirks: Add Framework 13 glossy and 2.8k panels

2025-01-26 Thread Sasha Levin
From: "Dustin L. Howett" [ Upstream commit d80b5c5b9be6b2e1cdeaaeaa8259523b63cae292 ] I have tested these panels on the Framework Laptop 13 AMD with firmware revision 3.05 (latest at time of submission). Signed-off-by: Dustin L. Howett Signed-off-by: Thomas Weißschuh Reviewed-by: Mario Limonc

[PATCH AUTOSEL 6.13 06/34] nvkm/gsp: correctly advance the read pointer of GSP message queue

2025-01-26 Thread Sasha Levin
From: Zhi Wang [ Upstream commit 8d9beb4aebc02c4bd09e1d39c9c5f1c68c786dbc ] A GSP event message consists three parts: message header, RPC header, message body. GSP calculates the number of pages to write from the total size of a GSP message. This behavior can be observed from the movement of the

[PATCH AUTOSEL 5.15 2/3] drm/sti: hdmi: use eld_mutex to protect access to connector->eld

2025-01-26 Thread Sasha Levin
From: Dmitry Baryshkov [ Upstream commit e99c0b517bcd53cf61f998a3c4291333401cb391 ] Reading access to connector->eld can happen at the same time the drm_edid_to_eld() updates the data. Take the newly added eld_mutex in order to protect connector->eld from concurrent access. Reviewed-by: Maxime

[PATCH AUTOSEL 5.10 2/3] drm/sti: hdmi: use eld_mutex to protect access to connector->eld

2025-01-26 Thread Sasha Levin
From: Dmitry Baryshkov [ Upstream commit e99c0b517bcd53cf61f998a3c4291333401cb391 ] Reading access to connector->eld can happen at the same time the drm_edid_to_eld() updates the data. Take the newly added eld_mutex in order to protect connector->eld from concurrent access. Reviewed-by: Maxime

[PATCH AUTOSEL 5.4 2/2] drm/sti: hdmi: use eld_mutex to protect access to connector->eld

2025-01-26 Thread Sasha Levin
From: Dmitry Baryshkov [ Upstream commit e99c0b517bcd53cf61f998a3c4291333401cb391 ] Reading access to connector->eld can happen at the same time the drm_edid_to_eld() updates the data. Take the newly added eld_mutex in order to protect connector->eld from concurrent access. Reviewed-by: Maxime

[PATCH AUTOSEL 6.1 6/9] drm/bridge: it6505: fix HDCP Bstatus check

2025-01-26 Thread Sasha Levin
From: Hermes Wu [ Upstream commit 0fd2ff47d8c207fa3173661de04bb9e8201c0ad2 ] When HDCP is activated, a DisplayPort source receiving CP_IRQ from the sink shall check Bstatus from DPCD and process the corresponding value Reviewed-by: Dmitry Baryshkov Signed-off-by: Hermes Wu Reviewed-by: Angelo

[PATCH AUTOSEL 6.1 7/9] drm/bridge: it6505: fix HDCP encryption when R0 ready

2025-01-26 Thread Sasha Levin
From: Hermes Wu [ Upstream commit 8c01b0bae2f9e58f2fee0e811cb90d8331986554 ] When starting HDCP authentication, HDCP encryption should be enabled when R0'is checked. Change encryption enables time at R0' ready. The hardware HDCP engine trigger is changed and the repeater KSV fails will restart

[PATCH AUTOSEL 6.1 8/9] drm/bridge: it6505: fix HDCP CTS compare V matching

2025-01-26 Thread Sasha Levin
From: Hermes Wu [ Upstream commit 0989c02c7a5c887c70afeae80c64d0291624e1a7 ] When HDCP negotiation with a repeater device. Checking SHA V' matching must retry 3 times before restarting HDCP. Signed-off-by: Hermes Wu Reviewed-by: AngeloGioacchino Del Regno Signed-off-by: Dmitry Baryshkov Lin

[PATCH AUTOSEL 6.6 16/17] drm/bridge: it6505: fix HDCP CTS KSV list wait timer

2025-01-26 Thread Sasha Levin
From: Hermes Wu [ Upstream commit 9f9eef9ec1a2b57d95a86fe81df758e8253a7766 ] HDCP must disabled encryption and restart authentication after waiting KSV for 5s. The original method uses a counter in a waitting loop that may wait much longer than it is supposed to. Use time_after() for KSV wait ti

[PATCH AUTOSEL 6.1 5/9] drm/bridge: it6505: Change definition MAX_HDCP_DOWN_STREAM_COUNT

2025-01-26 Thread Sasha Levin
From: Hermes Wu [ Upstream commit 85597bc0d70c287ba41f17d14d3d857a38a3d727 ] A HDCP source device shall support max downstream to 127 devices. Change definition MAX_HDCP_DOWN_STREAM_COUNT to 127 KSVs shall save for DRM blocked devices check. This results in struct it6505 growth by ~0.5 KiB. Re

[PATCH AUTOSEL 6.1 4/9] drm/amd/display: Fix Mode Cutoff in DSC Passthrough to DP2.1 Monitor

2025-01-26 Thread Sasha Levin
From: Fangzhi Zuo [ Upstream commit e56ad45e991128bf4db160b75a1d9f647a341d8f ] Source --> DP2.1 MST hub --> DP1.4/2.1 monitor When change from DP1.4 to DP2.1 from monitor manual, modes higher than 4k120 are all cutoff by mode validation. Switch back to DP1.4 gets all the modes up to 4k240 avail

[PATCH AUTOSEL 6.6 11/17] drm/amd/display: Fix Mode Cutoff in DSC Passthrough to DP2.1 Monitor

2025-01-26 Thread Sasha Levin
From: Fangzhi Zuo [ Upstream commit e56ad45e991128bf4db160b75a1d9f647a341d8f ] Source --> DP2.1 MST hub --> DP1.4/2.1 monitor When change from DP1.4 to DP2.1 from monitor manual, modes higher than 4k120 are all cutoff by mode validation. Switch back to DP1.4 gets all the modes up to 4k240 avail

[PATCH AUTOSEL 6.1 3/9] drm/sti: hdmi: use eld_mutex to protect access to connector->eld

2025-01-26 Thread Sasha Levin
From: Dmitry Baryshkov [ Upstream commit e99c0b517bcd53cf61f998a3c4291333401cb391 ] Reading access to connector->eld can happen at the same time the drm_edid_to_eld() updates the data. Take the newly added eld_mutex in order to protect connector->eld from concurrent access. Reviewed-by: Maxime

[PATCH AUTOSEL 6.1 1/9] drm/virtio: New fence for every plane update

2025-01-26 Thread Sasha Levin
From: Dongwon Kim [ Upstream commit d3c55b8ab6fe5fa2e7ab02efd36d09c39ee5022f ] Having a fence linked to a virtio_gpu_framebuffer in the plane update sequence would cause conflict when several planes referencing the same framebuffer (e.g. Xorg screen covering multi-displays configured for an exte

[PATCH AUTOSEL 6.6 15/17] drm/bridge: it6505: fix HDCP CTS compare V matching

2025-01-26 Thread Sasha Levin
From: Hermes Wu [ Upstream commit 0989c02c7a5c887c70afeae80c64d0291624e1a7 ] When HDCP negotiation with a repeater device. Checking SHA V' matching must retry 3 times before restarting HDCP. Signed-off-by: Hermes Wu Reviewed-by: AngeloGioacchino Del Regno Signed-off-by: Dmitry Baryshkov Lin

[PATCH AUTOSEL 6.6 09/17] drm/sti: hdmi: use eld_mutex to protect access to connector->eld

2025-01-26 Thread Sasha Levin
From: Dmitry Baryshkov [ Upstream commit e99c0b517bcd53cf61f998a3c4291333401cb391 ] Reading access to connector->eld can happen at the same time the drm_edid_to_eld() updates the data. Take the newly added eld_mutex in order to protect connector->eld from concurrent access. Reviewed-by: Maxime

[PATCH AUTOSEL 6.6 14/17] drm/bridge: it6505: fix HDCP encryption when R0 ready

2025-01-26 Thread Sasha Levin
From: Hermes Wu [ Upstream commit 8c01b0bae2f9e58f2fee0e811cb90d8331986554 ] When starting HDCP authentication, HDCP encryption should be enabled when R0'is checked. Change encryption enables time at R0' ready. The hardware HDCP engine trigger is changed and the repeater KSV fails will restart

[PATCH AUTOSEL 6.6 12/17] drm/bridge: it6505: Change definition MAX_HDCP_DOWN_STREAM_COUNT

2025-01-26 Thread Sasha Levin
From: Hermes Wu [ Upstream commit 85597bc0d70c287ba41f17d14d3d857a38a3d727 ] A HDCP source device shall support max downstream to 127 devices. Change definition MAX_HDCP_DOWN_STREAM_COUNT to 127 KSVs shall save for DRM blocked devices check. This results in struct it6505 growth by ~0.5 KiB. Re

[PATCH AUTOSEL 6.6 13/17] drm/bridge: it6505: fix HDCP Bstatus check

2025-01-26 Thread Sasha Levin
From: Hermes Wu [ Upstream commit 0fd2ff47d8c207fa3173661de04bb9e8201c0ad2 ] When HDCP is activated, a DisplayPort source receiving CP_IRQ from the sink shall check Bstatus from DPCD and process the corresponding value Reviewed-by: Dmitry Baryshkov Signed-off-by: Hermes Wu Reviewed-by: Angelo

[PATCH AUTOSEL 6.6 05/17] drm/bridge: ite-it66121: use eld_mutex to protect access to connector->eld

2025-01-26 Thread Sasha Levin
From: Dmitry Baryshkov [ Upstream commit 39ead6e02ea7d19b421e9d42299d4293fed3064e ] Reading access to connector->eld can happen at the same time the drm_edid_to_eld() updates the data. Take the newly added eld_mutex in order to protect connector->eld from concurrent access. Reviewed-by: Maxime

[PATCH AUTOSEL 6.6 08/17] drm/radeon: use eld_mutex to protect access to connector->eld

2025-01-26 Thread Sasha Levin
From: Dmitry Baryshkov [ Upstream commit b54c14f82428c8a602392d4cae1958a71a578132 ] Reading access to connector->eld can happen at the same time the drm_edid_to_eld() updates the data. Take the newly added eld_mutex in order to protect connector->eld from concurrent access. Reviewed-by: Maxime

[PATCH AUTOSEL 6.6 06/17] drm/amd/display: use eld_mutex to protect access to connector->eld

2025-01-26 Thread Sasha Levin
From: Dmitry Baryshkov [ Upstream commit 819bee01eea06282d7bda17d46caf29cae4f6d84 ] Reading access to connector->eld can happen at the same time the drm_edid_to_eld() updates the data. Take the newly added eld_mutex in order to protect connector->eld from concurrent access. Reviewed-by: Maxime

[PATCH AUTOSEL 6.12 25/31] drm/bridge: it6505: fix HDCP encryption when R0 ready

2025-01-26 Thread Sasha Levin
From: Hermes Wu [ Upstream commit 8c01b0bae2f9e58f2fee0e811cb90d8331986554 ] When starting HDCP authentication, HDCP encryption should be enabled when R0'is checked. Change encryption enables time at R0' ready. The hardware HDCP engine trigger is changed and the repeater KSV fails will restart

[PATCH AUTOSEL 6.6 04/17] drm/bridge: anx7625: use eld_mutex to protect access to connector->eld

2025-01-26 Thread Sasha Levin
From: Dmitry Baryshkov [ Upstream commit e72bf423a60afd744d13e40ab2194044a3af5217 ] Reading access to connector->eld can happen at the same time the drm_edid_to_eld() updates the data. Take the newly added eld_mutex in order to protect connector->eld from concurrent access. Reviewed-by: Maxime

[PATCH AUTOSEL 6.12 21/31] drm/amdgpu: Don't enable sdma 4.4.5 CTXEMPTY interrupt

2025-01-26 Thread Sasha Levin
From: Philip Yang [ Upstream commit b4b7271e5ca95b581f2fcc4ae852c4079215e92d ] The sdma context empty interrupt is dropped in amdgpu_irq_dispatch as unregistered interrupt src_id 243, this interrupt accounts to 1/3 of total interrupts and causes IH primary ring overflow when running stressful be

[PATCH AUTOSEL 6.6 03/17] drm/connector: add mutex to protect ELD from concurrent access

2025-01-26 Thread Sasha Levin
From: Dmitry Baryshkov [ Upstream commit df7c8e3dde37a9d81c0613285b43600f3cc70f34 ] The connector->eld is accessed by the .get_eld() callback. This access can collide with the drm_edid_to_eld() updating the data at the same time. Add drm_connector.eld_mutex to protect the data from concurrenct a

[PATCH AUTOSEL 6.6 01/17] drm/virtio: New fence for every plane update

2025-01-26 Thread Sasha Levin
From: Dongwon Kim [ Upstream commit d3c55b8ab6fe5fa2e7ab02efd36d09c39ee5022f ] Having a fence linked to a virtio_gpu_framebuffer in the plane update sequence would cause conflict when several planes referencing the same framebuffer (e.g. Xorg screen covering multi-displays configured for an exte

[PATCH AUTOSEL 6.12 30/31] drm/amd/display: Limit Scaling Ratio on DCN3.01

2025-01-26 Thread Sasha Levin
From: Gabe Teeger [ Upstream commit abc0ad6d08440761b199988c329ad7ac83f41c9b ] [why] Underflow and flickering was occuring due to high scaling ratios when resizing videos. [how] Limit the scaling ratios by increasing the max scaling factor Reviewed-by: Nicholas Kazlauskas Signed-off-by: Gabe

[PATCH AUTOSEL 6.12 26/31] drm/bridge: it6505: fix HDCP CTS compare V matching

2025-01-26 Thread Sasha Levin
From: Hermes Wu [ Upstream commit 0989c02c7a5c887c70afeae80c64d0291624e1a7 ] When HDCP negotiation with a repeater device. Checking SHA V' matching must retry 3 times before restarting HDCP. Signed-off-by: Hermes Wu Reviewed-by: AngeloGioacchino Del Regno Signed-off-by: Dmitry Baryshkov Lin

[PATCH AUTOSEL 6.12 27/31] drm/bridge: it6505: fix HDCP CTS KSV list wait timer

2025-01-26 Thread Sasha Levin
From: Hermes Wu [ Upstream commit 9f9eef9ec1a2b57d95a86fe81df758e8253a7766 ] HDCP must disabled encryption and restart authentication after waiting KSV for 5s. The original method uses a counter in a waitting loop that may wait much longer than it is supposed to. Use time_after() for KSV wait ti

[PATCH AUTOSEL 6.12 24/31] drm/bridge: it6505: fix HDCP Bstatus check

2025-01-26 Thread Sasha Levin
From: Hermes Wu [ Upstream commit 0fd2ff47d8c207fa3173661de04bb9e8201c0ad2 ] When HDCP is activated, a DisplayPort source receiving CP_IRQ from the sink shall check Bstatus from DPCD and process the corresponding value Reviewed-by: Dmitry Baryshkov Signed-off-by: Hermes Wu Reviewed-by: Angelo

[PATCH AUTOSEL 6.12 29/31] drm/amd/display: Increase sanitizer frame larger than limit when compile testing with clang

2025-01-26 Thread Sasha Levin
From: Nathan Chancellor [ Upstream commit e4479aecf6581af81bc0908575447878d2a07e01 ] Commit 24909d9ec7c3 ("drm/amd/display: Overwriting dualDPP UBF values before usage") added a new warning in dml2/display_mode_core.c when building allmodconfig with clang: drivers/gpu/drm/amd/amdgpu/../displa

[PATCH AUTOSEL 6.12 16/31] drm/exynos: hdmi: use eld_mutex to protect access to connector->eld

2025-01-26 Thread Sasha Levin
From: Dmitry Baryshkov [ Upstream commit 5e8436d334ed7f6785416447c50b42077c6503e0 ] Reading access to connector->eld can happen at the same time the drm_edid_to_eld() updates the data. Take the newly added eld_mutex in order to protect connector->eld from concurrent access. Reviewed-by: Maxime

[PATCH AUTOSEL 6.12 23/31] drm/bridge: it6505: Change definition MAX_HDCP_DOWN_STREAM_COUNT

2025-01-26 Thread Sasha Levin
From: Hermes Wu [ Upstream commit 85597bc0d70c287ba41f17d14d3d857a38a3d727 ] A HDCP source device shall support max downstream to 127 devices. Change definition MAX_HDCP_DOWN_STREAM_COUNT to 127 KSVs shall save for DRM blocked devices check. This results in struct it6505 growth by ~0.5 KiB. Re

[PATCH AUTOSEL 6.12 22/31] drm/amdkfd: Queue interrupt work to different CPU

2025-01-26 Thread Sasha Levin
From: Philip Yang [ Upstream commit 34db5a32617d102e8042151bb87590e43c97132e ] For CPX mode, each KFD node has interrupt worker to process ih_fifo to send events to user space. Currently all interrupt workers of same adev queue to same CPU, all workers execution are actually serialized and this

[PATCH AUTOSEL 6.12 13/31] drm/bridge: anx7625: use eld_mutex to protect access to connector->eld

2025-01-26 Thread Sasha Levin
From: Dmitry Baryshkov [ Upstream commit e72bf423a60afd744d13e40ab2194044a3af5217 ] Reading access to connector->eld can happen at the same time the drm_edid_to_eld() updates the data. Take the newly added eld_mutex in order to protect connector->eld from concurrent access. Reviewed-by: Maxime

[PATCH AUTOSEL 6.12 20/31] drm/amd/display: Fix Mode Cutoff in DSC Passthrough to DP2.1 Monitor

2025-01-26 Thread Sasha Levin
From: Fangzhi Zuo [ Upstream commit e56ad45e991128bf4db160b75a1d9f647a341d8f ] Source --> DP2.1 MST hub --> DP1.4/2.1 monitor When change from DP1.4 to DP2.1 from monitor manual, modes higher than 4k120 are all cutoff by mode validation. Switch back to DP1.4 gets all the modes up to 4k240 avail

[PATCH AUTOSEL 6.12 18/31] drm/sti: hdmi: use eld_mutex to protect access to connector->eld

2025-01-26 Thread Sasha Levin
From: Dmitry Baryshkov [ Upstream commit e99c0b517bcd53cf61f998a3c4291333401cb391 ] Reading access to connector->eld can happen at the same time the drm_edid_to_eld() updates the data. Take the newly added eld_mutex in order to protect connector->eld from concurrent access. Reviewed-by: Maxime

  1   2   >