From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][pata-2.6 tree] pdc202xx_old: rewrite mode programming code
Date: Mon, 5 Mar 2007 23:08:36 +0100 [thread overview]
Message-ID: <200703052308.36887.bzolnier@gmail.com> (raw)
In-Reply-To: <45EC8713.5060304@ru.mvista.com>
On Monday 05 March 2007, Sergei Shtylyov wrote:
> Hello, I wrote:
>
> >> official == same as in the docs and vendor driver :-)
>
> >>> Erm, those look a bit doubtful...
>
> >> I believe that they are correct - please see explanations below.
>
> > Yeah, sorry about that. Only SWDMA timings are suspicious.
>
> Hm, too early to say sorry. I was hasty/distacted and forgot what I was
> going to write... :-)
>
> >>>> Index: b/drivers/ide/pci/pdc202xx_old.c
> >>>> ===================================================================
> >>>> --- a/drivers/ide/pci/pdc202xx_old.c
> >>>> +++ b/drivers/ide/pci/pdc202xx_old.c
> >>>
> >>> [...]
>
> >>>> @@ -161,7 +95,7 @@ static int pdc202xx_tune_chipset (ide_dr
> >>>> case XFER_UDMA_0:
> >>>> case XFER_MW_DMA_2: TB = 0x60; TC = 0x03; break;
> >>>> case XFER_MW_DMA_1: TB = 0x60; TC = 0x04; break;
> >>>> - case XFER_MW_DMA_0:
> >>>> + case XFER_MW_DMA_0: TB = 0xE0; TC = 0x0F; break;
>
> >>> This seems even slower than SWDMA0!
> >>> Let's assume that means 7 active cycles and 15 recovery cycles
> >>> (MWDMA1/2 settings seem to confirm this hypothesis) -- this would
> >>> give us 720 ns vs the specified 480. Could you shed some light on
> >>> what these fields mean? :-/
>
> >> The calculations are done in a different way so we get the correct
> >> timings:
>
> >> 7 cycles (== 210 ns) are used for active time
>
> Ugh, forgot to say: this is overclocked, 215 ns is the minimum active time
> for this mode.
I know that is why I wrote in my previous mail:
"These timings are the maximum possible ones using MB[2:0] and MC[3:0]"
Driver can't do better than hardware and hopefully these 5 ns
are compensated somehow by the chipset (or not :-).
Bart
prev parent reply other threads:[~2007-03-05 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 0:49 [PATCH][pata-2.6 tree] pdc202xx_old: rewrite mode programming code Bartlomiej Zolnierkiewicz
2007-03-05 17:30 ` Sergei Shtylyov
2007-03-05 20:38 ` Bartlomiej Zolnierkiewicz
2007-03-05 20:51 ` Sergei Shtylyov
2007-03-05 21:09 ` Sergei Shtylyov
2007-03-05 22:08 ` Bartlomiej Zolnierkiewicz [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=200703052308.36887.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).