[PATCH] drm/i915/uc: Include requested frequency in slow firmware load messages

2024-12-20 Thread John . C . Harrison
From: John Harrison To aid debug of sporadic issues, include the requested frequency in the debug message as well as the actual frequency. That way we know for certain that the clamping is not because the driver forgot to ask. Signed-off-by: John Harrison Reviewed-by: Vinay Belgaumkar --- dri

Re: [PATCH 2/2] drm/i915/lttpr: Enable Extended Wake Timeout

2024-12-20 Thread kernel test robot
Hi Suraj, kernel test robot noticed the following build warnings: [auto build test WARNING on linus/master] [also build test WARNING on drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-tip/drm-tip v6.13-rc3 next-20241220] [If your patch is applied to the wrong git tree, kindly drop

[PATCH] drm/i915: Add debug print about hw config table size

2024-12-20 Thread John . C . Harrison
From: John Harrison Add debug info to help investigate a very rare bug: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13385 Signed-off-by: John Harrison --- drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/i915/g

Re: [PATCH v4 18/25] drm/msm/dpu: Reserve resources for CWB

2024-12-20 Thread Dmitry Baryshkov
On Fri, Dec 20, 2024 at 04:12:29PM -0800, Jessica Zhang wrote: > > > On 12/19/2024 9:52 PM, Dmitry Baryshkov wrote: > > On Mon, Dec 16, 2024 at 04:43:29PM -0800, Jessica Zhang wrote: > > > Add support for RM to reserve dedicated CWB PINGPONGs and CWB muxes > > > > > > For concurrent writeback, e

Re: [PATCH 2/2] drm/i915/lttpr: Enable Extended Wake Timeout

2024-12-20 Thread kernel test robot
Hi Suraj, kernel test robot noticed the following build errors: [auto build test ERROR on linus/master] [also build test ERROR on v6.13-rc3 next-20241220] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as

Re: [PATCH v4 18/25] drm/msm/dpu: Reserve resources for CWB

2024-12-20 Thread Jessica Zhang
On 12/19/2024 9:52 PM, Dmitry Baryshkov wrote: On Mon, Dec 16, 2024 at 04:43:29PM -0800, Jessica Zhang wrote: Add support for RM to reserve dedicated CWB PINGPONGs and CWB muxes For concurrent writeback, even-indexed CWB muxes must be assigned to even-indexed LMs and odd-indexed CWB muxes fo

[PATCH v4 1/3] drm/drm_mm: Safe macro for iterating through nodes in range

2024-12-20 Thread Tomasz Lis
Benefits of drm_mm_for_each_node_safe and drm_mm_for_each_node_in_range squished together into one macro. Signed-off-by: Tomasz Lis --- Cc: dri-devel@lists.freedesktop.org include/drm/drm_mm.h | 19 +++ 1 file changed, 19 insertions(+) diff --git a/include/drm/drm_mm.h b/includ

Re: [PATCH] drm/i915/selftests: Use preemption timeout on cleanup

2024-12-20 Thread Andi Shyti
Hi Janusz, > > > > > > + > > > > > > cond_resched(); > > > > > > > > > > > > - if (intel_gt_wait_for_idle(gt, HZ * 3) == -ETIME) { > > > > > > + if (intel_gt_wait_for_idle(gt, HZ * timeout_ms / 500) > > > > > > == -ETIME) { > > > > > > > > > > where is this 500

Re: [PATCH v5 1/2] drm/panthor: Expose size of driver internal BO's over fdinfo

2024-12-20 Thread kernel test robot
Hi Adrián, kernel test robot noticed the following build warnings: [auto build test WARNING on 6a8d72b80807ad45229c0f5a17e3be843b15a703] url: https://github.com/intel-lab-lkp/linux/commits/Adri-n-Mart-nez-Larumbe/drm-panthor-Expose-size-of-driver-internal-BO-s-over-fdinfo/20241219-022128 bas

Re: [PATCH v3] drm/msm/a6xx: Add support for Adreno 612

2024-12-20 Thread Dmitry Baryshkov
On Fri, Dec 20, 2024 at 08:56:31PM +0100, Konrad Dybcio wrote: > On 13.12.2024 12:46 PM, Akhil P Oommen wrote: > > From: Jie Zhang > > > > Add support for Adreno 612 GPU found in SM6150/QCS615 chipsets. > > A612 falls under ADRENO_6XX_GEN1 family and is a cut down version > > of A615 GPU. > > >

Re: [PATCH v3] drm/msm/a6xx: Add support for Adreno 612

2024-12-20 Thread Konrad Dybcio
On 13.12.2024 12:46 PM, Akhil P Oommen wrote: > From: Jie Zhang > > Add support for Adreno 612 GPU found in SM6150/QCS615 chipsets. > A612 falls under ADRENO_6XX_GEN1 family and is a cut down version > of A615 GPU. > > A612 has a new IP called Reduced Graphics Management Unit or RGMU > which is

Re: [git pull] drm fixes for 6.13-rc4

2024-12-20 Thread pr-tracker-bot
The pull request you sent on Fri, 20 Dec 2024 16:33:22 +1000: > https://gitlab.freedesktop.org/drm/kernel.git tags/drm-fixes-2024-12-20 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/af215c980c1fbf1ca01675b128b0dd194745b880 Thank you! -- Deet-doot-dot, I am a bot. h

[PATCH v8 06/10] drm/display/hdmi: implement hotplug functions

2024-12-20 Thread Dmitry Baryshkov
The HDMI Connectors need to perform a variety of tasks when the HDMI connector state changes. Such tasks include setting or invalidating CEC address, notifying HDMI codec driver, updating scrambler data, etc. Implementing such tasks in a driver-specific callbacks is error prone. Start implementing

[PATCH v8 08/10] drm/vc4: hdmi: switch to using generic HDMI Codec infrastructure

2024-12-20 Thread Dmitry Baryshkov
Drop driver-specific implementation and use the generic HDMI Codec framework in order to implement the HDMI audio support. Acked-by: Maxime Ripard Tested-by: Dave Stevenson Signed-off-by: Dmitry Baryshkov --- drivers/gpu/drm/vc4/vc4_hdmi.c | 73 +++--- drive

[PATCH v8 04/10] drm/bridge: connector: add support for HDMI codec framework

2024-12-20 Thread Dmitry Baryshkov
Add necessary glue code to be able to use new HDMI codec framework from the DRM bridge drivers. The drm_bridge implements a limited set of the hdmi_codec_ops interface, with the functions accepting both drm_connector and drm_bridge instead of just a generic void pointer. This framework is integrat

[PATCH v8 05/10] drm/bridge: lt9611: switch to using the DRM HDMI codec framework

2024-12-20 Thread Dmitry Baryshkov
Make the Lontium LT9611 DSI-to-HDMI bridge driver use the DRM HDMI Codec framework. This enables programming of Audio InfoFrames using the HDMI Connector interface and also enables support for the missing features, including the ELD retrieval and better hotplug support. Reviewed-by: Maxime Ripard

[PATCH v8 10/10] drm/vc4: hdmi: use drm_atomic_helper_connector_hdmi_hotplug()

2024-12-20 Thread Dmitry Baryshkov
Use the helper function to update the connector's information. This makes sure that HDMI-related events are handled in a generic way. Currently it is limited to the HDMI state reporting to the sound system. Acked-by: Maxime Ripard Tested-by: Dave Stevenson Signed-off-by: Dmitry Baryshkov --- d

[PATCH v8 09/10] drm/vc4: hdmi: stop rereading EDID in get_modes()

2024-12-20 Thread Dmitry Baryshkov
The vc4_hdmi_connector_detect_ctx() via vc4_hdmi_handle_hotplug() already reads EDID and propagates it to the drm_connector. Stop rereading EDID as a part of the .get_modes() callback and just update the list of modes. This matches the behaviour of the i915 driver. Acked-by: Maxime Ripard Tested-

[PATCH v8 07/10] drm/bridge_connector: hook drm_atomic_helper_connector_hdmi_hotplug()

2024-12-20 Thread Dmitry Baryshkov
Extend drm_bridge_connector code to read the EDID and use it to update connector status if the bridge chain implements HDMI bridge. Performing it from the generic location minimizes individual bridge's code and enforces standard behaviour from all corresponding drivers. Reviewed-by: Maxime Ripard

[PATCH v8 02/10] ASoC: hdmi-codec: move no_capture_mute to struct hdmi_codec_pdata

2024-12-20 Thread Dmitry Baryshkov
The no_capture_mute flag might differ from platform to platform, especially in the case of the wrapping implementations, like the upcoming DRM HDMI Codec framework. Move the flag next to all other flags in struct hdmi_codec_pdata. Acked-by: Mark Brown Tested-by: Dave Stevenson Signed-off-by: Dmi

[PATCH v8 03/10] drm/connector: implement generic HDMI audio helpers

2024-12-20 Thread Dmitry Baryshkov
Several DRM drivers implement HDMI codec support (despite its name it applies to both HDMI and DisplayPort drivers). Implement generic framework to be used by these drivers. This removes a requirement to implement get_eld() callback and provides default implementation for codec's plug handling. Ac

[PATCH v8 01/10] ASoC: hdmi-codec: pass data to get_dai_id too

2024-12-20 Thread Dmitry Baryshkov
The upcoming DRM connector HDMI codec implementation is going to use codec-specific data in the .get_dai_id to get drm_connector. Pass data to the callback, as it is done with other hdmi_codec_ops callbacks. Acked-by: Mark Brown Tested-by: Dave Stevenson Signed-off-by: Dmitry Baryshkov --- dri

[PATCH v8 00/10] drm: add DRM HDMI Codec framework

2024-12-20 Thread Dmitry Baryshkov
While porting lt9611 DSI-to-HDMI bridge driver to use HDMI Connector framework, I stumbled upon an issue while handling the Audio InfoFrames. The HDMI codec callbacks weren't receiving the drm_atomic_state, so there was no simple way to get the drm_connector that stayed at the end of the bridge cha

Re: [PATCH v7 00/10] drm: add DRM HDMI Codec framework

2024-12-20 Thread Dmitry Baryshkov
On Fri, Dec 20, 2024 at 03:00:47PM +, Dave Stevenson wrote: > On Fri, 20 Dec 2024 at 00:45, Dmitry Baryshkov > wrote: > > > > On Thu, Dec 19, 2024 at 04:16:37PM +, Dave Stevenson wrote: > > > On Wed, 18 Dec 2024 at 14:52, Dave Stevenson > > > wrote: > > > > > > > > Hi Maxime & Dmitry > >

Re: [PATCH v3 05/30] drm/gpusvm: Add support for GPU Shared Virtual Memory

2024-12-20 Thread Matthew Brost
On Tue, Dec 17, 2024 at 03:33:23PM -0800, Matthew Brost wrote: > This patch introduces support for GPU Shared Virtual Memory (SVM) in the > Direct Rendering Manager (DRM) subsystem. SVM allows for seamless > sharing of memory between the CPU and GPU, enhancing performance and > flexibility in GPU c

Re: [PATCH v3 15/30] drm/xe: Add unbind to SVM garbage collector

2024-12-20 Thread Ghimiray, Himal Prasad
On 18-12-2024 05:03, Matthew Brost wrote: Add unbind to SVM garbage collector. To facilitate add unbind support function to VM layer which unbinds a SVM range. Also teach PY layer to understand unbinds of SVM ranges. v3: - s/INVALID_VMA/XE_INVALID_VMA (Thomas) - Kernel doc (Thomas) - Ne

Re: [PATCH v3 15/30] drm/xe: Add unbind to SVM garbage collector

2024-12-20 Thread Matthew Brost
On Sat, Dec 21, 2024 at 12:20:09AM +0530, Ghimiray, Himal Prasad wrote: > > > On 18-12-2024 05:03, Matthew Brost wrote: > > Add unbind to SVM garbage collector. To facilitate add unbind support > > function to VM layer which unbinds a SVM range. Also teach PY layer to > > understand unbinds of SV

Re: [PATCH v4 00/25] drm/msm/dpu: Add Concurrent Writeback Support for DPU 10.x+

2024-12-20 Thread Jessica Zhang
On 12/19/2024 9:11 PM, Dmitry Baryshkov wrote: On Mon, Dec 16, 2024 at 04:43:11PM -0800, Jessica Zhang wrote: DPU supports a single writeback session running concurrently with primary display when the CWB mux is configured properly. This series enables clone mode for DPU driver and adds suppo

Re: [PATCH v3 19/30] drm/xe: Add SVM device memory mirroring

2024-12-20 Thread Matthew Brost
On Sat, Dec 21, 2024 at 12:09:55AM +0530, Ghimiray, Himal Prasad wrote: > > > On 18-12-2024 05:03, Matthew Brost wrote: > > Add SVM device memory mirroring which enables device pages for > > migration. Enabled via CONFIG_XE_DEVMEM_MIRROR Kconfig. Kconfig option > > defaults to enabled. If not ena

Re: [PATCH v3 19/30] drm/xe: Add SVM device memory mirroring

2024-12-20 Thread Ghimiray, Himal Prasad
On 18-12-2024 05:03, Matthew Brost wrote: Add SVM device memory mirroring which enables device pages for migration. Enabled via CONFIG_XE_DEVMEM_MIRROR Kconfig. Kconfig option defaults to enabled. If not enabled, SVM will work sans migration and KMD memory footprint will be less. v3: - Add

Re: [PATCH v4] drm/etnaviv: add optional reset support

2024-12-20 Thread Lucas Stach
Am Dienstag, dem 17.12.2024 um 11:36 + schrieb LECOINTRE Philippe: > Add optional reset support which is mentioned in vivante,gc.yaml to > allow the driver to work on SoCs whose reset signal is asserted by default > Thanks, applied to etnaviv/next. Regards, Lucas > Signed-off-by: Philippe Le

[PATCH v5 1/3] dt-bindings: display: bcm2711-hdmi: Add interrupt details for BCM2712

2024-12-20 Thread Dave Stevenson
Commit 62948c62abca ("dt-bindings: display: Add BCM2712 HDMI bindings") added the compatible strings for BCM2712, but missed out that the number of interrupts changed, and for BCM2712 the driver changes[1] required that the interrupts are named. Update the schema to correct the interrupt requireme

[PATCH v5 2/3] dt-bindings: display: Fix brcm,bcm2835-hvs bindings for BCM2712

2024-12-20 Thread Dave Stevenson
Commit 6cfcbe548a3a ("dt-bindings: display: Add BCM2712 HVS bindings") added the compatible string for BCM2712, but missed out that the number of interrupts and clocks changed too. The driver commit adding support for BCM2712 [1] also requires that both interrupts and clocks are named, so the rele

[PATCH v5 3/3] dt-bindings: interrupt-controller: brcm,bcm2836-l1-intc: Drop interrupt-controller requirement

2024-12-20 Thread Dave Stevenson
Since commit 88bbe85dcd37 ("irqchip: bcm2836: Move SMP startup code to arch/arm (v2)") the bcm2836-l1-intc block on bcm2711 is only used as a base address for the smp_boot_secondary hook on 32 bit kernels. It is not used as an interrupt controller. Drop the binding requirement for interrupt-contro

[PATCH v5 0/3] drm/vc4: Fixup DT and DT binding issues from recent patchset

2024-12-20 Thread Dave Stevenson
I missed the DT errors from the recent patchset[1] (DT patches in linux-next via Florian, DRM bindings patches on dri-misc-next) as Rob's bot report got spam filtered, so this is a fixup set. Largely it was changes to number of interrupts or clocks in the bindings, so those are now covered. I've

Re: [PATCH 6/7] accel/qaic: Add config structs for supported cards

2024-12-20 Thread Lizhi Hou
On 12/20/24 09:15, Jeffrey Hugo wrote: On 12/13/2024 5:35 PM, Lizhi Hou wrote: On 12/13/24 13:33, Jeffrey Hugo wrote: -static struct qaic_device *create_qdev(struct pci_dev *pdev, const struct pci_device_id *id) +static struct qaic_device *create_qdev(struct pci_dev *pdev, +

Re: [PATCH 7/7] accel/qaic: Add AIC200 support

2024-12-20 Thread Lizhi Hou
On 12/20/24 09:50, Jeffrey Hugo wrote: On 12/20/2024 10:33 AM, Lizhi Hou wrote: On 12/20/24 09:26, Jeffrey Hugo wrote: On 12/13/2024 5:49 PM, Lizhi Hou wrote: On 12/13/24 13:33, Jeffrey Hugo wrote: +static const struct qaic_device_config aic200_config = { +    .family = FAMILY_AIC200, +  

Re: [PATCH 2/2] drm/i915/lttpr: Enable Extended Wake Timeout

2024-12-20 Thread kernel test robot
Hi Suraj, kernel test robot noticed the following build errors: [auto build test ERROR on linus/master] [also build test ERROR on drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-tip/drm-tip v6.13-rc3 next-20241220] [If your patch is applied to the wrong git tree, kindly drop us a

Re: [PATCH 7/7] accel/qaic: Add AIC200 support

2024-12-20 Thread Jeffrey Hugo
On 12/20/2024 10:33 AM, Lizhi Hou wrote: On 12/20/24 09:26, Jeffrey Hugo wrote: On 12/13/2024 5:49 PM, Lizhi Hou wrote: On 12/13/24 13:33, Jeffrey Hugo wrote: +static const struct qaic_device_config aic200_config = { +    .family = FAMILY_AIC200, +    .bar_mask = BIT(0) | BIT(1) | BIT(2) | B

Re: [PATCH 7/7] accel/qaic: Add AIC200 support

2024-12-20 Thread Lizhi Hou
On 12/20/24 09:26, Jeffrey Hugo wrote: On 12/13/2024 5:49 PM, Lizhi Hou wrote: On 12/13/24 13:33, Jeffrey Hugo wrote: @@ -573,6 +898,13 @@ struct mhi_controller *qaic_mhi_register_controller(struct pci_dev *pci_dev, voi   mhi_cntrl->nr_irqs = 1;   mhi_cntrl->irq = devm_kmalloc(&pci_

Re: (subset) [PATCH 00/35] Reorganize kerneldoc parameter names

2024-12-20 Thread Srinivas Kandagatla
On Mon, 30 Sep 2024 13:20:46 +0200, Julia Lawall wrote: > Reorganize kerneldoc parameter names to match the parameter > order in the function header. > > The misordered cases were identified using the following > Coccinelle semantic patch: > > // > @initialize:ocaml@ > @@ > > [...] Applied,

Re: [PATCH 7/7] accel/qaic: Add AIC200 support

2024-12-20 Thread Jeffrey Hugo
On 12/13/2024 5:49 PM, Lizhi Hou wrote: On 12/13/24 13:33, Jeffrey Hugo wrote: @@ -573,6 +898,13 @@ struct mhi_controller *qaic_mhi_register_controller(struct pci_dev *pci_dev, voi   mhi_cntrl->nr_irqs = 1;   mhi_cntrl->irq = devm_kmalloc(&pci_dev->dev, sizeof(*mhi_cntrl->irq), GFP_KE

Re: [PATCH 6/7] accel/qaic: Add config structs for supported cards

2024-12-20 Thread Jeffrey Hugo
On 12/13/2024 5:35 PM, Lizhi Hou wrote: On 12/13/24 13:33, Jeffrey Hugo wrote: -static struct qaic_device *create_qdev(struct pci_dev *pdev, const struct pci_device_id *id) +static struct qaic_device *create_qdev(struct pci_dev *pdev, +   const struct qaic_device_config *co

[PATCH AUTOSEL 5.15 2/9] drm/amdkfd: Correct the migration DMA map direction

2024-12-20 Thread Sasha Levin
From: Prike Liang [ Upstream commit 5c3de6b02d38eb9386edf50490e050bb44398e40 ] The SVM DMA device map direction should be set the same as the DMA unmap setting, otherwise the DMA core will report the following warning. Before finialize this solution, there're some discussion on the DMA mapping

[PATCH AUTOSEL 6.1 02/12] drm/amdkfd: Correct the migration DMA map direction

2024-12-20 Thread Sasha Levin
From: Prike Liang [ Upstream commit 5c3de6b02d38eb9386edf50490e050bb44398e40 ] The SVM DMA device map direction should be set the same as the DMA unmap setting, otherwise the DMA core will report the following warning. Before finialize this solution, there're some discussion on the DMA mapping

[PATCH AUTOSEL 6.6 03/16] drm/amdkfd: Correct the migration DMA map direction

2024-12-20 Thread Sasha Levin
From: Prike Liang [ Upstream commit 5c3de6b02d38eb9386edf50490e050bb44398e40 ] The SVM DMA device map direction should be set the same as the DMA unmap setting, otherwise the DMA core will report the following warning. Before finialize this solution, there're some discussion on the DMA mapping

[PATCH AUTOSEL 6.12 06/29] drm/amdkfd: Correct the migration DMA map direction

2024-12-20 Thread Sasha Levin
From: Prike Liang [ Upstream commit 5c3de6b02d38eb9386edf50490e050bb44398e40 ] The SVM DMA device map direction should be set the same as the DMA unmap setting, otherwise the DMA core will report the following warning. Before finialize this solution, there're some discussion on the DMA mapping

[PATCH AUTOSEL 6.12 05/29] drm/amdgpu: use sjt mec fw on gfx943 for sriov

2024-12-20 Thread Sasha Levin
From: Victor Zhao [ Upstream commit 9a4ab400f1fad0e6e8686b8f5fc5376383860ce8 ] Use second jump table in sriov for live migration or mulitple VF support so different VF can load different version of MEC as long as they support sjt Signed-off-by: Victor Zhao Reviewed-by: Yang Wang Signed-off-by

Re: hda: how to implement component master_unbind?

2024-12-20 Thread Lucas De Marchi
On Thu, Dec 19, 2024 at 04:00:08PM +0200, Kai Vehmanen wrote: Hi, On Fri, 13 Dec 2024, Lucas De Marchi wrote: Thanks Kai to pointing me to this thread, trying to revive it. Also adding dri-devel as it may be relevant there and Maarten who worked on the xe integration recently ack, given fres

Re: [RFC PATCH 3/3] drm/virtio: implement blob userptr resource object

2024-12-20 Thread Simona Vetter
On Fri, Dec 20, 2024 at 06:04:09PM +0800, Honglei Huang wrote: > From: Honglei Huang > > A virtio-gpu userptr is based on HMM notifier. > Used for let host access guest userspace memory and > notice the change of userspace memory. > This series patches are in very beginning state, > User space ar

Re: [PATCH] MAINTAINERS: Assume maintainership of PL111

2024-12-20 Thread Simona Vetter
On Thu, Dec 19, 2024 at 07:36:05PM +0100, Linus Walleij wrote: > Emma Anholt dropped maintainership for PL111 and I > didn't notice it at the time. I've written part of it > and I'm happy to maintain it, list myself as maintainer > and assume active maintainership. > > Signed-off-by: Linus Walleij

Re: [PATCH] drm/fourcc: add LINEAR modifiers with an exact pitch alignment

2024-12-20 Thread Simona Vetter
On Fri, Dec 20, 2024 at 09:24:59AM -0500, Marek Olšák wrote: > > > > * Modifiers must uniquely encode buffer layout. In other words, a buffer > > must > > * match only a single modifier. > > > > That sentence is misleading and impossible to meet. Specifications are > sometimes changed to reflect

Re: [PATCH] drm/sched: Document run_job() refcount hazard

2024-12-20 Thread Christian König
Am 20.12.24 um 15:51 schrieb Danilo Krummrich: On Fri, Dec 20, 2024 at 03:11:34PM +0100, Philipp Stanner wrote: On Fri, 2024-12-20 at 14:25 +0100, Christian König wrote: Am 20.12.24 um 14:18 schrieb Danilo Krummrich: On Fri, Dec 20, 2024 at 01:53:34PM +0100, Christian König wrote: Am 20.12.24

Re: [PATCH] drm/fourcc: add LINEAR modifiers with an exact pitch alignment

2024-12-20 Thread Simona Vetter
On Thu, Dec 19, 2024 at 05:09:33PM +0100, Michel Dänzer wrote: > On 2024-12-19 10:02, Daniel Stone wrote: > > > > How this would be used in practice is also way too underdocumented. We > > need to document that exact-round-up 64b is more restrictive than > > any-multiple-of 64b is more restrictive

Re: [PATCH] drm/panel-edp: Add support for 2 panels

2024-12-20 Thread Doug Anderson
Hi, On Fri, Dec 20, 2024 at 4:21 AM Langyan Ye wrote: > > Add support for the following 2 panels: > 1. B140UAN04.4 > 2. CXOT T9 Can you please include the panel names in the subject line instead of just "add 2 panels"? Otherwise all the changes to this file look like the same subject. AKA, like:

Re: [PATCH v7 00/10] drm: add DRM HDMI Codec framework

2024-12-20 Thread Dave Stevenson
On Fri, 20 Dec 2024 at 00:45, Dmitry Baryshkov wrote: > > On Thu, Dec 19, 2024 at 04:16:37PM +, Dave Stevenson wrote: > > On Wed, 18 Dec 2024 at 14:52, Dave Stevenson > > wrote: > > > > > > Hi Maxime & Dmitry > > > > > > On Wed, 18 Dec 2024 at 07:59, Maxime Ripard wrote: > > > > > > > > On W

Re: [PATCH] drm/sched: Document run_job() refcount hazard

2024-12-20 Thread Danilo Krummrich
On Fri, Dec 20, 2024 at 03:11:34PM +0100, Philipp Stanner wrote: > On Fri, 2024-12-20 at 14:25 +0100, Christian König wrote: > > Am 20.12.24 um 14:18 schrieb Danilo Krummrich: > > > On Fri, Dec 20, 2024 at 01:53:34PM +0100, Christian König wrote: > > > > Am 20.12.24 um 13:45 schrieb Philipp Stanner

Re: [PULL] drm-intel-next

2024-12-20 Thread Rodrigo Vivi
On Wed, Dec 11, 2024 at 03:38:46PM -0500, Rodrigo Vivi wrote: > Hi Dave and Sima, > > Here goes our first drm-intel-next round targeting 6.14. > > One drm/print change coming from here. The rest is mostly > display changes and one GSC FW update for ARL platforms. > > Thanks, > Rodrigo. > > drm-

Re: [PATCH v4 5/6] optee: FF-A: dynamic restricted memory allocation

2024-12-20 Thread kernel test robot
: fac04efc5c793dccbd07e2d59af9f90b7fc0dca4 patch link: https://lore.kernel.org/r/20241217100809.3962439-6-jens.wiklander%40linaro.org patch subject: [PATCH v4 5/6] optee: FF-A: dynamic restricted memory allocation config: arm64-randconfig-002-20241220 (https://download.01.org/0day-ci/archive/20241220/202412202214.odgzpoke

Re: [PATCH] drm/fourcc: add LINEAR modifiers with an exact pitch alignment

2024-12-20 Thread Marek Olšák
> > * Modifiers must uniquely encode buffer layout. In other words, a buffer > must > * match only a single modifier. > That sentence is misleading and impossible to meet. Specifications are sometimes changed to reflect the overwhelming reality. Multiple modifiers can represent identical layouts

Re: [PATCH v2 4/7] drm/xe: Implement cgroup for vram

2024-12-20 Thread Rodrigo Vivi
On Thu, Dec 19, 2024 at 01:03:48PM +0100, Maxime Ripard wrote: > Hi Lucas, Thomas, Rodrigo, > > We forgot to Cc you on this series, sorry. Could you have a look at it, > and especially the following patch? I'm sorry for the delay here. I was following the thread on the side. I'm glad to see that

Re: [PATCH] drm/sched: Document run_job() refcount hazard

2024-12-20 Thread Philipp Stanner
On Fri, 2024-12-20 at 14:25 +0100, Christian König wrote: > Am 20.12.24 um 14:18 schrieb Danilo Krummrich: > > On Fri, Dec 20, 2024 at 01:53:34PM +0100, Christian König wrote: > > > Am 20.12.24 um 13:45 schrieb Philipp Stanner: > > > > From: Philipp Stanner > > > > > > > > drm_sched_backend_ops.r

Re: [PATCH 1/1] drm/amdgpu: Use device wedged event

2024-12-20 Thread kernel test robot
Hi André, kernel test robot noticed the following build errors: [auto build test ERROR on linus/master] [also build test ERROR on drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-tip/drm-tip v6.13-rc3 next-20241220] [If your patch is applied to the wrong git tree, kindly drop us a

Re: [PATCH] drm/i915/selftests: Use preemption timeout on cleanup

2024-12-20 Thread Andi Shyti
Hi Janusz, > > > > > + > > > > > cond_resched(); > > > > > > > > > > - if (intel_gt_wait_for_idle(gt, HZ * 3) == -ETIME) { > > > > > + if (intel_gt_wait_for_idle(gt, HZ * timeout_ms / 500) > > > > > == - > > > ETIME) { > > > > > > > > where is this 500 com

[PATCH v3 3/3] drm/vc4: Remove BOs seqnos

2024-12-20 Thread Maíra Canal
`bo->seqno`, `bo->write_seqno`, and `exec->bin_dep_seqno` are leftovers from a time when VC4 didn't support DMA Reservation Objects. Before DMA Resv was introduced, tracking the correspondence between BOs and jobs through the job's seqno made sense. However, this is no longer needed, as VC4 now su

[PATCH v3 2/3] drm/vc4: Use DMA Resv to implement VC4 wait BO IOCTL

2024-12-20 Thread Maíra Canal
Since the BOs used by VC4 have DMA Reservation Objects attached to them, waiting for seqnos to check BO availability is unnecessary. Instead, `drm_gem_dma_resv_wait()` can be used. Signed-off-by: Maíra Canal --- drivers/gpu/drm/vc4/vc4_gem.c | 25 ++--- 1 file changed, 14 ins

[PATCH v3 1/3] drm/vc4: Use DRM Execution Contexts

2024-12-20 Thread Maíra Canal
VC4 has internal copies of `drm_gem_lock_reservations()` and `drm_gem_unlock_reservations()` within the driver. Ideally, these hard-coded functions should be replaced with the generic functions provided by DRM common code. However, instead of using the DRM GEM functions to (un)lock reservations, tr

[PATCH v3 0/3] drm/vc4: Clean-up BO seqnos

2024-12-20 Thread Maíra Canal
This series introduces a series of clean-ups for BO reservations in the VC4 driver. Currently, VC4 uses shared fences to track BO reservations, similar to many other DRM devices. However, in addition to DMA reservation objects, VC4 has been maintaining a separate seqno tracking system for BOs to tr

Re: [PATCH v3 3/7] dt-bindings: gpio: brcmstb: permit gpio-line-names property

2024-12-20 Thread Bartosz Golaszewski
On Fri, Dec 20, 2024 at 2:02 PM Dave Stevenson wrote: > > Hi Linus > > On Fri, 20 Dec 2024 at 12:50, Linus Walleij wrote: > > > > On Thu, Dec 12, 2024 at 7:36 PM Dave Stevenson > > wrote: > > > > > gpio-line-names is a generic property that can be supported by any > > > GPIO controller, so permi

Re: [PATCH 1/1] drm/amdgpu: Use device wedged event

2024-12-20 Thread kernel test robot
Hi André, kernel test robot noticed the following build errors: [auto build test ERROR on linus/master] [also build test ERROR on v6.13-rc3 next-20241220] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as

Re: [PATCH] drm/sched: Document run_job() refcount hazard

2024-12-20 Thread Christian König
Am 20.12.24 um 14:18 schrieb Danilo Krummrich: On Fri, Dec 20, 2024 at 01:53:34PM +0100, Christian König wrote: Am 20.12.24 um 13:45 schrieb Philipp Stanner: From: Philipp Stanner drm_sched_backend_ops.run_job() returns a dma_fence for the scheduler. That fence is signalled by the driver once

Re: [PATCH] drm/sched: Document run_job() refcount hazard

2024-12-20 Thread Danilo Krummrich
On Fri, Dec 20, 2024 at 01:53:34PM +0100, Christian König wrote: > Am 20.12.24 um 13:45 schrieb Philipp Stanner: > > From: Philipp Stanner > > > > drm_sched_backend_ops.run_job() returns a dma_fence for the scheduler. > > That fence is signalled by the driver once the hardware completed the > > a

Re: [PATCH] drm/sched: Document run_job() refcount hazard

2024-12-20 Thread Danilo Krummrich
On Fri, Dec 20, 2024 at 01:45:15PM +0100, Philipp Stanner wrote: > From: Philipp Stanner > > drm_sched_backend_ops.run_job() returns a dma_fence for the scheduler. > That fence is signalled by the driver once the hardware completed the > associated job. The scheduler does not increment the refere

Re: [PATCH v3 3/7] dt-bindings: gpio: brcmstb: permit gpio-line-names property

2024-12-20 Thread Dave Stevenson
Hi Linus On Fri, 20 Dec 2024 at 12:50, Linus Walleij wrote: > > On Thu, Dec 12, 2024 at 7:36 PM Dave Stevenson > wrote: > > > gpio-line-names is a generic property that can be supported by any > > GPIO controller, so permit it through the binding. > > > > It is permitted to have a variable numbe

Re: [PATCH 13/26] RFC drm/xe/eudebug: userptr vm pread/pwrite

2024-12-20 Thread Christian König
Am 20.12.24 um 12:31 schrieb Mika Kuoppala: Implement debugger vm access for userptrs. When bind is done, take ref to current task so that we know from which vm the address was bound. Then during debugger pread/pwrite we use this target task as parameter to access the debuggee vm with access_pro

Re: [PATCH 2/2] drm/buddy: Add a testcase to verify the multiroot fini

2024-12-20 Thread Paneer Selvam, Arunpravin
Hi Matthew, On 12/16/2024 11:52 PM, Matthew Auld wrote: On 16/12/2024 13:07, Arunpravin Paneer Selvam wrote: - Added a testcase to verify the multiroot force merge fini. - Added a new field in_use to track the mm freed status. Signed-off-by: Arunpravin Paneer Selvam Signed-off-by: Lin.Cao

Re: [PATCH] drm/sched: Document run_job() refcount hazard

2024-12-20 Thread Christian König
Am 20.12.24 um 13:45 schrieb Philipp Stanner: From: Philipp Stanner drm_sched_backend_ops.run_job() returns a dma_fence for the scheduler. That fence is signalled by the driver once the hardware completed the associated job. The scheduler does not increment the reference count on that fence, bu

Re: [PATCH v3 3/7] dt-bindings: gpio: brcmstb: permit gpio-line-names property

2024-12-20 Thread Linus Walleij
On Thu, Dec 12, 2024 at 7:36 PM Dave Stevenson wrote: > gpio-line-names is a generic property that can be supported by any > GPIO controller, so permit it through the binding. > > It is permitted to have a variable number of GPIOs per node based > on brcm,gpio-bank-widths, so define an arbitrary

Re: [PATCH 14/26] drm/xe/eudebug: implement userptr_vma access

2024-12-20 Thread Mika Kuoppala
Joonas Lahtinen writes: > Quoting Joonas Lahtinen (2024-12-11 14:59:33) >> Quoting Christian König (2024-12-10 16:03:14) > > > >> > If you really want to expose an interface to userspace which walks the >> > process >> > page table, installs an MMU notifier, kmaps the resulting page and then >

[PATCH] drm/sched: Document run_job() refcount hazard

2024-12-20 Thread Philipp Stanner
From: Philipp Stanner drm_sched_backend_ops.run_job() returns a dma_fence for the scheduler. That fence is signalled by the driver once the hardware completed the associated job. The scheduler does not increment the reference count on that fence, but implicitly expects to inherit this fence from

Re: [PATCH 00/38] rockchip: Add rk3562 support

2024-12-20 Thread Greg Kroah-Hartman
On Fri, Dec 20, 2024 at 06:37:46PM +0800, Kever Yang wrote: > > This patch set adds rk3562 SoC and its evb support. > > The patch number is a little bit too big, some of them may need to split > out for different maintainers, please let me know which patch need to > split out. I recommend you do

Re: [PATCH] drm/i915/selftests: Use preemption timeout on cleanup

2024-12-20 Thread Janusz Krzysztofik
Hi Andi, On Tuesday, 17 December 2024 19:00:40 CET Janusz Krzysztofik wrote: > Hi Andi, > > On Tuesday, 17 December 2024 18:12:08 CET Andi Shyti wrote: > > Hi Janusz, > > > > ... > > > > > > > + > > > > > cond_resched(); > > > > > > > > > > - if (intel_gt_wait_for_id

Re: [PATCH] drm/fourcc: add LINEAR modifiers with an exact pitch alignment

2024-12-20 Thread Brian Starkey
This is getting long, so tl;dr: - Pitch alignment *by itself* is manageable. - Adding constraints in modifiers quickly leads to combinatorial explosion. - drm_fourcc.h explicitly says "it's incorrect to encode pitch alignment in a modifier", for all the reasons Daniel raised. That need

[PATCH 13/26] RFC drm/xe/eudebug: userptr vm pread/pwrite

2024-12-20 Thread Mika Kuoppala
Implement debugger vm access for userptrs. When bind is done, take ref to current task so that we know from which vm the address was bound. Then during debugger pread/pwrite we use this target task as parameter to access the debuggee vm with access_process_vm(). This is based on suggestions from

Re: [PATCH v5 1/2] drm/panthor: Expose size of driver internal BO's over fdinfo

2024-12-20 Thread Mihail Atanassov
On 20/12/2024 11:08, Steven Price wrote: On 19/12/2024 16:30, Mihail Atanassov wrote: On 18/12/2024 18:18, Adrián Martínez Larumbe wrote: From: Adrián Larumbe This will display the sizes of kenrel BO's bound to an open file, which are otherwise not exposed to UM through a handle. The si

Re: [PATCH v5 2/2] Documentation/gpu: Add fdinfo meanings of drm-*-internal memory tags

2024-12-20 Thread Steven Price
On 18/12/2024 18:18, Adrián Martínez Larumbe wrote: > From: Adrián Larumbe > > A previous commit enabled display of driver-internal kernel BO sizes > through the device file's fdinfo interface. > > Expand the description of the relevant driver-specific key:value pairs > with the definitions of t

Re: [PATCH v5 1/2] drm/panthor: Expose size of driver internal BO's over fdinfo

2024-12-20 Thread Steven Price
On 18/12/2024 19:14, Adrián Larumbe wrote: > On 19.12.2024 02:18, Adrián Martínez Larumbe wrote: >> From: Adrián Larumbe >> >> This will display the sizes of kenrel BO's bound to an open file, which are >> otherwise not exposed to UM through a handle. >> >> The sizes recorded are as follows: >> -

Re: [PATCH v5 1/2] drm/panthor: Expose size of driver internal BO's over fdinfo

2024-12-20 Thread Steven Price
On 19/12/2024 16:30, Mihail Atanassov wrote: > > > On 18/12/2024 18:18, Adrián Martínez Larumbe wrote: >> From: Adrián Larumbe >> >> This will display the sizes of kenrel BO's bound to an open file, >> which are >> otherwise not exposed to UM through a handle. >> >> The sizes recorded are as fol

Re: [PATCH v2] drm/bridge: synopsys: Fix Copyright Writing Style of dw-hdmi-qp

2024-12-20 Thread Neil Armstrong
Hi, On Mon, 16 Dec 2024 18:10:03 +0800, Andy Yan wrote: > The standard writing style should be: Co., Ltd. > This fix the mail server warning: > DBL_SPAM(6.50)[co.ltd:url]; > > Thanks, Applied to https://gitlab.freedesktop.org/drm/misc/kernel.git (drm-misc-next) [1/1] drm/bridge: synopsys: Fix

Re: [PATCH 0/3] drm: panel-simple: support TOPLAND TIAN G07017 LCD panel

2024-12-20 Thread Neil Armstrong
Hi, On Wed, 18 Dec 2024 20:44:57 +0100, Ahmad Fatoum wrote: > The TIAN-G07017-01 is a 7" TFT-LCD module by TOPLAND ELECTRONICS (H.K). > The panel features 1024x600 24-bit RGB pixels driven over LVDS as well > as a PWM backlight and I2C-connected ft5506-compatible capacitive touch. > > This serie

Re: [PATCH v4] drm/bridge:anx7625: Update HDCP content status

2024-12-20 Thread Neil Armstrong
Hi, On Thu, 19 Dec 2024 15:03:29 +0800, Xin Ji wrote: > When user enabled HDCP feature, userspace will set HDCP content > to DRM_MODE_CONTENT_PROTECTION_DESIRED. Next, anx7625 will update > HDCP content to DRM_MODE_CONTENT_PROTECTION_ENABLED if down stream > support HDCP feature. > > As anx7625 b

[PATCH 00/38] rockchip: Add rk3562 support

2024-12-20 Thread Kever Yang
This patch set adds rk3562 SoC and its evb support. The patch number is a little bit too big, some of them may need to split out for different maintainers, please let me know which patch need to split out. Test with GMAC, USB, PCIe, EMMC, SD Card. This patch set is base on the patche set for r

[RFC PATCH 3/3] drm/virtio: implement blob userptr resource object

2024-12-20 Thread Honglei Huang
From: Honglei Huang A virtio-gpu userptr is based on HMM notifier. Used for let host access guest userspace memory and notice the change of userspace memory. This series patches are in very beginning state, User space are pinned currently to ensure the host device memory operations are correct. T

[RFC PATCH 2/3] drm/virtgpu api: add blob userptr resource

2024-12-20 Thread Honglei Huang
From: Honglei Huang This makes blob userptr resource available to guest userspace. - Flag VIRTGPU_BLOB_FLAG_USE_USERPTR for guest userspace blob create, enable this flag to indicate blob userptr resource create. - New parameter blob_userptr for bypass userspace memory address to virtio GPU, like

[RFC PATCH 1/3] virtio-gpu api: add blob userptr resource

2024-12-20 Thread Honglei Huang
From: Honglei Huang Add a new resource for blob resource, called userptr, used for let host access guest user space memory, to acquire a simple SVM features in virtio GPU. - The capset VIRTIO_GPU_CAPSET_HSAKMT used for context init, in this series patches only HSAKMT context can use the userptr

Re: [PATCH] drm/sched: Separate drm_sched_fini() driver checklist

2024-12-20 Thread Philipp Stanner
On Tue, 2024-12-17 at 10:49 +0700, Bagas Sanjaya wrote: > Commit baf4afc5831438 ("drm/sched: Improve teardown documentation") > documents drm_sched_fini() with a post-function call checklist for > drivers. The checklist triggers htmldocs warning (but renders > correctly > in htmldocs output): > >

Re: [PATCH v3 25/33] drm/mediatek: mtk_hdmi: Remove goto in mtk_hdmi_clk_enable_audio()

2024-12-20 Thread 胡俊光

Re: [PATCH v3 23/33] drm/mediatek: mtk_hdmi: Use devm managed version of drm_bridge_add

2024-12-20 Thread 胡俊光

RE: [PATCH] drm: xlnx: zynqmp_dpsub: Fix kernel doc

2024-12-20 Thread Sagar, Vishal
power of 2) > + * @audio: DP audio data > */ > struct zynqmp_dpsub { > struct device *dev; > > --- > base-commit: 74ef9527bd87ead62deabe749a6d867af748d448 > change-id: 20241220-xilinx-dp-audio-doc-fix-0651029616e7 > > Best regards, > -- > Tomi Valkeinen

Re: [PATCH v3 08/15] drm/rockchip: analogix_dp: Add support to get panel from the DP AUX bus

2024-12-20 Thread Damon Ding
Hi Dmitry, On 2024/12/20 8:16, Dmitry Baryshkov wrote: On Thu, Dec 19, 2024 at 04:05:57PM +0800, Damon Ding wrote: The rockchip_dp_of_panel_on_aux_bus() helps to check whether the DT configurations related to the DP AUX bus are correct or not. If failed to get the panel from the platform bus,

  1   2   >