linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] hpt366: fix HPT37x PIO mode timings (take 2)
Date: Sun, 9 Dec 2007 18:10:35 +0100	[thread overview]
Message-ID: <200712091810.36063.bzolnier@gmail.com> (raw)
In-Reply-To: <200712081838.10647.sshtylyov@ru.mvista.com>

On Saturday 08 December 2007, Sergei Shtylyov wrote:
> After looking into the HPT370 manual (now that I have it) and re-checking all
> the timing tables, here's what I have discovered:
> 
> - at 33 MHz clock, PIO mode 0 timings turned to be overclocked, and all other
>   PIO modes underclocked;
> 
> - at 50 MHz clock, PIO modes 0 to 2 turned to be overclocked;
> 
> - at 66 MHz clock, PIO mode 0 was overclocked too.
> 
> Finally, the taskfile timing (matching PIO mode 0) turned to be overclocked at
> all clock frequencies (and in all manuals)...
> 
> The new timings have been tested on HPT370 chip (at 33 MHz PCI clock) and on
> HPT371N chip (at both 50 and 66 MHz DPLL clock).
> 
> Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>

applied

> ---
> Many PIO modes at 55/66 MHz (as well as MDDMA modes at all clocks) are also
> underclocked but I decided not to touch them, at least for the time being.
> The patch is against the Linus' tree, with PIO0 setup time correct this time...

Since it is against Linus' tree I assume that it is safe enough to be merged
for 2.6.24, right?

  reply	other threads:[~2007-12-09 18:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-08 15:38 [PATCH] hpt366: fix HPT37x PIO mode timings (take 2) Sergei Shtylyov
2007-12-09 17:10 ` Bartlomiej Zolnierkiewicz [this message]
2007-12-10 12:33   ` 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=200712091810.36063.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=linux-ide@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).