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

2023-09-08 Thread Liu Lucas/刘保柱
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;

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

2023-09-08 Thread Ian Ray
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

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

2023-09-08 Thread Dmitry Baryshkov
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

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

2023-09-08 Thread Dmitry Baryshkov
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

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

2023-09-08 Thread Dmitry Baryshkov
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

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

2023-09-08 Thread Andi Shyti
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 > >

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

2023-09-08 Thread Rodrigo Vivi
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 v2 2/2] drm/tests: Add new format conversion tests to better cover drm_fb_blit()

2023-09-08 Thread Maira Canal
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 |

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

2023-09-08 Thread Maira Canal
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] drm/tests: Zero initialize fourccs_out

2023-09-08 Thread Maira Canal
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.

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

2023-09-08 Thread Maira Canal
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:

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

2023-09-08 Thread Maira Canal
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 ---  

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

2023-09-08 Thread Harry Wentland
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

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

2023-09-08 Thread Maira Canal
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 ---  

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

2023-09-08 Thread Maira Canal
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

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

2023-09-08 Thread Maira Canal
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 ---  

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

2023-09-08 Thread Philipp Stanner
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

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

2023-09-08 Thread Philipp Stanner
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

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

2023-09-08 Thread Philipp Stanner
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 2/5] kernel: kexec: copy user-array safely

2023-09-08 Thread Philipp Stanner
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

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

2023-09-08 Thread Philipp Stanner
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

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

2023-09-08 Thread Philipp Stanner
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

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

2023-09-08 Thread Sasha Levin
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

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

2023-09-08 Thread Sasha Levin
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

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

2023-09-08 Thread Sasha Levin
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

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

2023-09-08 Thread Sasha Levin
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

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

2023-09-08 Thread Sasha Levin
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:

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

2023-09-08 Thread Sasha Levin
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

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

2023-09-08 Thread Sasha Levin
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

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

2023-09-08 Thread Sasha Levin
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

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

2023-09-08 Thread Sasha Levin
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:

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

2023-09-08 Thread Sasha Levin
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

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

2023-09-08 Thread Sasha Levin
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

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

2023-09-08 Thread Sasha Levin
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

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

2023-09-08 Thread Sasha Levin
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

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

2023-09-08 Thread Sasha Levin
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]

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

2023-09-08 Thread Sasha Levin
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 10/22] drm/vkms: Fix race-condition between the hrtimer and the atomic commit

2023-09-08 Thread Sasha Levin
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

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

2023-09-08 Thread Sasha Levin
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:

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

2023-09-08 Thread Sasha Levin
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 01/22] drm/bridge: tc358762: Instruct DSI host to generate HSE packets

2023-09-08 Thread Sasha Levin
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:

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

2023-09-08 Thread Abhinav Kumar
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.4 23/31] drm/mediatek: dp: Change logging to dev for mtk_dp_aux_transfer()

2023-09-08 Thread Sasha Levin
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

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

2023-09-08 Thread Sasha Levin
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

[PATCH AUTOSEL 6.4 21/31] drm/exynos: fix a possible null-pointer dereference due to data race in exynos_drm_crtc_atomic_disable()

2023-09-08 Thread Sasha Levin
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

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

2023-09-08 Thread Sasha Levin
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

[PATCH AUTOSEL 6.4 18/31] drm/amd/display: Use DTBCLK as refclk instead of DPREFCLK

2023-09-08 Thread Sasha Levin
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]

[PATCH AUTOSEL 6.4 14/31] drm/vkms: Fix race-condition between the hrtimer and the atomic commit

2023-09-08 Thread Sasha Levin
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

[PATCH AUTOSEL 6.4 13/31] drm/amd/display: Fix underflow issue on 175hz timing

2023-09-08 Thread Sasha Levin
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.4 12/31] drm/amd/display: Read down-spread percentage from lut to adjust dprefclk.

2023-09-08 Thread Sasha Levin
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:

[PATCH AUTOSEL 6.4 10/31] drm/amd/display: Add stream overhead in BW calculations for 128b/132b

2023-09-08 Thread Sasha Levin
From: George Shen [ Upstream commit 974764180838516f80a13257da67a1ec6afb87d4 ] [Why] Current BW calculations do not account for the additional padding added for uncompressed pixel-to-symbol packing. This results in X.Y being too low for 128b/132b SST streams in certain scenarios. If X.Y is too

[PATCH AUTOSEL 6.4 03/31] drm: bridge: samsung-dsim: Drain command transfer FIFO before transfer

