[PATCH AUTOSEL 6.4 20/31] drm/amd/display: Blocking invalid 420 modes on HDMI TMDS for DCN314

From: Leo Chen [ Upstream commit 4c6107a653ccf361cb1b6ba35d558a1a5e6e57ac ] [Why & How] HDMI TMDS does not have ODM support. Filtering 420 modes that exceed the 4096 FMT limitation on DCN314 will resolve intermittent corruptions issues. Reviewed-by: Nicholas Kazlauskas Acked-by: Tom Chung Sig

[PATCH AUTOSEL 6.4 23/31] drm/mediatek: dp: Change logging to dev for mtk_dp_aux_transfer()

From: AngeloGioacchino Del Regno [ Upstream commit fd70e2019bfbcb0ed90c5e23839bf510ce6acf8f ] Change logging from drm_{err,info}() to dev_{err,info}() in functions mtk_dp_aux_transfer() and mtk_dp_aux_do_transfer(): this will be essential to avoid getting NULL pointer kernel panics if any kind o

[PATCH] drm/msm/dpu: enable smartdma on sm8350

To support high resolutions on sm8350, enable smartdma in its catalog. Signed-off-by: Abhinav Kumar --- Notes: only compile tested, to be landed after sufficient testing .../drm/msm/disp/dpu1/catalog/dpu_7_0_sm8350.h | 16 1 file changed, 8 insertions(+), 8 deletions(-)

[PATCH AUTOSEL 6.1 01/22] drm/bridge: tc358762: Instruct DSI host to generate HSE packets

From: Marek Vasut [ Upstream commit 362fa8f6e6a05089872809f4465bab9d011d05b3 ] This bridge seems to need the HSE packet, otherwise the image is shifted up and corrupted at the bottom. This makes the bridge work with Samsung DSIM on i.MX8MM and i.MX8MP. Signed-off-by: Marek Vasut Reviewed-by: S

[PATCH AUTOSEL 6.1 02/22] drm/edid: Add quirk for OSVR HDK 2.0

From: Ralph Campbell [ Upstream commit 98d4cb705bc00afd4a9a71cc1e84f7111682639a ] The OSVR virtual reality headset HDK 2.0 uses a different EDID vendor and device identifier than the HDK 1.1 - 1.4 headsets. Add the HDK 2.0 vendor and device identifier to the quirks table so that window managers

[PATCH AUTOSEL 6.1 08/22] drm/amd/display: Read down-spread percentage from lut to adjust dprefclk.

From: Martin Tsai [ Upstream commit 6917b0b711713b9d84d7e0844e9aa613997a51b2 ] [Why] Panels show corruption with high refresh rate timings when ss is enabled. [How] Read down-spread percentage from lut to adjust dprefclk. Reviewed-by: Nicholas Kazlauskas Acked-by: Alex Hung Signed-off-by: Ma

[PATCH AUTOSEL 6.1 10/22] drm/vkms: Fix race-condition between the hrtimer and the atomic commit

From: Maíra Canal [ Upstream commit a0e6a017ab56936c0405fe914a793b241ed25ee0 ] Currently, it is possible for the composer to be set as enabled and then as disabled without a proper call for the vkms_vblank_simulate(). This is problematic, because the driver would skip one CRC output, causing CRC

[PATCH AUTOSEL 6.1 09/22] drm/amd/display: Fix underflow issue on 175hz timing

From: Leo Ma [ Upstream commit 735688eb905db529efea0c78466fccc1461c3fde ] [Why] Screen underflows happen on 175hz timing for 3 plane overlay case. [How] Based on dst y prefetch value clamp to equ or oto for bandwidth calculation. Reviewed-by: Dillon Varone Acked-by: Alex Hung Signed-off-by:

[PATCH AUTOSEL 6.1 14/22] drm/amd/display: Use DTBCLK as refclk instead of DPREFCLK

