From: Lukas Wunner <lukas@wunner.de>
To: Aditya Garg <aditya.garg@linux.dev>
Cc: vasilij.kernel@tototo.si, Aun-Ali Zaidi <admin@kodeit.net>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Kerem Karabay <kekrby@gmail.com>,
Atharva Tiwari <atharvatiwarilinuxdev@gmail.com>
Subject: Re: [PATCH v2] drm/appletbdrm: Add suspend and resume support
Date: Thu, 15 Oct 2026 22:26:15 +0200 [thread overview]
Message-ID: <atE25_ZrIQct41wt@wunner.de> (raw)
In-Reply-To: <E1AEF567-3705-4AE7-B409-6E6D70C505AC@linux.dev>
On Wed, Oct 07, 2026 at 07:50:38PM +0530, Aditya Garg wrote:
> > On 4 Oct 2026, at 5:36???PM, Aditya Garg <aditya.garg@linux.dev> wrote:
> > The driver has no USB power management callbacks, so the USB core
> > unbinds it before system suspend and binds it again on resume. The DRM
> > device is unregistered and registered again on every suspend and resume
> > cycle, userspace driving the Touch Bar through it (such as tiny-dfr)
> > loses its device, and the Touch Bar stays dark after resume.
> >
> > Implement suspend and resume with drm_mode_config_helper_suspend() and
> > drm_mode_config_helper_resume(), so the device stays registered and the
> > last committed state is restored on resume. If the device was reset
> > while suspended, repeat the probe-time handshake first.
[...]
> Could anyone please merge it if they are ok with it? Thanks.
I'd love to, but both v1 and v2 have sashiko findings that nobody bothered
to debunk or fix. (The fix for v1 consisted of removing a callback, which
triggered other sashiko findings.) I'm neither an expert on this driver
nor the tiny drm library, but I'd like to help improve Linux Mac support.
Please help me understand whether the sashiko findings are valid.
Thanks,
Lukas
next prev parent reply other threads:[~2026-10-15 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 19:25 [PATCH] " Vasilij Markin via B4 Relay
2026-09-25 11:51 ` Aditya Garg
2026-10-04 12:06 ` [PATCH v2] " Aditya Garg
2026-10-07 14:20 ` Aditya Garg
2026-10-15 20:26 ` Lukas Wunner [this message]
2026-10-15 22:13 ` Vasilij
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=atE25_ZrIQct41wt@wunner.de \
--to=lukas@wunner.de \
--cc=aditya.garg@linux.dev \
--cc=admin@kodeit.net \
--cc=airlied@gmail.com \
--cc=atharvatiwarilinuxdev@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kekrby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=vasilij.kernel@tototo.si \
/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
all inboxes | Powered by JetHome®