Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: linux-mips@linux-mips.org, Jeff Garzik <jgarzik@pobox.com>,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH 12/14] ata: pata_octeon_cf: Use I/O clock rate for timing calculations.
Date: Mon, 11 Oct 2010 14:43:54 +0100	[thread overview]
Message-ID: <20101011134354.GI30695@linux-mips.org> (raw)
In-Reply-To: <1286492633-26885-13-git-send-email-ddaney@caviumnetworks.com>

On Thu, Oct 07, 2010 at 04:03:51PM -0700, David Daney wrote:

> The creation of the I/O clock domain requires some adjustments.  Since
> the CF bus timing logic is clocked by the I/O clock, use its rate for
> delay calculations.
> 
> Signed-off-by: David Daney <ddaney@caviumnetworks.com>
> Cc: Jeff Garzik <jgarzik@pobox.com>
> Cc: linux-ide@vger.kernel.org

Haven't seen any ack yet but I assume due to the dependencies on other
MIPS patches it'll be ok if I merge this through the MIPS tree, so I
queued it for 2.6.37.

Thanks!

  Ralf

  reply	other threads:[~2010-10-11 13:44 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07 23:03 [PATCH 00/14] Add initial support for Octeon CN63XX David Daney
2010-10-07 23:03 ` [PATCH 01/14] MIPS: Octeon: Update register definitions for CN63XX chips David Daney
2010-10-11 12:47   ` Ralf Baechle
2010-10-07 23:03 ` [PATCH 02/14] MIPS: Octeon: Add cn63XX to Octeon chip detection macros David Daney
2010-10-11 13:08   ` Ralf Baechle
2010-10-07 23:03 ` [PATCH 03/14] MIPS: Octeon: Update L2 Cache code for CN63XX David Daney
2010-10-11 12:54   ` Ralf Baechle
2010-10-07 23:03 ` [PATCH 04/14] MIPS: Add identifiers for Octeon II CPUs David Daney
2010-10-07 23:03 ` [PATCH 05/14] MIPS: Octeon: Handle Octeon II caches David Daney
2010-10-11 13:13   ` Ralf Baechle
2010-10-07 23:03 ` [PATCH 06/14] MIPS: Octeon: Probe for Octeon II CPUs David Daney
2010-10-11 13:23   ` Ralf Baechle
2010-10-07 23:03 ` [PATCH 07/14] MIPS: Octeon: Enable Read Inhibit / eXecute Inhibit on Octeon II David Daney
2010-10-11 13:24   ` Ralf Baechle
2010-10-07 23:03 ` [PATCH 08/14] MIPS: Octeon: Scale Octeon2 clocks in octeon_init_cvmcount() David Daney
2010-10-08 10:36   ` Sergei Shtylyov
2010-10-11 12:31     ` Ralf Baechle
2010-10-11 13:26   ` Ralf Baechle
2010-10-07 23:03 ` [PATCH 09/14] MIPS: Octeon: Remove bogus code from octeon_get_clock_rate() David Daney
2010-10-11 13:28   ` Ralf Baechle
2010-10-07 23:03 ` [PATCH 10/14] MIPS: Octeon: Add octeon_get_io_clock_rate() for cn63xx David Daney
2010-10-11 13:30   ` Ralf Baechle
2010-10-07 23:03 ` [PATCH 11/14] MIPS: Octeon: Use I/O clock rate for calculations David Daney
2010-10-11 13:40   ` Ralf Baechle
2010-10-07 23:03 ` [PATCH 12/14] ata: pata_octeon_cf: Use I/O clock rate for timing calculations David Daney
2010-10-11 13:43   ` Ralf Baechle [this message]
2010-10-14  8:42     ` Jeff Garzik
2010-10-07 23:03 ` [PATCH 13/14] watchdog: octeon-wdt: " David Daney
2010-10-10 18:23   ` Wim Van Sebroeck
2010-10-11 12:40     ` Ralf Baechle
2010-10-07 23:03 ` [PATCH 14/14] MIPS: Octeon: Apply CN63XXP1 errata workarounds David Daney
2010-10-11 13:45   ` Ralf Baechle

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=20101011134354.GI30695@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=ddaney@caviumnetworks.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-mips@linux-mips.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