Re: [PATCH v3 09/11] drm/mediatek: Add secure flow support to mediatek-drm

2023-12-25 Thread 胡俊光

Re: [PATCH v3 06/11] drm/mediatek: Add get_sec_port interface to mtk_ddp_comp

2023-12-25 Thread 胡俊光

Re: [PATCH v3 07/11] drm/mediatek: Add secure layer config support for ovl

2023-12-25 Thread 胡俊光

Re: [PATCH v3 08/11] drm/mediatek: Add secure layer config support for ovl_adaptor

2023-12-25 Thread 胡俊光

[PATCH AUTOSEL 6.1 20/24] drm/amd/display: get dprefclk ss info from integration info table

2023-12-25 Thread Sasha Levin
From: Charlene Liu [ Upstream commit 51e7b64690776a9981355428b537af9048308a95 ] [why & how] we have two SSC_En: we get ssc_info from dce_info for MPLL_SSC_EN. we used to call VBIOS cmdtbl's smu_info's SS persentage for DPRECLK SS info, is used for DP AUDIO and VBIOS' smu_info table was from

[PATCH AUTOSEL 6.6 33/39] drm/amd/display: Add case for dcn35 to support usb4 dmub hpd event

2023-12-25 Thread Sasha Levin
From: Wayne Lin [ Upstream commit 989824589f793120833bef13aa4e21f5a836a707 ] [Why & how] Refactor dc_is_dmub_outbox_supported() a bit and add case for dcn35 to register dmub outbox notification irq to handle usb4 relevant hpd event. Reviewed-by: Roman Li Reviewed-by: Jun Lei Signed-off-by:

[PATCH AUTOSEL 6.6 34/39] drm/amd/display: get dprefclk ss info from integration info table

2023-12-25 Thread Sasha Levin
From: Charlene Liu [ Upstream commit 51e7b64690776a9981355428b537af9048308a95 ] [why & how] we have two SSC_En: we get ssc_info from dce_info for MPLL_SSC_EN. we used to call VBIOS cmdtbl's smu_info's SS persentage for DPRECLK SS info, is used for DP AUDIO and VBIOS' smu_info table was from

[PATCH AUTOSEL 6.6 32/39] drm/amdkfd: svm range always mapped flag not working on APU

2023-12-25 Thread Sasha Levin
From: Philip Yang [ Upstream commit ebab8c3eb6a6515dc14cd93fc29dd287709da6d3 ] On gfx943 APU there is no VRAM and page migration, queue CWSR area, svm range with always mapped flag, is not mapped to GPU correctly. This works fine if retry fault on CWSR area can be recovered, but could cause

Re: [PATCH] drm/vmwgfx: Unmap the surface before resetting it on a plane state

2023-12-25 Thread Stefan Hoffmeister
Quoting Zack Rusin : Switch to a new plane state requires unreferencing of all held surfaces. In the work required for mob cursors the mapped surfaces started being cached but the variable indicating whether the surface is currently mapped was not being reset. This leads to crashes as the

[PATCH linux-next v2] drm/panel: Simplify with dev_err_probe()

2023-12-25 Thread chenguanxi11234
From: Chen Haonan dev_err_probe() can check if the error code is -EPROBE_DEFER and can return the error code, replacing dev_err() with it simplifies the code. Signed-off-by: Chen Haonan --- drivers/gpu/drm/panel/panel-boe-himax8279d.c | 18 ++ 1 file changed, 6

Re: [PATCH -next] drm/nouveau: uapi: fix kerneldoc warnings

2023-12-25 Thread Randy Dunlap
On 12/25/23 00:30, Vegard Nossum wrote: > > On 25/12/2023 08:40, Randy Dunlap wrote: >> I do see one thing that I don't like in the generated html output. >> It's not a problem with this patch. >> The #defines for DRM_NOUVEAU_VM_BIND_OP_MAP etc. have a ';' at the >> end of each line: >> >>

