public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kristian Høgsberg" <krh@redhat.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Subject: Re: [PATCH 3/4] Add driver for OHCI firewire host controllers.
Date: Wed, 20 Dec 2006 13:10:52 -0500	[thread overview]
Message-ID: <45897CAC.1050905@redhat.com> (raw)
In-Reply-To: <4588BA0E.1080801@shaw.ca>

Robert Hancock wrote:
> Kristian Høgsberg wrote:
...
>> +static struct pci_driver fw_ohci_pci_driver = {
>> +    .name        = ohci_driver_name,
>> +    .id_table    = pci_table,
>> +    .probe        = pci_probe,
>> +    .remove        = pci_remove,
>> +};
> 
> How about suspend/resume support? Lots of laptops have OHCI 1394 and 
> full suspend/resume support is something that the current ohci1394 
> driver lacks.

Yes, good point, that needs to work too.  What I'm thinking here is that we 
need to turn off the link-on bit in the self ID packets we send out and then 
generate a bus reset before we suspend.  It shouldn't be necessary to change 
upper level drivers, the SBP-2 driver should just remaind logged in to the 
storage device.  When resuming, we re-enable the link-on bit and do a bus 
reset again, and should be back in operation.

Kristian



  parent reply	other threads:[~2006-12-20 18:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.4xX+iXSBwItlW4ONHWvAYR6m5+c@ifi.uio.no>
2006-12-20  4:20 ` [PATCH 3/4] Add driver for OHCI firewire host controllers Robert Hancock
2006-12-20  8:10   ` Stefan Richter
2006-12-20 18:10   ` Kristian Høgsberg [this message]
2006-12-20  0:58 Kristian Høgsberg

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=45897CAC.1050905@redhat.com \
    --to=krh@redhat.com \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /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