From: sashiko-bot@kernel.org
To: "Lyude Paul" <lyude@redhat.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v6 5/5] drm/nouveau/kms/nv50-: Enable atomic modesetting by default
Date: Thu, 13 Aug 2026 18:03:42 +0000 [thread overview]
Message-ID: <20260813180343.5F4E71F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260813174416.1812656-6-lyude@redhat.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The patch completely fails to enable atomic modesetting by default on nv50+ hardware and introduces a spurious warning on every boot for legacy hardware.
--
--- Patch [5]: [PATCH v6 5/5] drm/nouveau/kms/nv50-: Enable atomic modesetting by default ---
commit 72a6dbf310da7445e59ffec7fdf8ec40a1396882
Author: Lyude Paul <lyude@redhat.com>
drm/nouveau/kms/nv50-: Enable atomic modesetting by default
This commit aims to enable atomic modesetting by default on nv50+ hardware
while retaining a module parameter to turn it off if regressions occur.
> diff --git a/drivers/gpu/drm/nouveau/nouveau_drm.c b/drivers/gpu/drm/nouveau/nouveau_drm.c
> index 82a8061e6d3e2..8ee36c5d79fdb 100644
> --- a/drivers/gpu/drm/nouveau/nouveau_drm.c
> +++ b/drivers/gpu/drm/nouveau/nouveau_drm.c
> @@ -745,7 +745,7 @@ nouveau_drm_device_new(struct device *parent, struct nvkm_device *device)
> else
> driver = &driver_legacy_kms;
> } else {
> - if (nouveau_atomic)
> + if (nouveau_atomic != -1)
[Severity: Medium]
Does this inadvertently leave atomic modesetting disabled by default on
nv50+ hardware, and introduce a regression where spurious warnings are
printed on older hardware?
Looking at nouveau_drm_device_new(), the check above this else block for nv50+
hardware remains unmodified:
if (device->card_type >= NV_50) {
if (nouveau_atomic)
driver = &driver_atomic_kms;
else
driver = &driver_legacy_kms;
}
Since the module parameter nouveau_atomic remains initialized to 0, atomic
modesetting remains disabled by default on nv50+, which seems to defeat the
purpose described in the commit message.
Additionally, for pre-nv50 hardware, the modified condition
(nouveau_atomic != -1) now evaluates to true by default (0 != -1), which will
cause this dev_warn() to print spuriously on every boot.
> dev_warn(parent, "Atomic modesetting not supported (needs nv50+)\n");
>
> driver = &driver_legacy_kms;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260813174416.1812656-1-lyude@redhat.com?part=5
prev parent reply other threads:[~2026-08-13 18:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 17:42 [PATCH v6 0/5] drm/nouveau: Enable atomic modesetting by default Lyude Paul
2026-08-13 17:42 ` Lyude Paul
2026-08-13 17:42 ` [PATCH v6 1/5] drm/nouveau: Fix cleanup bug in nouveau_drm_device_new() Lyude Paul
2026-08-13 17:42 ` Lyude Paul
2026-08-13 17:42 ` [PATCH v6 2/5] drm/nouveau: Print the nouveau.atomic parameter in nouveau_display_options() Lyude Paul
2026-08-13 17:42 ` Lyude Paul
2026-08-13 17:42 ` [PATCH v6 3/5] drm/nouveau: Fix drm_driver struct/nouveau.atomic parameter handling Lyude Paul
2026-08-13 17:42 ` Lyude Paul
2026-08-13 17:42 ` [PATCH v6 4/5] drm/nouveau/kms: Only allow enabling atomic modesetting on nv50+ Lyude Paul
2026-08-13 17:42 ` Lyude Paul
2026-08-13 17:42 ` [PATCH v6 5/5] drm/nouveau/kms/nv50-: Enable atomic modesetting by default Lyude Paul
2026-08-13 17:42 ` Lyude Paul
2026-08-13 18:03 ` sashiko-bot [this message]
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=20260813180343.5F4E71F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=lyude@redhat.com \
--cc=sashiko-reviews@lists.linux.dev \
/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.