All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	jeff@garzik.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH 7/7] libata: Add 32bit PIO support
Date: Tue, 06 Jan 2009 15:47:37 +0300	[thread overview]
Message-ID: <496352E9.9030101@ru.mvista.com> (raw)
In-Reply-To: <4962AE92.5060401@shaw.ca>

Hello.

Robert Hancock wrote:

>> This matters for some controllers and in one or two cases almost doubles
>> PIO performance. Add a bmdma32 operations set we can inherit and 
>> activate
>> it for some controllers
>>
>> Signed-off-by: Alan Cox <alan@redhat.com>
>> ---
>>
>>  drivers/ata/ata_piix.c    |    2 +-
>>  drivers/ata/libata-sff.c  |   53 
>> +++++++++++++++++++++++++++++++++++++++++++++
>>  drivers/ata/pata_ali.c    |    6 +++--
>>  drivers/ata/pata_amd.c    |    4 ++-
>>  drivers/ata/pata_mpiix.c  |    3 ++-
>>  drivers/ata/pata_sil680.c |    4 ++-
>>  include/linux/libata.h    |    3 +++
>>  7 files changed, 66 insertions(+), 9 deletions(-)
>
> This can likely be enabled for more controllers (presumably all the 
> SFF-based SATA controllers as well as any other PATA that couldn't be 
> on a physical ISA bus).

   Why are you so sure? Some controllers only support 32-bit accesses 
when prefetch is enabled, some may not support it at all...

> This is a start though.
>
> Don't some of the VLB controller drivers have their own private 32-bit 
> PIO implementation? Those should likely be updated to use this support.

   You mean sequence of 3 reads of some non-datra register?

MBR, Sergei



  parent reply	other threads:[~2009-01-06 12:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05 14:12 [PATCH 0/7] ata: Updates and improvements Alan Cox
2009-01-05 14:12 ` [PATCH 1/7] pata_hpt3x3: Workarounds for chipset Alan Cox
2009-01-05 14:13 ` [PATCH 2/7] pata_ali: force initialise a few bits Alan Cox
2009-01-05 14:13 ` [PATCH 3/7] pata_ali: Fix and workaround for FIFO DMA bug Alan Cox
2009-01-05 14:15 ` [PATCH 4/7] libata: Drain data on errors Alan Cox
2009-01-05 14:16 ` [PATCH 5/7] libata: Improve timeout handling Alan Cox
2009-01-07  0:29   ` Robert Hancock
2009-01-05 14:16 ` [PATCH 6/7] libata: clean up the SFF code for coding style Alan Cox
2009-01-05 14:16 ` [PATCH 7/7] libata: Add 32bit PIO support Alan Cox
2009-01-06  1:06   ` Robert Hancock
2009-01-06  9:46     ` Alan Cox
2009-01-06 12:47     ` Sergei Shtylyov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-05 19:42 [PATCH 1/7] pata_ninja32: update ID table Alan Cox
2008-12-05 19:44 ` [PATCH 7/7] libata: Add 32bit PIO support Alan Cox
2008-12-05 20:16   ` Elias Oltmanns
2008-12-06  0:25     ` 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=496352E9.9030101@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hancockr@shaw.ca \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.