From: Austin Zheng [ Upstream commit 4a30cc2bd281fa176a68b5305cd3695d636152ad ] [Why] Flash of corruption observed when UCLK switching after transitioning from DTBCLK to DPREFCLK on subVP(DP) + subVP(HDMI) config Scenario where DPREFCLK is required instead of DTBCLK is not expected [How] Always

[PATCH AUTOSEL 6.1 15/22] drm/amd/display: Blocking invalid 420 modes on HDMI TMDS for DCN31

From: Leo Chen [ Upstream commit 026a71babf48efb6b9884a3a66fa31aec9e1ea54 ] [Why & How] HDMI TMDS does not have ODM support. Filtering 420 modes that exceed the 4096 FMT limitation on DCN31 will resolve intermittent corruptions issues. Reviewed-by: Nicholas Kazlauskas Acked-by: Tom Chung Sign

[PATCH AUTOSEL 6.1 18/22] drm/mediatek: dp: Change logging to dev for mtk_dp_aux_transfer()

From: AngeloGioacchino Del Regno [ Upstream commit fd70e2019bfbcb0ed90c5e23839bf510ce6acf8f ] Change logging from drm_{err,info}() to dev_{err,info}() in functions mtk_dp_aux_transfer() and mtk_dp_aux_do_transfer(): this will be essential to avoid getting NULL pointer kernel panics if any kind o

[PATCH AUTOSEL 6.1 17/22] drm/exynos: fix a possible null-pointer dereference due to data race in exynos_drm_crtc_atomic_disable()

From: Tuo Li [ Upstream commit 2e63972a2de14482d0eae1a03a73e379f1c3f44c ] The variable crtc->state->event is often protected by the lock crtc->dev->event_lock when is accessed. However, it is accessed as a condition of an if statement in exynos_drm_crtc_atomic_disable() without holding the lock:

[PATCH AUTOSEL 6.1 16/22] drm/amd/display: Blocking invalid 420 modes on HDMI TMDS for DCN314

From: Leo Chen [ Upstream commit 4c6107a653ccf361cb1b6ba35d558a1a5e6e57ac ] [Why & How] HDMI TMDS does not have ODM support. Filtering 420 modes that exceed the 4096 FMT limitation on DCN314 will resolve intermittent corruptions issues. Reviewed-by: Nicholas Kazlauskas Acked-by: Tom Chung Sig

[PATCH AUTOSEL 5.15 01/13] drm/bridge: tc358762: Instruct DSI host to generate HSE packets

From: Marek Vasut [ Upstream commit 362fa8f6e6a05089872809f4465bab9d011d05b3 ] This bridge seems to need the HSE packet, otherwise the image is shifted up and corrupted at the bottom. This makes the bridge work with Samsung DSIM on i.MX8MM and i.MX8MP. Signed-off-by: Marek Vasut Reviewed-by: S

[PATCH AUTOSEL 5.15 06/13] drm/vkms: Fix race-condition between the hrtimer and the atomic commit

From: Maíra Canal [ Upstream commit a0e6a017ab56936c0405fe914a793b241ed25ee0 ] Currently, it is possible for the composer to be set as enabled and then as disabled without a proper call for the vkms_vblank_simulate(). This is problematic, because the driver would skip one CRC output, causing CRC

[PATCH AUTOSEL 5.15 09/13] drm/amd/display: Blocking invalid 420 modes on HDMI TMDS for DCN31

From: Leo Chen [ Upstream commit 026a71babf48efb6b9884a3a66fa31aec9e1ea54 ] [Why & How] HDMI TMDS does not have ODM support. Filtering 420 modes that exceed the 4096 FMT limitation on DCN31 will resolve intermittent corruptions issues. Reviewed-by: Nicholas Kazlauskas Acked-by: Tom Chung Sign

[PATCH AUTOSEL 5.15 10/13] drm/exynos: fix a possible null-pointer dereference due to data race in exynos_drm_crtc_atomic_disable()

