From: Maxime Ripard <maxime@cerno.tech> To: Daniel Vetter <daniel@ffwll.ch> Cc: "Rob Clark" <robdclark@chromium.org>, "Kalyan Thota" <quic_kalyant@quicinc.com>, "Daniel Vetter" <daniel.vetter@ffwll.ch>, "Michel Dänzer" <michel@daenzer.net>, "Abhinav Kumar" <quic_abhinavk@quicinc.com>, "DRI Development" <dri-devel@lists.freedesktop.org>, "Kazlauskas, Nicholas" <nicholas.kazlauskas@amd.com>, "Dmitry Osipenko" <dmitry.osipenko@collabora.com>, "Daniel Vetter" <daniel.vetter@intel.com>, "Jessica Zhang" <quic_jesszhan@quicinc.com>, "Mikita Lipski" <mikita.lipski@amd.com>, "Intel Graphics Development" <intel-gfx@lists.freedesktop.org> Subject: Re: [PATCH] drm/atomic-helpers: remove legacy_cursor_update hacks Date: Thu, 12 May 2022 10:08:35 +0200 [thread overview] Message-ID: <20220512080835.oy6cvqycgsfsjcly@houat> (raw) In-Reply-To: <YmqEBB1m6W3XMwsR@phenom.ffwll.local> [-- Attachment #1: Type: text/plain, Size: 794 bytes --] Hi Daniel, An update on this On Thu, Apr 28, 2022 at 02:09:40PM +0200, Daniel Vetter wrote: > > We integrated this in the (downstream) RaspberryPi kernel, and it seems > > to trigger some weird regressions: > > > > - If we move the cursor under X, the primary plane update is stuck: > > https://github.com/raspberrypi/linux/issues/4988 So it turns out the upstream driver doesn't seem affected by this, but only a downstream alternative. > > - Switching back and forth between VT gets the kernel stuck (with a > > locking issue in fb_release?) > > https://github.com/raspberrypi/linux/issues/5011 And this one turned out to be a separate issue fixed by Javier already. So as far as I'm concerned, this patch seems to be working fine on vc4 Maxime [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime@cerno.tech> To: Daniel Vetter <daniel@ffwll.ch> Cc: "Rob Clark" <robdclark@chromium.org>, "Kalyan Thota" <quic_kalyant@quicinc.com>, "Daniel Vetter" <daniel.vetter@ffwll.ch>, "Michel Dänzer" <michel@daenzer.net>, "Abhinav Kumar" <quic_abhinavk@quicinc.com>, "DRI Development" <dri-devel@lists.freedesktop.org>, "Kazlauskas, Nicholas" <nicholas.kazlauskas@amd.com>, "Dmitry Osipenko" <dmitry.osipenko@collabora.com>, "Daniel Vetter" <daniel.vetter@intel.com>, "Jessica Zhang" <quic_jesszhan@quicinc.com>, "Mikita Lipski" <mikita.lipski@amd.com>, "Intel Graphics Development" <intel-gfx@lists.freedesktop.org> Subject: Re: [Intel-gfx] [PATCH] drm/atomic-helpers: remove legacy_cursor_update hacks Date: Thu, 12 May 2022 10:08:35 +0200 [thread overview] Message-ID: <20220512080835.oy6cvqycgsfsjcly@houat> (raw) In-Reply-To: <YmqEBB1m6W3XMwsR@phenom.ffwll.local> [-- Attachment #1: Type: text/plain, Size: 794 bytes --] Hi Daniel, An update on this On Thu, Apr 28, 2022 at 02:09:40PM +0200, Daniel Vetter wrote: > > We integrated this in the (downstream) RaspberryPi kernel, and it seems > > to trigger some weird regressions: > > > > - If we move the cursor under X, the primary plane update is stuck: > > https://github.com/raspberrypi/linux/issues/4988 So it turns out the upstream driver doesn't seem affected by this, but only a downstream alternative. > > - Switching back and forth between VT gets the kernel stuck (with a > > locking issue in fb_release?) > > https://github.com/raspberrypi/linux/issues/5011 And this one turned out to be a separate issue fixed by Javier already. So as far as I'm concerned, this patch seems to be working fine on vc4 Maxime [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-05-12 8:08 UTC|newest] Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-31 15:20 [PATCH] drm/atomic-helpers: remove legacy_cursor_update hacks Daniel Vetter 2022-03-31 15:20 ` [Intel-gfx] " Daniel Vetter 2022-03-31 19:35 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork 2022-03-31 20:10 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork 2022-04-01 8:39 ` [PATCH] " Maxime Ripard 2022-04-01 8:39 ` [Intel-gfx] " Maxime Ripard 2022-04-06 21:57 ` Rob Clark 2022-04-06 21:57 ` [Intel-gfx] " Rob Clark 2022-04-07 1:27 ` Jessica Zhang 2022-04-07 1:27 ` [Intel-gfx] " Jessica Zhang 2022-04-07 9:33 ` Daniel Vetter 2022-04-07 9:33 ` [Intel-gfx] " Daniel Vetter 2022-04-07 22:51 ` Rob Clark 2022-04-07 22:51 ` [Intel-gfx] " Rob Clark 2022-04-07 22:59 ` Abhinav Kumar 2022-04-07 22:59 ` [Intel-gfx] " Abhinav Kumar 2022-04-07 23:12 ` Rob Clark 2022-04-07 23:12 ` [Intel-gfx] " Rob Clark 2022-04-09 4:04 ` Abhinav Kumar 2022-04-09 4:04 ` [Intel-gfx] " Abhinav Kumar 2022-04-12 23:36 ` Abhinav Kumar 2022-04-12 23:36 ` [Intel-gfx] " Abhinav Kumar 2022-04-13 11:20 ` Daniel Vetter 2022-04-13 11:20 ` [Intel-gfx] " Daniel Vetter 2022-04-28 8:08 ` Maxime Ripard 2022-04-28 8:08 ` Maxime Ripard 2022-04-28 12:09 ` Daniel Vetter 2022-04-28 12:09 ` [Intel-gfx] " Daniel Vetter 2022-05-12 8:08 ` Maxime Ripard [this message] 2022-05-12 8:08 ` Maxime Ripard 2022-09-26 15:06 ` Melissa Wen 2022-09-26 15:06 ` [Intel-gfx] " Melissa Wen 2022-04-07 7:49 ` Thomas Zimmermann 2022-04-07 7:49 ` Thomas Zimmermann 2022-04-07 9:30 ` Daniel Vetter 2022-04-07 9:30 ` [Intel-gfx] " Daniel Vetter 2022-04-07 12:32 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/atomic-helpers: remove legacy_cursor_update hacks (rev2) Patchwork 2022-04-07 13:04 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork 2022-04-07 18:35 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork -- strict thread matches above, loose matches on Subject: below -- 2023-02-16 11:12 [PATCH] drm/atomic-helpers: remove legacy_cursor_update hacks Daniel Vetter 2023-02-16 11:12 ` Daniel Vetter 2023-02-16 11:12 ` Daniel Vetter 2023-02-22 23:14 ` Rob Clark 2023-02-22 23:14 ` Rob Clark 2023-02-22 23:14 ` Rob Clark 2023-02-22 23:21 ` Rob Clark 2023-02-22 23:21 ` Rob Clark 2023-02-22 23:21 ` Rob Clark 2023-03-07 14:56 ` Maxime Ripard 2023-03-07 14:56 ` Maxime Ripard 2023-03-07 14:56 ` Maxime Ripard 2024-01-23 6:09 ` Jason-JH Lin (林睿祥) 2024-01-23 6:09 ` Jason-JH Lin (林睿祥) 2024-01-23 6:09 ` Jason-JH Lin (林睿祥) 2024-01-23 6:09 ` Jason-JH Lin (林睿祥) 2024-01-23 6:09 ` Jason-JH Lin (林睿祥) 2024-01-25 18:17 ` Daniel Vetter 2024-01-25 18:17 ` Daniel Vetter 2024-01-25 18:17 ` Daniel Vetter 2024-01-25 18:17 ` Daniel Vetter 2024-01-25 18:17 ` Daniel Vetter 2024-01-31 5:17 ` Jason-JH Lin (林睿祥) 2024-01-31 5:17 ` Jason-JH Lin (林睿祥) 2024-01-31 5:17 ` Jason-JH Lin (林睿祥) 2024-01-31 5:17 ` Jason-JH Lin (林睿祥) 2024-01-31 5:17 ` Jason-JH Lin (林睿祥) 2024-01-31 9:11 ` Daniel Vetter 2024-01-31 9:11 ` Daniel Vetter 2024-01-31 9:11 ` Daniel Vetter 2024-01-31 9:11 ` Daniel Vetter 2024-01-31 9:11 ` Daniel Vetter 2024-01-31 10:26 ` Dmitry Baryshkov 2024-01-31 10:26 ` Dmitry Baryshkov 2024-01-31 10:26 ` Dmitry Baryshkov 2024-01-31 11:28 ` Daniel Vetter 2024-01-31 11:28 ` Daniel Vetter 2024-01-31 11:28 ` Daniel Vetter 2024-01-31 11:28 ` Daniel Vetter 2024-01-31 11:28 ` Daniel Vetter 2020-10-21 16:32 [PATCH 1/3] " Daniel Vetter 2020-10-23 12:26 ` [PATCH] " Daniel Vetter
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220512080835.oy6cvqycgsfsjcly@houat \ --to=maxime@cerno.tech \ --cc=daniel.vetter@ffwll.ch \ --cc=daniel.vetter@intel.com \ --cc=daniel@ffwll.ch \ --cc=dmitry.osipenko@collabora.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=intel-gfx@lists.freedesktop.org \ --cc=michel@daenzer.net \ --cc=mikita.lipski@amd.com \ --cc=nicholas.kazlauskas@amd.com \ --cc=quic_abhinavk@quicinc.com \ --cc=quic_jesszhan@quicinc.com \ --cc=quic_kalyant@quicinc.com \ --cc=robdclark@chromium.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.