From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linuxppc-dev@ozlabs.org, linux1394-devel@lists.sourceforge.net,
Bernhard Kaindl <bk@fsfe.org>, Pavel Machek <pavel@ucw.cz>
Subject: Re: [Fwd: Re: ohci1394: steps to implement suspend/resume]
Date: Thu, 07 Sep 2006 10:53:36 +1000 [thread overview]
Message-ID: <1157590416.22705.269.camel@localhost.localdomain> (raw)
In-Reply-To: <44FEDF5D.9060707@s5r6.in-berlin.de>
On Wed, 2006-09-06 at 16:46 +0200, Stefan Richter wrote:
> Hello LinuxPPC-dev,
>
> we have now patches coming in to fix up the lack of generic suspend +
> resume support in drivers/ieee1394/ohci1394. Attached is the latest and
> by far most functional one by Bernhard Kaindl. A big question is how
> this relates to the already existing PPC-PMAC platform code in
> ohci1394's suspend and resume hooks.
>
> - Which functionalities does the existing platform code provide in
> detail?
>
> - Do we have to keep platform code and generic code separate? I.e.
> #ifdef CONFIG_PPC_PMAC
> ...pmac_call_feature...
> #else
> ...new generic code...
> #endif
>
> - Or are parts of the until now missing, new generic code necessary
> for PMacs too? If yes, is the platform code treated to be the lowest
> level as far as the oreder of code is concerned?
>
> - Or would the platform code be obsolete?
>
> We already broke your platform code once by what was meant as a bugfix
> for non-PMacs. It'd be good to know enough to not repeat such mistakes...
The PowerMac code will stop the chip clocks. It should be used as the
last step of the suspend sequence and first step of the return sequence,
in _addition_ to your new code. Note also that the code you posted lacks
calls to pci_set_power_state()...
Ben.
next prev parent reply other threads:[~2006-09-07 0:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 14:46 [Fwd: Re: ohci1394: steps to implement suspend/resume] Stefan Richter
2006-09-07 0:53 ` Benjamin Herrenschmidt [this message]
2006-09-07 19:34 ` Stefan Richter
2006-09-07 23:30 ` Benjamin Herrenschmidt
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=1157590416.22705.269.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=bk@fsfe.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=pavel@ucw.cz \
--cc=stefanr@s5r6.in-berlin.de \
/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;
as well as URLs for NNTP newsgroup(s).