From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ CI.checkpatch: warning for series starting with [CI,1/3] drm: Add drm_vblank_work_flush_all().
Date: Fri, 02 Feb 2024 16:28:39 -0000 [thread overview]
Message-ID: <170689131940.952961.11583300168938869495@5338d5abeb45> (raw)
In-Reply-To: <20240202154423.834991-1-maarten.lankhorst@linux.intel.com>
== Series Details ==
Series: series starting with [CI,1/3] drm: Add drm_vblank_work_flush_all().
URL : https://patchwork.freedesktop.org/series/129477/
State : warning
== Summary ==
+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
35591fb8b4d5305b37ce31483f85ac0956eaa536
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 71a674695131baf7132cc227489e63f8f3f75e4b
Author: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Date: Fri Feb 2 16:44:23 2024 +0100
drm/i915: Use the same vblank worker for atomic unpin
In case of legacy cursor update, the cursor VMA needs to be unpinned
only after vblank. This exceeds the lifetime of the whole atomic commit.
Any trick I attempted to keep the atomic commit alive didn't work, as
drm_atomic_helper_setup_commit() force throttles on any old commit that
wasn't cleaned up.
The only option remaining is to remove the plane from the atomic commit,
and use the same path as the legacy cursor update to clean the state
after vblank.
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
+ /mt/dim checkpatch 1dd92467500a5ead3e44bbdfe15e064dd79b65ef drm-intel
ce4163e35 drm: Add drm_vblank_work_flush_all().
-:33: WARNING:WAITQUEUE_ACTIVE: waitqueue_active without comment
#33: FILE: drivers/gpu/drm/drm_vblank_work.c:249:
+ waitqueue_active(&vblank->work_wait_queue),
total: 0 errors, 1 warnings, 0 checks, 41 lines checked
17949a6b5 drm/i915: Use vblank worker to unpin old legacy cursor fb safely
71a674695 drm/i915: Use the same vblank worker for atomic unpin
-:37: WARNING:TYPO_SPELLING: 'succesful' may be misspelled - perhaps 'successful'?
#37: FILE: drivers/gpu/drm/i915/display/intel_atomic_plane.c:1168:
+ * This branch can only ever be called after plane update is succesful,
^^^^^^^^^
-:118: WARNING:LONG_LINE: line length of 105 exceeds 100 columns
#118: FILE: drivers/gpu/drm/i915/display/intel_crtc.c:641:
+ drm_crtc_accurate_vblank_count(&crtc->base) + 1,
total: 0 errors, 2 warnings, 0 checks, 110 lines checked
next prev parent reply other threads:[~2024-02-02 16:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 15:44 [CI 1/3] drm: Add drm_vblank_work_flush_all() Maarten Lankhorst
2024-02-02 15:44 ` [CI 2/3] drm/i915: Use vblank worker to unpin old legacy cursor fb safely Maarten Lankhorst
2024-02-02 15:44 ` [CI 3/3] drm/i915: Use the same vblank worker for atomic unpin Maarten Lankhorst
2024-02-02 16:28 ` ✓ CI.Patch_applied: success for series starting with [CI,1/3] drm: Add drm_vblank_work_flush_all() Patchwork
2024-02-02 16:28 ` Patchwork [this message]
2024-02-02 16:29 ` ✓ CI.KUnit: " Patchwork
2024-02-02 16:36 ` ✓ CI.Build: " Patchwork
2024-02-02 16:37 ` ✓ CI.Hooks: " Patchwork
2024-02-02 16:38 ` ✗ CI.checksparse: warning " Patchwork
2024-02-02 17:01 ` ✓ CI.BAT: success " Patchwork
2024-02-02 19:30 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2024-02-02 19:30 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-02-02 19:42 ` ✓ Fi.CI.BAT: success " Patchwork
2024-02-02 21:10 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-04-03 9:51 ` ✗ Fi.CI.BUILD: failure for series starting with [CI,1/3] drm: Add drm_vblank_work_flush_all(). (rev2) Patchwork
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=170689131940.952961.11583300168938869495@5338d5abeb45 \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
/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: link
Be 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.