From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pata_it8213: MWDMA0 is unsupported
Date: Thu, 26 Nov 2009 21:33:14 +0300 [thread overview]
Message-ID: <4B0EC9EA.9000608@ru.mvista.com> (raw)
In-Reply-To: <200911261927.00597.bzolnier@gmail.com>
Bartlomiej Zolnierkiewicz wrote:
>>>>>>>MWDMA0 timings cannot be met with the PIIX based controller
>>>>>>>programming interface.
>>>>>>>This change should be safe as this is how we have been doing
>>>>>>>things in IDE it8213 host driver for years.
>>>>>>>Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
>>>>>>>---
>>>>>>>Verified with the documentation (similar case as with pata_efar).
>>>>>>Uhhh, no...
>>>>>>Too many damn drivers.
>>>>>>Too much damn duplication.
>>>>>>Too much damn subtle differences here and there.
>>>>>>The hardware is probably fine for MWMDA0 when it comes to pata_{efar,it8213},
>>>>>>it just not documented properly in the data sheet.
>>>>> How so with pata_efar? The active/recovery bitfields are still 2-bit
>>>>>wide, no?
>>>>Yes but when TIMEx bit is disabled we are using XFER_PIO_SLOW timings.
>> 600 ns cycle vs spec'ed 480 ns? Is it really worth it?
> 960 ns actually
That table you're looking at (probably in the SLC90E66 datasheet?) must
be screwed up. 960 ns is used for command cycles, according to Intel's docs,
data cycles run at 600 ns...
>>>>All data sheets including original Intel ones are a complete crap when it
>>>>comes to explicitly documenting this behavior.
>>>OTOH all drivers set TIMEx for MWDMA0 currently.. ?
>>
>> ... which would give a grossly overclocked timing.
> Except ata_piix which blacklists MWDMA0 for _all_ PATA controllers.. :)
:-)
> I'm leaving my patches as they were for now, unless somebody wants to
> untangle this mess this is a safest and quickest way forward..
MBR, Sergei
next prev parent reply other threads:[~2009-11-26 18:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 16:28 [PATCH] pata_it8213: MWDMA0 is unsupported Bartlomiej Zolnierkiewicz
2009-11-26 17:00 ` Bartlomiej Zolnierkiewicz
2009-11-26 17:23 ` Sergei Shtylyov
2009-11-26 18:00 ` Bartlomiej Zolnierkiewicz
2009-11-26 18:03 ` Bartlomiej Zolnierkiewicz
2009-11-26 18:12 ` Sergei Shtylyov
2009-11-26 18:27 ` Bartlomiej Zolnierkiewicz
2009-11-26 18:33 ` Sergei Shtylyov [this message]
2009-11-26 18:47 ` Sergei Shtylyov
2009-12-03 21:04 ` Jeff Garzik
2009-12-03 22:06 ` Sergei Shtylyov
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=4B0EC9EA.9000608@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).