From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Bob Ham <rah@bash.sh>, linux-ide@vger.kernel.org
Subject: Re: hpt374 sata (Highpoint Rocket 1540)
Date: Wed, 1 Aug 2007 23:07:59 +0200 [thread overview]
Message-ID: <200708012308.00057.bzolnier@gmail.com> (raw)
In-Reply-To: <46B08D63.4040205@ru.mvista.com>
Hi,
On Wednesday 01 August 2007, Sergei Shtylyov wrote:
> > Does this patch change anything?
>
> Heh, did you *really* hope it will? :-D
Well, ugh, yes? :)
> > [PATCH] hpt366: always tune PIO
>
> > Index: b/drivers/ide/pci/hpt366.c
> > ===================================================================
> > --- a/drivers/ide/pci/hpt366.c
> > +++ b/drivers/ide/pci/hpt366.c
> > @@ -1,5 +1,5 @@
> > /*
> > - * linux/drivers/ide/pci/hpt366.c Version 1.10 Jun 29, 2007
> > + * linux/drivers/ide/pci/hpt366.c Version 1.11 Jul 29, 2007
> > *
> > * Copyright (C) 1999-2003 Andre Hedrick <andre@linux-ide.org>
> > * Portions Copyright (C) 2001 Sun Microsystems, Inc.
> > @@ -1265,10 +1265,10 @@ static void __devinit init_hwif_hpt366(i
> > if (new_mcr != old_mcr)
> > pci_write_config_byte(dev, hwif->select_data + 1, new_mcr);
> >
> > - if (!hwif->dma_base) {
> > - hwif->drives[0].autotune = hwif->drives[1].autotune = 1;
> > + hwif->drives[0].autotune = hwif->drives[1].autotune = 1;
> > +
> > + if (hwif->dma_base == 0)
> > return;
> > - }
> >
> > hwif->ultra_mask = hwif->cds->udma_mask;
> > hwif->mwdma_mask = 0x07;
>
> Concerning the patch (I lacked time to look at the driver to refresh my
> memory before -- was looking at the new Disk-on-chip H3 driver to be submitted
> for comments soon, BTW): it makes little sense in its current form since
> setting any DMA mode also sets 8-bit PIO timings now (and if DMA can't be set,
> the driver will fallback to PIO anyway)
Without ->autotune timings for PIO data transfers are never set and we need
to have a valid settings for some commands (IDENTIFY, SMART data) even if
DMA is not going to be used. Thus why I was hoping that this patch might be
of some help.
> I have a patch that changes this behavior and switches to always
> auto-tuning PIO but I've changed my mind on how the DMA/PIO timing register
> sharing should be handled now -- however, since I was unable to come up with
> anything better all that time, I'll consider pushing out this version when I
> have a spare time...
Please do.
Thanks,
Bart
next prev parent reply other threads:[~2007-08-01 21:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 11:08 hpt374 sata (Highpoint Rocket 1540) Bob Ham
2007-07-31 12:23 ` Alan Cox
2007-07-31 20:12 ` Bob Ham
2007-07-31 13:29 ` Sergei Shtylyov
2007-07-31 15:35 ` Brad Campbell
2007-07-31 17:52 ` Sergei Shtylyov
2007-07-31 21:22 ` Bob Ham
2007-07-31 21:32 ` Bartlomiej Zolnierkiewicz
2007-07-31 22:06 ` Bob Ham
2007-08-01 13:40 ` Sergei Shtylyov
2007-08-01 15:52 ` Bob Ham
2007-08-01 15:58 ` Sergei Shtylyov
2007-08-01 17:15 ` Bob Ham
2007-08-01 18:19 ` Sergei Shtylyov
2007-08-01 22:43 ` Alan Cox
2007-08-02 12:41 ` Sergei Shtylyov
2007-08-02 13:12 ` Alan Cox
2007-08-01 21:03 ` Bob Ham
2007-08-01 21:08 ` Sergei Shtylyov
2007-08-01 22:42 ` Alan Cox
2007-08-05 18:10 ` Sergei Shtylyov
2007-08-01 21:07 ` Bartlomiej Zolnierkiewicz [this message]
2007-08-01 21:16 ` Sergei Shtylyov
2007-08-01 21:29 ` Bartlomiej Zolnierkiewicz
2007-08-01 16:14 ` 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=200708012308.00057.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=rah@bash.sh \
--cc=sshtylyov@ru.mvista.com \
/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;
as well as URLs for NNTP newsgroup(s).