From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jason Lunz <lunz@falooley.org>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@ucw.cz>,
Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: [PATCH] amd74xx: implement suspend-to-ram
Date: Tue, 01 Aug 2006 09:18:26 +0200 [thread overview]
Message-ID: <1154416706.21801.53.camel@localhost.localdomain> (raw)
In-Reply-To: <1154116826.13509.160.camel@localhost.localdomain>
On Fri, 2006-07-28 at 21:00 +0100, Alan Cox wrote:
> Ar Gwe, 2006-07-28 am 13:13 -0400, ysgrifennodd Jason Lunz:
> > OK, I'll see about moving it there. Will this still be
> > controller-specific, or are you suggesting this is something ide ought
> > to do globally?
>
> It should be done globally. In many cases the chips start up from power
> on configured for PIO 0 so that side happens to work, but not all chips
> do this as you've found out. Setting the PIO side correctly is a fix
> even if its not a bug people hit a lot.
It's actually incorrect to just "restore" the previous timings. In many
case, the disk will have been reset too. The safe thing is to force the
controller in PIO0 mode at resume, and the best place to do that is from
the controller's own resume(), as I do on pmac. It's the parent of the
hwif and thus will be resumed before the later.
Later on, the state machine will redo the tuning to get to a better
speed, including sending the right commands to also reconfigure the
drive.
Ben.
next prev parent reply other threads:[~2006-08-07 13:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 14:46 [PATCH] amd74xx: implement suspend-to-ram Rafael J. Wysocki
2006-07-28 16:51 ` Alan Cox
2006-07-28 17:13 ` Jason Lunz
2006-07-28 19:16 ` Brad Campbell
2006-07-28 20:00 ` Alan Cox
2006-08-01 7:18 ` Benjamin Herrenschmidt [this message]
2006-07-29 23:34 ` [patch, rft] ide: reprogram disk pio timings on resume Jason Lunz
2006-07-30 3:25 ` Brad Campbell
2006-07-30 17:26 ` Alan Cox
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=1154416706.21801.53.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lunz@falooley.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=vojtech@suse.cz \
/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