From: Russell King <rmk+lkml@arm.linux.org.uk>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Len Brown <lenb@kernel.org>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
pm list <linux-pm@lists.linux-foundation.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: 900af0d breaks some embedded suspend/resume
Date: Sat, 18 Apr 2009 15:28:07 +0100 [thread overview]
Message-ID: <20090418142807.GB7148@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200904181559.19485.rjw@sisk.pl>
On Sat, Apr 18, 2009 at 03:59:18PM +0200, Rafael J. Wysocki wrote:
> On Saturday 18 April 2009, Rafael J. Wysocki wrote:
> > On Saturday 18 April 2009, Russell King wrote:
> > > Some platforms need to talk via I2C to power control devices during
> > > the suspend method. Currently, they do this via the platform PM ops
> > > prepare callback, relying on the I2C driver being hooked into the
> > > 'late' suspend method, and hence being shut down _after_ the prepare
> > > callback.
> >
> > Well, I was not aware of this dependency and it seems quite unusual for a
> > platform to depend on a driver like this.
> >
> > > However, as of the above commit, the ordering is changed such that
> > > platforms don't get notified of suspends until after all devices are
> > > well and truely shut down.
> > >
> > > This can't work, and actively breaks some platforms.
> >
> > Sorry for that.
> >
> > The patchset in question had been discussed quite extensively before it was
> > merged and it's a pity none of the people caring for the affected platforms
> > took part in those discussions. That would allow us to avoid the breakage.
> >
> > > Please come up with another solution for your PCI problems,
> >
> > I don't think this is possible, sorry.
> >
> > > or provide alternative equivalent functionality where the platform code is
> > > notified of the PM event prior to the late suspend callback being issued.
> >
> > There is the .begin() callback that could be used, but if you need the
> > platform to be notified _just_ prior to the late suspend callback, then the
> > only thing I can think of at the moment is the appended patch.
> >
> > It shouldn't break anything in theory, because the majority of drivers put
> > their devices into low power states in the "regular" suspend callbacks anyway.
>
> Still, if it turns out to break anything, we'll have to think of an alternative
> approach.
>
> Which platforms exactly are affected?
The one I've maintained since 2.6.9 and am just sending out the initial
bits for final review.
(It's taking a long time to get it out there because I can only spend
very little time on it, and it keeps getting broken - ALSA, SCSI and
now PM have all broken it in the last couple of months.)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
prev parent reply other threads:[~2009-04-18 14:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090417231009.GB6900@flint.arm.linux.org.uk>
2009-04-18 13:23 ` 900af0d breaks some embedded suspend/resume Rafael J. Wysocki
2009-04-18 13:53 ` Russell King
2009-04-18 14:26 ` Rafael J. Wysocki
2009-04-18 14:41 ` Russell King
2009-04-18 15:09 ` Rafael J. Wysocki
2009-04-18 18:09 ` Russell King
2009-04-18 18:47 ` [PATCH] PM/Suspend: Introduce two new platform callbacks to avoid breakage (Re: 900af0d breaks some embedded suspend/resume) Rafael J. Wysocki
2009-04-19 17:57 ` Len Brown
2009-04-19 20:03 ` Russell King
2009-04-20 0:50 ` Rafael J. Wysocki
2009-04-20 0:56 ` [GIT PULL] PM update for 2.6.30 Rafael J. Wysocki
2009-04-19 23:31 ` [PATCH] PM/Suspend: Introduce two new platform callbacks to avoid breakage (Re: 900af0d breaks some embedded suspend/resume) Nigel Cunningham
2009-04-20 0:50 ` Rafael J. Wysocki
2009-04-20 8:35 ` Russell King
2009-04-20 8:48 ` Nigel Cunningham
2009-04-18 14:42 ` 900af0d breaks some embedded suspend/resume Rafael J. Wysocki
2009-04-18 19:06 ` Linus Torvalds
2009-04-18 22:44 ` Rafael J. Wysocki
2009-04-26 9:25 ` Pavel Machek
2009-04-18 13:59 ` Rafael J. Wysocki
2009-04-18 14:28 ` Russell King [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=20090418142807.GB7148@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.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