[PATCH v3 3/5] drm/msm/dpu: drop dpu_encoder_phys_ops.atomic_mode_set

2023-12-25 Thread Dmitry Baryshkov
The atomic_mode_set() callback only sets the phys_enc's IRQ data. As the INTF and WB are statically allocated to each encoder/phys_enc, drop the atomic_mode_set callback and set the IRQs during encoder init. For the CMD panel usecase some of IRQ indexes depend on the selected resources. Move

[PATCH v3 5/5] drm/msm/dpu: drop dpu_encoder_phys_ops::atomic_check()

2023-12-25 Thread Dmitry Baryshkov
Writeback was the last user of dpu_encoder_phys_ops's atomic_check() callback. As the code was moved to the dpu_writeback.c, the callback becomes unused. Drop it now. Signed-off-by: Dmitry Baryshkov --- drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 15 ---

[PATCH v3 2/5] drm/msm/dpu: split _dpu_encoder_resource_control_helper()

2023-12-25 Thread Dmitry Baryshkov
Follow the _dpu_encoder_irq_control() change and split the _dpu_encoder_resource_control_helper() into enable and disable parts. Signed-off-by: Dmitry Baryshkov --- drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 45 + drivers/gpu/drm/msm/disp/dpu1/dpu_trace.h | 12 -- 2

[PATCH v3 4/5] drm/msm/dpu: move writeback's atomic_check to dpu_writeback.c

2023-12-25 Thread Dmitry Baryshkov
dpu_encoder_phys_wb is the only user of encoder's atomic_check callback. Move corresponding checks to drm_writeback_connector's implementation and drop the dpu_encoder_phys_wb_atomic_check() function. Signed-off-by: Dmitry Baryshkov --- .../drm/msm/disp/dpu1/dpu_encoder_phys_wb.c | 54

[PATCH v3 1/5] drm/msm/dpu: split irq_control into irq_enable and _disable

2023-12-25 Thread Dmitry Baryshkov
The single helper for both enable and disable cases is too complicated, especially if we start adding more code to these helpers. Split it into irq_enable and irq_disable cases. Signed-off-by: Dmitry Baryshkov --- drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 36 +++---

[PATCH v3 0/5] drm/msm/dpu: remove dpu_encoder_phys_ops::atomic_mode_set callback

2023-12-25 Thread Dmitry Baryshkov
The dpu_encoder_phys_ops::atomic_mode_set() callback is mostly redundant. Implementations only set the IRQ indices there. Move statically allocated IRQs to dpu_encoder_phys_*_init() and set dynamically allocated IRQs in the irq_enable() callback. The writeback backend of the dpu_encoder is the

Re: [PATCH] drm/bridge: parade-ps8640: Wait for HPD when doing an AUX transfer

2023-12-25 Thread Pin-yen Lin
Hi, On Fri, Dec 22, 2023 at 11:34 PM Doug Anderson wrote: > > Hi, > > On Fri, Dec 22, 2023 at 2:29 AM Pin-yen Lin wrote: > > > > Hi Douglas, > > > > On Fri, Dec 22, 2023 at 5:56 AM Douglas Anderson > > wrote: > > > > > > Unlike what is claimed in commit f5aa7d46b0ee ("drm/bridge: > > >

Re: [PATCH v3 01/11] drm/mediatek: Add interface to allocate MediaTek GEM buffer.

2023-12-25 Thread 胡俊光

Re: [PATCH -next] drm/nouveau: uapi: fix kerneldoc warnings

2023-12-25 Thread Vegard Nossum
On 25/12/2023 08:40, Randy Dunlap wrote: I do see one thing that I don't like in the generated html output. It's not a problem with this patch. The #defines for DRM_NOUVEAU_VM_BIND_OP_MAP etc. have a ';' at the end of each line: struct drm_nouveau_vm_bind_op { __u32 op; #define