[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250416220406.GB8400@robin.jannau.net>
Date: Thu, 17 Apr 2025 00:04:06 +0200
From: Janne Grunau <j@...nau.net>
To: Alyssa Rosenzweig <alyssa@...enzweig.io>
Cc: Sasha Finkelstein <fnkl.kernel@...il.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...il.com>, Simona Vetter <simona@...ll.ch>,
Neal Gompa <neal@...pa.dev>, Dmitry Baryshkov <lumag@...nel.org>,
dri-devel@...ts.freedesktop.org, asahi@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] Apple Display Pipe driver fixes
On Wed, Apr 16, 2025 at 04:54:38PM -0400, Alyssa Rosenzweig wrote:
> > This is preferable to driver changes since keeps the device powered on
> > if the adpdrm module is not available during boot.
>
> Struggling to parse this sentence, do you mean to say:
>
> > Driver changes are preferred, since that patch keeps the device
> > powered on if the adpdrm module is not available during boot.
no. The sentence misses "it" between "since" and "keeps". I meant to say
that the linked devicetree change is preferable. A hypothetical
adp_drv.c change to keep the power-domain during s2idle only works if
the driver is loaded.
The changes in this series (especially Patch 1/4) just prevent the
soft-locked CPU after resume. The touch bar display won't display
anything.
Janne
Powered by blists - more mailing lists