All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	jgarzik@pobox.com, linux-ide@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH] pata_hpt{37x|3x2n}: fix timing register masks
Date: Fri, 27 Nov 2009 00:42:24 +0300	[thread overview]
Message-ID: <4B0EF640.5060000@ru.mvista.com> (raw)
In-Reply-To: <4B0EF0A4.1000201@ru.mvista.com>

Hello, I wrote:

>>>> These drivers inherited from the older 'hpt366' IDE driver the 
>>>> buggy timing
>>>> register masks in their set_piomode() metods. As a result, too low 
>>>> command
>>>> cycle active time is programmed for slow PIO modes.  Quite 
>>>> fortunately, it's
>>>> later "fixed up" by the set_dmamode() methods which also 
>>>> "helpfully" reprogram
>>>> the command timings, usually to PIO mode 4.
>>>>
>>>> However, the drivers added some breakage of their own too:  the bit 
>>>> that they
>>>> set/clear to control the FIFO is wrong -- it's actually the MSB of 
>>>> the command
>>>> cycle setup time; setting it in DMA mode is also wrong as this bit 
>>>> is only for
>>>> PIO actually...
>>>>
>>>> Fix all this and bump the drivers' versions, accounting for recenjt 
>>>> patches
>>>> that forgot to do it...
>>>>       
>>
>> Sergei, pata_hpt37x contains another copy of ->set_{piomode,dmamode} 
>> methods
>> (for HPT372 and later chipsets) which also need to be updated.
>>   
>
>   Oh, horror... :-(
>   They also all need to be squashed together and the interrupt bit 
> manipulation moved to some other place...

   I think I'll also do use different masks for UDMA and MWDMA in order 
to not change PIO data timings when setting an UDMA mode.

MBR, Sergei



      reply	other threads:[~2009-11-26 21:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24 20:15 [PATCH] pata_hpt{37x|3x2n}: fix timing register masks Sergei Shtylyov
2009-11-24 21:20 ` Alan Cox
2009-11-26 20:51   ` Bartlomiej Zolnierkiewicz
2009-11-26 21:18     ` Sergei Shtylyov
2009-11-26 21:42       ` Sergei Shtylyov [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=4B0EF640.5060000@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=stable@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.