linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	linux-ide@vger.kernel.org, desaster.area@addcom.de,
	alan@redhat.com, bzolnier@gmail.com
Subject: Re: [PATCH] pata_sis: add missing UDMA5 timing value in sis_66_set_dmamode()
Date: Tue, 25 Sep 2007 18:06:42 -0400	[thread overview]
Message-ID: <46F98672.7070603@redhat.com> (raw)
In-Reply-To: <20070921072905.GC10660@htj.dyndns.org>

On 09/21/2007 03:29 AM, Tejun Heo wrote:
> sis_66_set_dmamode() also handles early UDMA100 (SIS630 ET) but is
> missing udma timing value for UDMA100.  According to sis5513, this
> should be 0x8000.  This caused UDMA100 device to fail on pata_sis till
> it downgrades to UDMA66 while it works fine on sis5513 at UDMA100.
> 
> Reported by Adam Blech.
> 
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> Cc: Adam Blech <desaster.area@addcom.de>
> ---
>  drivers/ata/pata_sis.c |    3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/ata/pata_sis.c b/drivers/ata/pata_sis.c
> index da3f720..3b5be77 100644
> --- a/drivers/ata/pata_sis.c
> +++ b/drivers/ata/pata_sis.c
> @@ -376,8 +376,9 @@ static void sis_66_set_dmamode (struct ata_port *ap, struct ata_device *adev)
>  	int drive_pci = sis_old_port_base(adev);
>  	u16 timing;
>  
> +	/* MWDMA 0-2 and UDMA 0-5 */
>  	const u16 mwdma_bits[] = { 0x008, 0x302, 0x301 };
> -	const u16 udma_bits[]  = { 0xF000, 0xD000, 0xB000, 0xA000, 0x9000};
> +	const u16 udma_bits[]  = { 0xF000, 0xD000, 0xB000, 0xA000, 0x9000, 0x8000 };
>  
>  	pci_read_config_word(pdev, drive_pci, &timing);
>  

Is this going into 2.6.23?
It's not in 2.6.23-rc8-mm1...

  parent reply	other threads:[~2007-09-25 22:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21  7:29 [PATCH] pata_sis: add missing UDMA5 timing value in sis_66_set_dmamode() Tejun Heo
2007-09-21 10:41 ` Alan Cox
2007-09-21 10:38   ` Tejun Heo
2007-09-25 22:06 ` Chuck Ebbert [this message]
2007-09-26  1:39 ` Jeff Garzik

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=46F98672.7070603@redhat.com \
    --to=cebbert@redhat.com \
    --cc=alan@redhat.com \
    --cc=bzolnier@gmail.com \
    --cc=desaster.area@addcom.de \
    --cc=htejun@gmail.com \
    --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 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).