From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/sysfb: Support basic power management
Date: Sun, 12 Apr 2026 12:33:54 +1000 [thread overview]
Message-ID: <review-overall-20260408120722.328769-1-tzimmermann@suse.de> (raw)
In-Reply-To: <20260408120722.328769-1-tzimmermann@suse.de>
Overall Series Review
Subject: drm/sysfb: Support basic power management
Author: Thomas Zimmermann <tzimmermann@suse.de>
Patches: 6
Reviewed: 2026-04-12T12:33:54.714983
---
This is a clean, straightforward 5-patch series by Thomas Zimmermann adding basic PM (suspend/resume) support to all five sysfb DRM drivers: corebootdrm, efidrm, ofdrm, simpledrm, and vesadrm.
Each patch follows an identical pattern: add PM callbacks that call `drm_mode_config_helper_suspend()`/`drm_mode_config_helper_resume()`, wire them up via `DEFINE_SIMPLE_DEV_PM_OPS` and `pm_sleep_ptr()`. The approach is correct -- all five drivers use `DRIVER_ATOMIC` and set up `mode_config_funcs` with `drm_atomic_helper_commit`, which is required for the config helper suspend/resume to work.
I verified that `dev_get_drvdata()` retrieval in each PM callback matches what each driver's probe function stores via `platform_set_drvdata()`. The series is correct.
**One design observation:** All five patches are nearly identical boilerplate. Since every sysfb driver embeds a `struct drm_sysfb_device` (which embeds `struct drm_device`), shared PM ops could be factored into `drm_sysfb_helper.h`, avoiding ~20 lines of duplication in each driver. The blocker is that drvdata is inconsistent across the drivers: corebootdrm and simpledrm store their outer device struct, while efidrm, ofdrm, and vesadrm store the `struct drm_device *` directly. Standardizing the drvdata convention would enable a single shared `drm_sysfb_pm_ops`. This is a nice-to-have, not a blocker.
**Verdict:** Series looks good.
---
---
Generated by Claude Code Patch Reviewer
prev parent reply other threads:[~2026-04-12 2:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 12:03 [PATCH 0/5] drm/sysfb: Support basic power management Thomas Zimmermann
2026-04-08 12:03 ` [PATCH 1/5] drm/sysfb: corebootdrm: Support " Thomas Zimmermann
2026-04-12 2:33 ` Claude review: " Claude Code Review Bot
2026-04-08 12:03 ` [PATCH 2/5] drm/sysfb: efidrm: " Thomas Zimmermann
2026-04-12 2:33 ` Claude review: " Claude Code Review Bot
2026-04-08 12:03 ` [PATCH 3/5] drm/sysfb: ofdrm: " Thomas Zimmermann
2026-04-12 2:33 ` Claude review: " Claude Code Review Bot
2026-04-08 12:03 ` [PATCH 4/5] drm/sysfb: simpledrm: " Thomas Zimmermann
2026-04-12 2:33 ` Claude review: " Claude Code Review Bot
2026-04-08 12:03 ` [PATCH 5/5] drm/sysfb: vesadrm: " Thomas Zimmermann
2026-04-12 2:33 ` Claude review: " Claude Code Review Bot
2026-04-12 2:33 ` Claude Code Review 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=review-overall-20260408120722.328769-1-tzimmermann@suse.de \
--to=claude-review@example.com \
--cc=dri-devel-reviews@example.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox