From: Lee Jones <lee@kernel.org>
To: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
Cc: Mark Rutland <mark.rutland@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: (subset) [PATCH 0/4] power: sys-off: fix Pixel C shutdown via MAX77620
Date: Thu, 21 May 2026 17:24:36 +0100 [thread overview]
Message-ID: <20260521162436.GG3591266@google.com> (raw)
In-Reply-To: <f98bcd81-29c6-4df2-8040-d17686b28f45@tecnico.ulisboa.pt>
On Thu, 21 May 2026, Diogo Ivo wrote:
>
>
> On 5/21/26 12:41, Lee Jones wrote:
> > On Thu, 21 May 2026, Diogo Ivo wrote:
> >
> > > Hi Lee,
> > >
> > > On 5/20/26 18:25, Lee Jones wrote:
> > > > On Thu, 14 May 2026 16:47:18 +0200, Diogo Ivo wrote:
> > > > > This series migrates PSCI and MAX77620 poweroff handling to the
> > > > > sys-off framework and fixes shutdown on the Pixel C (Smaug).
> > > > >
> > > > > The first two patches replace legacy pm_power_off usage in the PSCI
> > > > > and MAX77620 drivers with sys-off handlers. Besides aligning both
> > > > > drivers with the modern poweroff infrastructure, this removes the
> > > > > global callback dependency and allows multiple handlers to coexist
> > > > > with explicit priorities.
> > > > >
> > > > > [...]
> > > >
> > > > Applied, thanks!
> > >
> > > Thanks for applying the patches! Just a question and an observation:
> > >
> > > - I'm assuming you were ok with merging [2/4] despite the possible
> > > deadlock since this risk is already present in mainline in the same
> > > form so we're not actually making things worse, is that so?
> >
> > Did you see the text below?
>
> Yes, but patch 3 is not addressing the possible deadlock hence my
> question.
>
> > Both patches 2 and 3 are applied.
> >
> > > - The observation is that the comment about overriding PSCI is only
> > > true after (and if) a reworked [1/4] is actually merged.
> > > If it isn't then patch [3/4] is actually working around another handler
> > > in soc/tegra/pmc.c where a handler that only does work for the Nexus
> > > 7 is actually registered at FIRMWARE level for all platforms that
> > > probe that driver (I will send out a patch shortly to only register
> > > the handler on the Nexus 7).
> >
> > I assume the other patches will be applied soon.
> >
> > If this causes some kind of issue - let me know later on in the cycle
> > and I'll remove whatever patches you ask me to.
>
> The PSCI patch [1/4] has a fundamental issue and needs a respin to be
> applied.
>
> In connection with this it might then become easier to quirk the PSCI
> driver rather than the PMIC driver, so for the moment I'll ask you to
> drop [3/4] until I propose the changes to the PSCI maintainers and see
> the feedback and at that point we can either completely drop [3/4] or
> reapply it; sorry for the noise.
Done.
--
Lee Jones
prev parent reply other threads:[~2026-05-21 16:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 14:47 [PATCH 0/4] power: sys-off: fix Pixel C shutdown via MAX77620 Diogo Ivo
2026-05-14 14:47 ` [PATCH 1/4] firmware: psci: switch SYSTEM_OFF to sys-off handler API Diogo Ivo
2026-05-14 14:47 ` [PATCH 2/4] mfd: max77620: convert poweroff support to sys-off API Diogo Ivo
2026-05-14 14:47 ` [PATCH 3/4] mfd: max77620: override PSCI poweroff handler on Pixel C Diogo Ivo
2026-05-21 7:52 ` Thierry Reding
2026-05-21 9:23 ` Diogo Ivo
2026-05-21 9:43 ` Thierry Reding
2026-05-21 9:49 ` Diogo Ivo
2026-05-14 14:47 ` [PATCH 4/4] arm64: tegra: smaug: mark MAX77620 as system power controller Diogo Ivo
2026-05-20 16:25 ` (subset) [PATCH 0/4] power: sys-off: fix Pixel C shutdown via MAX77620 Lee Jones
2026-05-21 9:47 ` Diogo Ivo
2026-05-21 10:41 ` Lee Jones
2026-05-21 13:59 ` Diogo Ivo
2026-05-21 16:24 ` Lee Jones [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=20260521162436.GG3591266@google.com \
--to=lee@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=diogo.ivo@tecnico.ulisboa.pt \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=thierry.reding@kernel.org \
/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