Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: David Daney <ddaney@caviumnetworks.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 21:48:47 +0300	[thread overview]
Message-ID: <493D6C0F.7070809@ru.mvista.com> (raw)
In-Reply-To: <493D65C8.2060808@caviumnetworks.com>

David Daney wrote:

>> Hello.

>> David Daney wrote:

>>> The forthcoming OCTEON SOC Compact Flash driver needs a few more
>>> timing values than were available in the ata_timing table.  I add new
>>> columns for write_hold and read_holdz times.  The values were obtained
>>> from the Compact Flash specification Rev 4.1.

>>> Signed-off-by: David Daney <ddaney@caviumnetworks.com>

>> NAK.

>>> diff --git a/include/linux/libata.h b/include/linux/libata.h
>>> index ed3f26e..95fa9f6 100644
>>> --- a/include/linux/libata.h
>>> +++ b/include/linux/libata.h
>>
>> [...]
>>
>>>  enum ata_xfer_mask {
>>> @@ -864,6 +868,8 @@ struct ata_timing {
>>>      unsigned short cyc8b;        /* t0 for 8-bit I/O */
>>>      unsigned short active;        /* t2 or tD */
>>>      unsigned short recover;        /* t2i or tK */
>>> +    unsigned short write_hold;    /* t4 */
>>> +    unsigned short read_holdz;    /* t6z */
>>
>>
>>    Sorry for failing to notice this before but t6z is again the timing 
>> that the host can't control. Therefore I'm seeig no sense in its 
>> addition.
> 
> 
> The host cannot control t6z, but in some cases (like ours) it needs to 
> be aware of its value.  We cannot start driving the bus for access to 
> other devices until the CF stops driving it.  We need to know how long 
> to wait until it is safe to use the bus for other things.

    Re-read the spec please, the timing you need is t9 and it's much longer 
than t6 that your driver using instead.

>> I don't know how your driver is going to use it -- but most probably 
>> incorrectly...

> Thanks for that vote of confidence.

   You're welcome. :-)

> David Daney

MBR, Sergei

  reply	other threads:[~2008-12-08 18:49 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 [this message]
2008-12-08 18:55         ` Sergei Shtylyov
2008-12-08 20:44           ` David Daney
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=493D6C0F.7070809@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=ddaney@caviumnetworks.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