From: Tuo Li [ Upstream commit 2e63972a2de14482d0eae1a03a73e379f1c3f44c ] The variable crtc->state->event is often protected by the lock crtc->dev->event_lock when is accessed. However, it is accessed as a condition of an if statement in exynos_drm_crtc_atomic_disable() without holding the lock:

[PATCH AUTOSEL 5.10 1/9] drm/bridge: tc358762: Instruct DSI host to generate HSE packets

From: Marek Vasut [ Upstream commit 362fa8f6e6a05089872809f4465bab9d011d05b3 ] This bridge seems to need the HSE packet, otherwise the image is shifted up and corrupted at the bottom. This makes the bridge work with Samsung DSIM on i.MX8MM and i.MX8MP. Signed-off-by: Marek Vasut Reviewed-by: S

[PATCH AUTOSEL 5.10 6/9] drm/exynos: fix a possible null-pointer dereference due to data race in exynos_drm_crtc_atomic_disable()

From: Tuo Li [ Upstream commit 2e63972a2de14482d0eae1a03a73e379f1c3f44c ] The variable crtc->state->event is often protected by the lock crtc->dev->event_lock when is accessed. However, it is accessed as a condition of an if statement in exynos_drm_crtc_atomic_disable() without holding the lock:

[PATCH AUTOSEL 5.4 1/4] drm/exynos: fix a possible null-pointer dereference due to data race in exynos_drm_crtc_atomic_disable()

From: Tuo Li [ Upstream commit 2e63972a2de14482d0eae1a03a73e379f1c3f44c ] The variable crtc->state->event is often protected by the lock crtc->dev->event_lock when is accessed. However, it is accessed as a condition of an if statement in exynos_drm_crtc_atomic_disable() without holding the lock:

[PATCH AUTOSEL 4.19 1/3] drm/exynos: fix a possible null-pointer dereference due to data race in exynos_drm_crtc_atomic_disable()

From: Tuo Li [ Upstream commit 2e63972a2de14482d0eae1a03a73e379f1c3f44c ] The variable crtc->state->event is often protected by the lock crtc->dev->event_lock when is accessed. However, it is accessed as a condition of an if statement in exynos_drm_crtc_atomic_disable() without holding the lock:

[PATCH AUTOSEL 4.14 1/3] drm/exynos: fix a possible null-pointer dereference due to data race in exynos_drm_crtc_atomic_disable()

From: Tuo Li [ Upstream commit 2e63972a2de14482d0eae1a03a73e379f1c3f44c ] The variable crtc->state->event is often protected by the lock crtc->dev->event_lock when is accessed. However, it is accessed as a condition of an if statement in exynos_drm_crtc_atomic_disable() without holding the lock:

[PATCH v2 0/5] Introduce new wrappers to copy user-arrays

Hi! David Airlie suggested that we could implement new wrappers around (v)memdup_user() for duplicating user arrays. This small patch series first implements the two new wrapper functions memdup_array_user() and vmemdup_array_user(). They calculate the array-sizes safely, i.e., they return an err

[PATCH v2 1/5] string.h: add array-wrappers for (v)memdup_user()

Currently, user array duplications are sometimes done without an overflow check. Sometimes the checks are done manually; sometimes the array size is calculated with array_size() and sometimes by calculating n * size directly in code. Introduce wrappers for arrays for memdup_user() and vmemdup_user

[PATCH v2 2/5] kernel: kexec: copy user-array safely

Currently, there is no overflow-check with memdup_user(). Use the new function memdup_array_user() instead of memdup_user() for duplicating the user-space array safely. Suggested-by: David Airlie Signed-off-by: Philipp Stanner --- kernel/kexec.c | 2 +- 1 file changed, 1 insertion(+), 1 deleti

[PATCH v2 3/5] kernel: watch_queue: copy user-array safely

Currently, there is no overflow-check with memdup_user(). Use the new function memdup_array_user() instead of memdup_user() for duplicating the user-space array safely. Suggested-by: David Airlie Signed-off-by: Philipp Stanner --- kernel/watch_queue.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH v2 4/5] drm_lease.c: copy user-array safely