2023-09-08 Thread Sasha Levin
From: Marek Vasut [ Upstream commit 14806c6415820b1c4bc317655c40784d050a2edb ] Wait until the command transfer FIFO is empty before loading in the next command. The previous behavior where the code waited until command transfer FIFO was not full suffered from transfer corruption, where the last

[PATCH AUTOSEL 6.4 02/31] drm/edid: Add quirk for OSVR HDK 2.0

2023-09-08 Thread Sasha Levin
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.4 01/31] drm/bridge: tc358762: Instruct DSI host to generate HSE packets

2023-09-08 Thread Sasha Levin
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:

[PATCH AUTOSEL 6.5 28/36] drm/mediatek: dp: Change logging to dev for mtk_dp_aux_transfer()

2023-09-08 Thread Sasha Levin
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

[PATCH AUTOSEL 6.5 26/36] drm/exynos: fix a possible null-pointer dereference due to data race in exynos_drm_crtc_atomic_disable()

2023-09-08 Thread Sasha Levin
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

[PATCH AUTOSEL 6.5 25/36] drm/msm/adreno: Use quirk to identify cached-coherent support

2023-09-08 Thread Sasha Levin
From: Rob Clark [ Upstream commit 155668ef412fc82ff3172666831d95770141cdd6 ] It is better to explicitly list it. With the move to opaque chip-id's for future devices, we should avoid trying to infer things like generation from the numerical value. Signed-off-by: Rob Clark Reviewed-by: Konrad

[PATCH AUTOSEL 6.5 24/36] drm/msm/adreno: Use quirk identify hw_apriv

2023-09-08 Thread Sasha Levin
From: Rob Clark [ Upstream commit 459f9e26e7d49f80f587d7592ccb78e00ab458e4 ] Rather than just open coding a list of gpu-id matches. Signed-off-by: Rob Clark Reviewed-by: Konrad Dybcio Reviewed-by: Dmitry Baryshkov Patchwork: https://patchwork.freedesktop.org/patch/549764/ Signed-off-by:

[PATCH AUTOSEL 6.5 23/36] drm/amd/display: Use max memclk variable when setting max memclk

2023-09-08 Thread Sasha Levin
From: Alvin Lee [ Upstream commit 2b1b838ea8e5437ef06a29818d16e9efdfaf0037 ] [Description] In overclocking scenarios the max memclk could be higher than the DC mode limit. However, for configs that don't support MCLK switching we need to set the max memclk to the overclocked max instead of the

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

2023-09-08 Thread Sasha Levin
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

[PATCH AUTOSEL 6.5 21/36] drm/amd/display: Blocking invalid 420 modes on HDMI TMDS for DCN31

2023-09-08 Thread Sasha Levin
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

[PATCH AUTOSEL 6.5 20/36] drm/amd/display: Use DTBCLK as refclk instead of DPREFCLK

2023-09-08 Thread Sasha Levin
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]

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

2023-09-08 Thread Sebastian Wick
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 > Cc: Pekka Paalanen > Cc: Simon Ser >

[PATCH AUTOSEL 6.5 16/36] drm/vkms: Fix race-condition between the hrtimer and the atomic commit

2023-09-08 Thread Sasha Levin
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

[PATCH AUTOSEL 6.5 15/36] drm/amd/display: Fix underflow issue on 175hz timing

2023-09-08 Thread Sasha Levin
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.5 14/36] drm/amd/display: Read down-spread percentage from lut to adjust dprefclk.

2023-09-08 Thread Sasha Levin
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:

[PATCH AUTOSEL 6.5 13/36] drm/amdgpu: Update ring scheduler info as needed

2023-09-08 Thread Sasha Levin
From: Lijo Lazar [ Upstream commit 6cb209ed68e45c8e4b71d97a037ac6b7dbce9b50 ] Not all rings have scheduler associated. Only update scheduler data for rings with scheduler. It could result in out of bound access as total rings are more than those associated with particular IPs. Signed-off-by:

[PATCH AUTOSEL 6.5 11/36] drm/amd/display: Add stream overhead in BW calculations for 128b/132b

2023-09-08 Thread Sasha Levin
From: George Shen [ Upstream commit 974764180838516f80a13257da67a1ec6afb87d4 ] [Why] Current BW calculations do not account for the additional padding added for uncompressed pixel-to-symbol packing. This results in X.Y being too low for 128b/132b SST streams in certain scenarios. If X.Y is too

