LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Tobias Diedrich <ranma+kernel@tdiedrich.de>,
	Linux Kernel ML <linux-kernel@vger.kernel.org>,
	linux-ide@vger.kernel.org, Alan <alan@lxorguk.ukuu.org.uk>
Subject: Re: pata_amd dropping to PIO on resume
Date: Fri, 16 Feb 2007 18:51:08 -0500	[thread overview]
Message-ID: <45D6436C.4060209@garzik.org> (raw)
In-Reply-To: <45D63BCE.2080700@shaw.ca>

Robert Hancock wrote:
> Tobias Diedrich wrote:
>> Possibly a known issue:
>>
>> After resume pata_amd drops from UDMA/33 to PIO on my system.
>> Reloading the module puts both attached optical drives (master and
>> slave) back to UDMA/33.
>>
>> AFAICS "simplex DMA is claimed by other device, disabling DMA" seems
>> to be causing it to drop to PIO (but only after a suspend/resume
>> cycle, not on boot or module load).
>>
>> Burning a DVD with 6x speed using PIO makes heavy use of burnproof
>> and makes the whole system quite sluggish. :)
> 
> Yes, the fact that it's going into simplex mode is the problem, it 
> wasn't in simplex to start with. It looks like pata_amd does an 
> ata_pci_clear_simplex only for certain chip models, maybe this model 
> needs it as well?
> 

Deleting the ata_pci_clear_simplex() call, then adding 
ATA_FLAG_IGN_SIMPLEX to the ata_port_info info[] array, is also worth 
trying.

	Jeff



  reply	other threads:[~2007-02-16 23:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.q7ZuddHInqn2dVlS+EWjXjPvFC8@ifi.uio.no>
2007-02-16 23:18 ` Robert Hancock
2007-02-16 23:51   ` Jeff Garzik [this message]
2007-02-17  9:49     ` Tobias Diedrich
2007-02-19 22:08     ` Alan
2007-02-20 15:27       ` Jeff Garzik
2007-02-20 16:42         ` Alan
2007-02-16 16:21 Tobias Diedrich

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=45D6436C.4060209@garzik.org \
    --to=jeff@garzik.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hancockr@shaw.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ranma+kernel@tdiedrich.de \
    --subject='Re: pata_amd dropping to PIO on resume' \
    /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

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).