Currently, there is no overflow-check with memdup_user(). Use the new function memdup_array_user() instead of memdup_user() for duplicating the user-space array safely. Suggested-by: David Airlie Signed-off-by: Philipp Stanner --- drivers/gpu/drm/drm_lease.c | 4 ++-- 1 file changed, 2 inserti

[PATCH v2 5/5] drm: vmgfx_surface.c: copy user-array safely

Currently, there is no overflow-check with memdup_user(). Use the new function memdup_array_user() instead of memdup_user() for duplicating the user-space array safely. Suggested-by: David Airlie Signed-off-by: Philipp Stanner --- drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 4 ++-- 1 file change

Re: [PATCH 07/10] drm/tests: Add test for drm_framebuffer_init()

Hi Carlos, On 9/4/23 14:41, Carlos wrote: Hi Maíra, On 8/26/23 11:16, Maíra Canal wrote: Hi Carlos, On 8/25/23 13:11, Carlos Eduardo Gallo Filho wrote: Add a single KUnit test case for the drm_framebuffer_init function. Signed-off-by: Carlos Eduardo Gallo Filho ---   drivers/gpu/drm/tests/

Re: [PATCH 03/10] drm/tests: Add test case for drm_internal_framebuffer_create()

Hi Carlos, On 9/4/23 13:57, Carlos wrote: Hi Maíra, On 8/26/23 10:58, Maíra Canal wrote: Hi Carlos, On 8/25/23 13:07, Carlos Eduardo Gallo Filho wrote: Introduce a test to cover the creation of framebuffer with modifier on a device that doesn't support it. Signed-off-by: Carlos Eduardo Gall

Re: [PATCH 06/10] drm/tests: Add test for drm_framebuffer_lookup()

Hi Carlos, On 9/4/23 15:52, Carlos wrote: Hi Maíra, On 8/26/23 11:13, Maíra Canal wrote: Hi Carlos, On 8/25/23 13:07, Carlos Eduardo Gallo Filho wrote: Add a single KUnit test case for the drm_framebuffer_lookup function. Signed-off-by: Carlos Eduardo Gallo Filho ---   drivers/gpu/drm/test

Re: [RFC PATCH 01/10] drm/doc/rfc: Describe why prescriptive color pipeline is needed

On 2023-09-08 15:30, Sebastian Wick wrote: Hey Harry, Thank you and Simon for this great document. Really happy about it, but obviously I've got a few notes and questions inline. On Fri, Sep 08, 2023 at 11:02:26AM -0400, Harry Wentland wrote: Signed-off-by: Harry Wentland Cc: Ville Syrjala

Re: [PATCH 05/10] drm/tests: Add test for drm_framebuffer_cleanup()

Hi Carlos, On 9/4/23 14:22, Carlos wrote: Hi Maíra, On 8/26/23 11:06, Maíra Canal wrote: Hi Carlos, On 8/25/23 13:07, Carlos Eduardo Gallo Filho wrote: Add a single KUnit test case for the drm_framebuffer_cleanup function. Signed-off-by: Carlos Eduardo Gallo Filho ---   drivers/gpu/drm/tes

Re: [PATCH] drm/debugfs: Add inline to drm_debugfs_dev_init() to suppres -Wunused-function

Hi Arthur, On 9/1/23 15:05, Arthur Grillo wrote: When CONFIG_DEBUG_FS is not set -Wunused-function warnings appear, make the static function inline to suppress that. Reported-by: kernel test robot Closes: https://lore.kernel.org/oe-kbuild-all/202309012114.t8vlfaf8-...@intel.com/ Closes: http

Re: [PATCH] drm/tests: Zero initialize fourccs_out

Hi Arthur, On 9/1/23 15:52, Arthur Grillo wrote: fourccs_out array is not initialized. As the drm_fb_build_fourcc_list() doesn't necessarily change all the array, and the test compares all of it, the comparison could fail if the array is not initialized. Zero initialize the array to fix this. F