[PATCH AUTOSEL 6.5 10/36] drm/amdgpu: Increase soft IH ring size

2023-09-08 Thread Sasha Levin
From: Philip Yang [ Upstream commit bf80d34b6c58ad1c4f76067ecd460a148eab9d39 ] Retry faults are delegated to soft IH ring and then processed by deferred worker. Current soft IH ring size PAGE_SIZE can store 128 entries, which may overflow and drop retry faults, causes HW stucks because the

[PATCH AUTOSEL 6.5 03/36] drm: bridge: samsung-dsim: Drain command transfer FIFO before transfer

2023-09-08 Thread Sasha Levin
From: Marek Vasut [ Upstream commit 14806c6415820b1c4bc317655c40784d050a2edb ] Wait until the command transfer FIFO is empty before loading in the next command. The previous behavior where the code waited until command transfer FIFO was not full suffered from transfer corruption, where the last

[PATCH AUTOSEL 6.5 02/36] drm/edid: Add quirk for OSVR HDK 2.0

2023-09-08 Thread Sasha Levin
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.5 01/36] drm/bridge: tc358762: Instruct DSI host to generate HSE packets

2023-09-08 Thread Sasha Levin
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:

Re: [PATCH 3/3] drm/mst: adjust the function drm_dp_remove_payload_part2()

2023-09-08 Thread Imre Deak
On Thu, Sep 07, 2023 at 03:44:39AM +, Lin, Wayne wrote: > [AMD Official Use Only - General] > > > -Original Message- > > From: Imre Deak > > Sent: Friday, August 25, 2023 9:56 PM > > To: Lin, Wayne > > Cc: dri-devel@lists.freedesktop.org; amd-...@lists.freedesktop.org; > >

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

2023-09-08 Thread Abhinav Kumar
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 the data rate of the display. Fail the

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

2023-09-08 Thread Abhinav Kumar
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 fall within the MDP clock limits. If the SSPP cannot process

[PATCH] drm/sched: test before reading fence timestamp

2023-09-08 Thread Yunxiang Li
Reading fence timestamp always need to check the corresponding flag bit before to make sure the write is actually visible, otherwise we can read garbage here. Fixes: 1774baa64f93 ("drm/scheduler: Change scheduled fence track v2") Signed-off-by: Yunxiang Li ---

[Bug 217889] WARNING: CPU: 0 PID: 5172 at drivers/gpu/drm/ttm/ttm_bo.c:362 ttm_bo_release+0x309/0x330 [ttm] after resolution change

2023-09-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=217889 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED

Re: [PATCH v3] drm/plane: Add documentation about software color conversion.

2023-09-08 Thread Thomas Zimmermann
Hi Am 08.09.23 um 16:48 schrieb Jocelyn Falempe: On 08/09/2023 15:56, Thomas Zimmermann wrote: Hi Am 08.09.23 um 13:16 schrieb Pekka Paalanen: On Fri, 8 Sep 2023 11:21:51 +0200 Thomas Zimmermann wrote: Hi Am 25.08.23 um 16:04 schrieb Jocelyn Falempe: [...] + * + * But there are two

[PATCH v3 9/9] drm: ci: Use scripts/config to enable/disable configs

2023-09-08 Thread Vignesh Raman
Instead of modifying files in git to enable/disable configs, use scripts/config on the .config file which will be used for building the kernel. Suggested-by: Jani Nikula Signed-off-by: Vignesh Raman --- v2: - Added a new patch in the series to use scripts/config to enable/disable configs

[PATCH v3 8/9] drm: ci: Enable new jobs

2023-09-08 Thread Vignesh Raman
Enable the following jobs, as the issues noted in the TODO comments have been resolved. This will ensure that these jobs are now included and executed as part of the CI/CD pipeline. msm:apq8016: TODO: current issue: it is not fiding the NFS root. Fix and remove this rule. mediatek:mt8173: TODO:

[PATCH v3 7/9] drm: ci: Update xfails

2023-09-08 Thread Vignesh Raman
Update amdgpu-stoney-fails, mediatek-mt8173-flakes, mediatek-mt8173-fails, rockchip-rk3399-fails, rockchip-rk3399-flakes, rockchip-rk3288-flakes, i915-cml-fails, i915-cml-flakes, msm-apq8016-flakes files. Add tests that fail sometimes into the *-flakes file and tests that are failing into the

[PATCH v3 6/9] arm64: defconfig: Enable DA9211 regulator

