From: David Daney <ddaney@caviumnetworks.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-ide@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: [PATCH 1/2] libata: Add two more columns to the ata_timing table.
Date: Mon, 08 Dec 2008 12:44:44 -0800 [thread overview]
Message-ID: <493D873C.3020202@caviumnetworks.com> (raw)
In-Reply-To: <493D6DA1.3090801@ru.mvista.com>
Sergei Shtylyov wrote:
> OK, t6z is yet longer than t9 but putting it into the table seems
> pointless anyway as it's fixed at 30 ns, at least for the standard 5 PIO
> modes (and for other two modes 30 ns would be good anyway).
> Though frankly speaking I don't quite understand your care for this
> timing, if the ATA standard permits -CE deasserted and data bus being
> driven to overlap.
It doesn't matter what the ATA standard permits in this case. We need
to assure that the OCTEON Boot Bus standard is respected. There are
several timing parameters that we have to set based on the documented
properties of the device. Ideally if we try to run bus cycles for
non-ATA/CF devices that share the signal lines of the Boot Bus, they
should not interfere with the CF interface.
David Daney
next prev parent reply other threads:[~2008-12-08 20:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 23:06 [PATCH 0/2] libata: Cavium OCTEON SOC Compact Flash driver (v3) David Daney
2008-12-05 23:09 ` [PATCH 1/2] libata: Add two more columns to the ata_timing table David Daney
2008-12-06 20:19 ` Sergei Shtylyov
2008-12-08 18:22 ` David Daney
2008-12-08 18:48 ` Sergei Shtylyov
2008-12-08 18:55 ` Sergei Shtylyov
2008-12-08 20:44 ` David Daney [this message]
2008-12-08 23:19 ` Sergei Shtylyov
2008-12-05 23:09 ` [PATCH 2/2] libata: New driver for OCTEON SOC Compact Flash interface (v3) David Daney
2008-12-06 22:46 ` 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=493D873C.3020202@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-mips@linux-mips.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).