Re: [PATCH v2 1/2] drm/tests: Add calls to drm_fb_blit() on supported format conversion tests

Hi Arthur, On 9/5/23 18:27, Arthur Grillo wrote: Add a call to drm_fb_blit() on existing format conversion tests that has support. Signed-off-by: Arthur Grillo Reviewed-by: Maíra Canal Best Regards, - Maíra --- drivers/gpu/drm/tests/drm_format_helper_test.c | 142 ++

Re: [PATCH v2 2/2] drm/tests: Add new format conversion tests to better cover drm_fb_blit()

Hi Arthur, On 9/5/23 18:27, Arthur Grillo wrote: To fully cover drm_fb_blit(), add format conversion tests that are only supported through drm_fb_blit(). Signed-off-by: Arthur Grillo Reviewed-by: Maíra Canal Best Regards, - Maíra --- drivers/gpu/drm/tests/drm_format_helper_test.c | 142

[PATCH] drm/doc/rfc: Mark long running workload as complete.

From: Matthew Brost No DRM scheduler changes required, drivers just return NULL in run_job vfunc. Signed-off-by: Matthew Brost --- Christian, Alex, Danilo, Lina, and others I'd like to kindly ask your attention and probably an ack from you here. Based on [1] and other discussions that we had

Re: [PATCH v3] drm/i915: Run relevant bits of debugfs drop_caches per GT

Hi Rodrigo and Nirmoy, On Thu, Sep 07, 2023 at 09:47:19AM -0400, Rodrigo Vivi wrote: > On Thu, Sep 07, 2023 at 02:58:08PM +0200, Andi Shyti wrote: > > From: Tvrtko Ursulin > > > > Walk all GTs when doing the respective bits of drop_caches work. > > > > Signed-off-by: Tvrtko Ursulin > > Signed-

Re: [PATCH 1/2] drm/msm/dpu: fail dpu_plane_atomic_check() based on mdp clk limits

On Fri, 8 Sept 2023 at 21:56, Abhinav Kumar wrote: > > Currently, dpu_plane_atomic_check() does not check whether the > plane can process the image without exceeding the per chipset > limits for MDP clock. This leads to underflow issues because the > SSPP is not able to complete the processing for

Re: [PATCH] drm/msm/dpu: enable smartdma on sm8350

On Fri, 8 Sept 2023 at 22:33, Abhinav Kumar wrote: > > To support high resolutions on sm8350, enable smartdma > in its catalog. > > Signed-off-by: Abhinav Kumar > --- > > Notes: > only compile tested, to be landed after sufficient testing I'll test sm8350 (and hopefully sm8450) early next we

Re: [PATCH 2/2] drm/msm/dpu: try multirect based on mdp clock limits

On Fri, 8 Sept 2023 at 21:55, Abhinav Kumar wrote: > > It's certainly possible that for large resolutions a single DPU SSPP > cannot process the image without exceeding the MDP clock limits but > it can still process it in multirect mode because the source rectangles > will get divided and can fal

Re: EXT: Re: [RFC] drm/bridge: megachips-stdpxxxx-ge-b850v3-fw: switch to drm_do_get_edid()

On Fri, Sep 01, 2023 at 05:52:02PM +0300, Jani Nikula wrote: > > On Fri, 01 Sep 2023, Jani Nikula wrote: > > The driver was originally added in commit fcfa0ddc18ed ("drm/bridge: > > Drivers for megachips-stdp-ge-b850v3-fw (LVDS-DP++)"). I tried to > > look up the discussion, but didn't find a

回复: [PATCH] drm/komeda: add NV12 format to support writeback layer type

Hi all, Do you have any suggestions for the patch I submitted? Please also let me know, thank you! Best Regards, baozhu.liu -邮件原件- 发件人: baozhu.liu 发送时间: 2023年8月29日 17:30 收件人: liviu.du...@arm.com; airl...@gmail.com; dan...@ffwll.ch 抄送: dri-devel@lists.freedesktop.org; linux-ker

<    1   2