2023-09-08 Thread Vignesh Raman
Mediatek mt8173 board fails to boot with DA9211 regulator disabled. Enabling CONFIG_REGULATOR_DA9211=y in drm-ci fixes the issue. So enable it in the defconfig since kernel-ci also requires it. Suggested-by: AngeloGioacchino Del Regno Signed-off-by: Vignesh Raman --- v3: - New patch in the

[PATCH v3 5/9] drm: ci: Enable regulator

2023-09-08 Thread Vignesh Raman
Enable CONFIG_REGULATOR_DA9211=y to fix mt8173 boot issue. Signed-off-by: Vignesh Raman --- v2: - No changes v3: - Remove CONFIG_RTC_DRV_MT6397=y as it is already enabled in defconfig --- drivers/gpu/drm/ci/arm64.config | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v3 4/9] drm: ci: virtio: Update ci variables

2023-09-08 Thread Vignesh Raman
Update ci variables to fix the below error, ERROR - Igt error: malloc(): corrupted top size ERROR - Igt error: Received signal SIGABRT. ERROR - Igt error: Stack trace: ERROR - Igt error: #0 [fatal_sig_handler+0x17b] Signed-off-by: Vignesh Raman --- v2: - No changes v3: - No changes ---

[PATCH v3 3/9] drm: ci: Force db410c to host mode

2023-09-08 Thread Vignesh Raman
Force db410c to host mode to fix network issue which results in failure to mount root fs via NFS. See https://gitlab.freedesktop.org/gfx-ci/linux/-/commit/cb72a629b8c15c80a54dda510743cefd1c4b65b8 Compile the base device tree with overlay support and use fdtoverlay command to merge base device

[PATCH v3 2/9] arm64: dts: qcom: apq8016-sbc: Add overlay for usb host mode

2023-09-08 Thread Vignesh Raman
Due to the presence of the fastboot micro cable in the CI farm, it causes the hardware to remain in gadget mode instead of host mode. So it doesn't find the network, which results in failure to mount root fs via NFS. Add an overlay dtso file that sets the dr_mode to host, allowing the USB

[PATCH v3 1/9] drm: ci: igt_runner: Remove todo

