All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "David Müller" <dave.mueller@gmx.ch>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: Fix a large collection of DMA mode mismatches
Date: Fri, 22 Aug 2008 02:28:09 -0400	[thread overview]
Message-ID: <48AE5C79.8090101@pobox.com> (raw)
In-Reply-To: <20080801091834.5ca39334@lxorguk.ukuu.org.uk>

Alan Cox wrote:
> From: Alan Cox <alan@redhat.com>
> 
> Dave Müller sent a diff for the pata_oldpiix that highlighted a problem
> where a lot of the ATA drivers assume dma_mode == 0 means "no DMA" while
> the core code uses 0xFF.
> 
> This turns out to have other consequences such as code doing >= XFER_UDMA_0
> also catching 0xFF as UDMAlots. Fortunately it doesn't generally affect
> set_dma_mode, although some drivers call back into their own set mode code
> from other points.
> 
> Having been through the drivers I've added helpers for using_udma/using_mwdma
> dma_enabled so that people don't open code ranges that may change (eg if UDMA8
> appears somewhere)
> 
> Thanks to David for the initial bits
> 
> Signed-off-by: Alan Cox <alan@redhat.com>
> ---
> 
>  drivers/ata/libata-core.c |    4 ++--
>  drivers/ata/pata_acpi.c   |    2 +-
>  drivers/ata/pata_atiixp.c |    2 +-
>  drivers/ata/pata_cs5530.c |    6 +++---
>  drivers/ata/pata_sc1200.c |    6 +++---
>  include/linux/libata.h    |   22 ++++++++++++++++++++++
>  6 files changed, 32 insertions(+), 10 deletions(-)

applied (w/ David's pata_oldpiix update)



      parent reply	other threads:[~2008-08-22  6:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01  8:18 [PATCH] libata: Fix a large collection of DMA mode mismatches Alan Cox
2008-08-01 11:56 ` David Müller
2008-08-01 22:42   ` Alan Cox
2008-08-03  4:45 ` Tejun Heo
2008-08-03 13:08   ` Alan Cox
2008-08-03 14:02     ` Tejun Heo
2008-08-22  6:28 ` Jeff Garzik [this message]

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=48AE5C79.8090101@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dave.mueller@gmx.ch \
    --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.