From: Jeff Garzik <jeff@garzik.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: "Rogério Brito" <rbrito@ime.usp.br>,
"Michael Tokarev" <mjt@tls.msk.ru>, "Mark Lord" <lkml@rtr.ca>,
linux-kernel@vger.kernel.org,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Subject: Re: Quick question about libata and hdparm
Date: Mon, 11 May 2009 14:34:55 -0400 [thread overview]
Message-ID: <4A086FCF.5090907@garzik.org> (raw)
In-Reply-To: <200904202231.25670.bzolnier@gmail.com>
Bartlomiej Zolnierkiewicz wrote:
> From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
> Subject: [PATCH] pata_pdc202xx_old: fix UDMA33 handling
>
> The original driver doesn't use 66 MHz clock for UDMA33.
>
> [ The alternative solution would be to adjust UDMA33 timings
> for 66 MHz clock but I think that it is safer to stick with
> old & tested behavior for now. ]
>
> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
> ---
> drivers/ata/pata_pdc202xx_old.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> Index: b/drivers/ata/pata_pdc202xx_old.c
> ===================================================================
> --- a/drivers/ata/pata_pdc202xx_old.c
> +++ b/drivers/ata/pata_pdc202xx_old.c
> @@ -2,7 +2,7 @@
> * pata_pdc202xx_old.c - Promise PDC202xx PATA for new ATA layer
> * (C) 2005 Red Hat Inc
> * Alan Cox <alan@lxorguk.ukuu.org.uk>
> - * (C) 2007 Bartlomiej Zolnierkiewicz
> + * (C) 2007,2009 Bartlomiej Zolnierkiewicz
> *
> * Based in part on linux/drivers/ide/pci/pdc202xx_old.c
> *
> @@ -158,7 +158,7 @@ static void pdc2026x_bmdma_start(struct
> u32 len;
>
> /* Check we keep host level locking here */
> - if (adev->dma_mode >= XFER_UDMA_2)
> + if (adev->dma_mode > XFER_UDMA_2)
> iowrite8(ioread8(clock) | sel66, clock);
> else
> iowrite8(ioread8(clock) & ~sel66, clock);
> @@ -212,7 +212,7 @@ static void pdc2026x_bmdma_stop(struct a
> iowrite8(ioread8(clock) & ~sel66, clock);
> }
> /* Flip back to 33Mhz for PIO */
> - if (adev->dma_mode >= XFER_UDMA_2)
> + if (adev->dma_mode > XFER_UDMA_2)
> iowrite8(ioread8(clock) & ~sel66, clock);
applied
next prev parent reply other threads:[~2009-05-11 18:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 0:22 Quick question about libata and hdparm Rogério Brito
2009-04-19 6:31 ` Robert Hancock
2009-04-19 12:33 ` Mark Lord
2009-04-19 12:44 ` Michael Tokarev
2009-04-19 12:57 ` Jeff Garzik
2009-04-19 13:06 ` Michael Tokarev
2009-04-19 20:11 ` Rogério Brito
2009-04-19 21:27 ` Jeff Garzik
2009-04-20 17:35 ` Rogério Brito
2009-04-20 18:40 ` Alan Cox
2009-04-20 20:41 ` Rogério Brito
2009-04-20 21:16 ` Alan Cox
2009-04-20 20:31 ` Bartlomiej Zolnierkiewicz
2009-04-20 20:45 ` Rogério Brito
2009-04-20 21:19 ` Alan Cox
2009-04-20 22:57 ` Rogério Brito
2009-04-21 5:32 ` Rogério Brito
2009-04-21 12:59 ` Bartlomiej Zolnierkiewicz
2009-04-23 5:56 ` Rogério Brito
2009-04-23 21:31 ` Bartlomiej Zolnierkiewicz
2009-04-24 3:00 ` Rogério Brito
2009-05-01 9:18 ` Rogério Brito
2009-05-01 10:31 ` Alan Cox
2009-05-01 11:50 ` Rogério Brito
2009-05-01 13:16 ` Alan Cox
2009-05-01 14:19 ` Rogério Brito
2009-05-01 11:20 ` Bartlomiej Zolnierkiewicz
2009-05-11 18:34 ` Jeff Garzik [this message]
2009-04-19 20:03 ` Rogério Brito
2009-04-19 23:41 ` Mark Lord
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=4A086FCF.5090907@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=mjt@tls.msk.ru \
--cc=rbrito@ime.usp.br \
/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