2023-09-08 Thread Vignesh Raman
/sys/kernel/debug/dri/*/state exist for every atomic KMS driver. We do not test non-atomic drivers, so remove the todo. Signed-off-by: Vignesh Raman --- v2: - No changes v3: - No changes --- drivers/gpu/drm/ci/igt_runner.sh | 1 - 1 file changed, 1 deletion(-) diff --git

[PATCH v3 0/9] drm: ci: fixes

2023-09-08 Thread Vignesh Raman
The patch series contains improvements, enabling new ci jobs which enables testing for Mediatek MT8173, Qualcomm APQ 8016 and VirtIO GPU, fixing issues with the ci jobs and updating the expectation files. This series is intended for drm branch topic/drm-ci. v2: - Use fdtoverlay command to merge

Re: [PATCH v3] drm/plane: Add documentation about software color conversion.

2023-09-08 Thread Thomas Zimmermann
Hi Am 08.09.23 um 16:41 schrieb Pekka Paalanen: On Fri, 8 Sep 2023 15:56:51 +0200 Thomas Zimmermann wrote: Hi Am 08.09.23 um 13:16 schrieb Pekka Paalanen: On Fri, 8 Sep 2023 11:21:51 +0200 Thomas Zimmermann wrote: Hi Am 25.08.23 um 16:04 schrieb Jocelyn Falempe: [...] + * + *

Re: [PATCH v2 1/2] drm/amd/display: fix the white screen issue when >= 64GB DRAM

2023-09-08 Thread Alex Deucher
Series is: Reviewed-by: Alex Deucher On Fri, Sep 8, 2023 at 10:56 AM Hamza Mahfooz wrote: > > From: Yifan Zhang > > Dropping bit 31:4 of page table base is wrong, it makes page table > base points to wrong address if phys addr is beyond 64GB; dropping > page_table_start/end bit 31:4 is

Re: [PATCH v2 2/2] Revert "drm/amd: Disable S/G for APUs when 64GB or more host memory"

2023-09-08 Thread Harry Wentland
Series is Acked-by: Harry Wentland Harry On 2023-09-08 10:55, Hamza Mahfooz wrote: This reverts commit 5b7a256c982636ebc4f16b708b40ff56d33c8a86. Since, we now have an actual fix for this issue, we can get rid of this workaround as it can cause pin failures if enough VRAM isn't carved out by

[Bug 217889] New: WARNING: CPU: 0 PID: 5172 at drivers/gpu/drm/ttm/ttm_bo.c:362 ttm_bo_release+0x309/0x330 [ttm] after resolution change

2023-09-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=217889 Bug ID: 217889 Summary: WARNING: CPU: 0 PID: 5172 at drivers/gpu/drm/ttm/ttm_bo.c:362 ttm_bo_release+0x309/0x330 [ttm] after resolution change Product:

[RFC PATCH 09/10] drm/plane: Add COLOR PIPELINE property

2023-09-08 Thread Harry Wentland
We're adding a new enum COLOR PIPELINE property. This property will have entries for each COLOR PIPELINE by referencing the DRM object ID of the first drm_colorop of the pipeline. 0 disables the entire COLOR PIPELINE. Userspace can use this to discover the available color pipelines, as well as

[RFC PATCH 10/10] drm/vkms: Add enumerated 1D curve colorop

2023-09-08 Thread Harry Wentland
Signed-off-by: Harry Wentland Cc: Ville Syrjala Cc: Pekka Paalanen Cc: Simon Ser Cc: Harry Wentland Cc: Melissa Wen Cc: Jonas Ådahl Cc: Sebastian Wick Cc: Shashank Sharma Cc: Alexander Goins Cc: Joshua Ashton Cc: Michel Dänzer Cc: Aleix Pol Cc: Xaver Hugl Cc: Victoria Brekenfeld Cc:

[RFC PATCH 08/10] drm/colorop: Add new IOCTLs to retrieve drm_colorop objects

2023-09-08 Thread Harry Wentland
Since we created a new DRM object we need new IOCTLs (and new libdrm functions) to retrieve those objects. TODO: Can we make these IOCTLs and libdrm functions generic to allow for new DRM objects in the future without the need for new IOCTLs and libdrm functions? Signed-off-by: Harry Wentland

[RFC PATCH 05/10] drm/colorop: Add BYPASS property

2023-09-08 Thread Harry Wentland
We want to be able to bypass each colorop at all times. Introduce a new BYPASS boolean property for this. Signed-off-by: Harry Wentland Cc: Ville Syrjala Cc: Pekka Paalanen Cc: Simon Ser Cc: Harry Wentland Cc: Melissa Wen Cc: Jonas Ådahl Cc: Sebastian Wick Cc: Shashank Sharma Cc:

[RFC PATCH 07/10] drm/colorop: Add atomic state print for drm_colorop

2023-09-08 Thread Harry Wentland
Signed-off-by: Harry Wentland Cc: Ville Syrjala Cc: Pekka Paalanen Cc: Simon Ser Cc: Harry Wentland Cc: Melissa Wen Cc: Jonas Ådahl Cc: Sebastian Wick Cc: Shashank Sharma Cc: Alexander Goins Cc: Joshua Ashton Cc: Michel Dänzer Cc: Aleix Pol Cc: Xaver Hugl Cc: Victoria Brekenfeld Cc:

[RFC PATCH 06/10] drm/colorop: Add NEXT property

2023-09-08 Thread Harry Wentland
We'll construct color pipelines out of drm_colorop by chaining them via the NEXT pointer. NEXT will point to the next drm_colorop in the pipeline, or by 0 if we're at the end of the pipeline. Signed-off-by: Harry Wentland Cc: Ville Syrjala Cc: Pekka Paalanen Cc: Simon Ser Cc: Harry Wentland

[RFC PATCH 04/10] drm/color: Add 1D Curve subtype

2023-09-08 Thread Harry Wentland
Signed-off-by: Harry Wentland Cc: Ville Syrjala Cc: Pekka Paalanen Cc: Simon Ser Cc: Harry Wentland Cc: Melissa Wen Cc: Jonas Ådahl Cc: Sebastian Wick Cc: Shashank Sharma Cc: Alexander Goins Cc: Joshua Ashton Cc: Michel Dänzer Cc: Aleix Pol Cc: Xaver Hugl Cc: Victoria Brekenfeld Cc:

[RFC PATCH 02/10] drm/colorop: Introduce new drm_colorop mode object

2023-09-08 Thread Harry Wentland
This patches introduces a new drm_colorop mode object. This object represents color transformations and can be used to define color pipelines. We also introduce the drm_colorop_state here, as well as various helpers and state tracking bits. Signed-off-by: Harry Wentland Cc: Ville Syrjala Cc:

  1   2   >