[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171013164235.thgqha7sl5tdptwv@sirena.co.uk>
Date: Fri, 13 Oct 2017 17:42:35 +0100
From: Mark Brown <broonie@...nel.org>
To: Brian Norris <briannorris@...omium.org>
Cc: Doug Anderson <dianders@...omium.org>,
Jeffy Chen <jeffy.chen@...k-chips.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Heiko Stuebner <heiko@...ech.de>,
linux-spi <linux-spi@...r.kernel.org>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>
Subject: Re: [RESEND PATCH 1/2] spi: rockchip: Convert to late and early
system PM callbacks
On Fri, Oct 13, 2017 at 08:51:21AM -0700, Brian Norris wrote:
> Yes, this does seem odd to me too. This looks like an arms race hack
> that should be avoided unless we know a legit root cause. Also,
> "probe order implies suspend order" doesn't quite work for async suspend
> anyway, so we'd probably want to express the dependency properly
> anyway.
Yeah, it's the same stuff as we get with initcall ordering. This sort
of thing does happen with things like PMICs which tend to have hardware
that the system wants to manipulate in the IRQs off part of suspend.
Ideally the dependency annotation stuff would figure things out though
I'm not sure what the status of that is.
> Any chance this is related? Seems like that might break the parent/child
> relationship for master/slave:
> commit d7e2ee257038baeb03baef602500368a51ee9eef
> Author: Linus Walleij <linus.walleij@...aro.org>
> Date: Mon Apr 11 13:51:03 2016 +0200
> spi: let SPI masters ignore their children for PM
That's for runtime PM, I'd not expect it to affect system suspend.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists