From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Russell King <rmk+lkml@arm.linux.org.uk>,
Len Brown <lenb@kernel.org>,
Linux Kernel List <linux-kernel@vger.kernel.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: Sun, 26 Apr 2009 11:25:51 +0200 [thread overview]
Message-ID: <20090426092550.GB1354@ucw.cz> (raw)
In-Reply-To: <200904190044.58444.rjw@sisk.pl>
On Sun 2009-04-19 00:44:57, Rafael J. Wysocki wrote:
> On Saturday 18 April 2009, Linus Torvalds wrote:
> >
> > On Sat, 18 Apr 2009, Russell King wrote:
> > >
> > > What I need to be able to do is to suspend most devices on the host side
> > > which may involve talking to a separate microcontroller via I2C to shut
> > > down power to peripherals.
> >
> > I suspect that for cases like this, the simplest thing to do is to just
> > add a marker for "don't mess with my power management, I'm doing
> > everything through sysdev" for the specified devices.
>
> In this particular case, if sysdev was used, there would be no problem, but the
> platform uses a platform device to suspend-resume the i2c controller.
> In principle we could convert it to use a sysdev, but that would be more
> difficult than the last patch I sent IMO (at least to me).
>
> Also, apparently it is not the only platform doing it.
OTOH... if the device is needed in late phases of sleep, sysdev *does*
sound like a way to go. So it would be nice to convert those devices
to sysdevs one day.....
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-04-28 20:27 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 [this message]
2009-04-18 13:59 ` Rafael J. Wysocki
2009-04-18 14:28 ` Russell King
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=20090426092550.GB1354@ucw.cz \
--to=pavel@ucw.cz \
--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=rmk+lkml@arm.linux.org.uk \
--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