From: "Sonic Zhang" <sonic.adi@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH again] [libata] libata driver for bf548 on chip ATAPI controller.
Date: Wed, 15 Aug 2007 16:55:48 +0800 [thread overview]
Message-ID: <4e5ebad50708150155s5cd75a5bt813742b5a02d56d@mail.gmail.com> (raw)
In-Reply-To: <20070814103013.6899813f@the-village.bc.nu>
On 8/14/07, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > +/**
> > + * Register transfer timing table
> > + */
>
> Libata has a complete set of transfer mode tables and timing functions -
> any reason for not using them ?
>
After a bit investigation, I find the timing paramters difined in
struct ata_timing are different from that in hardware manual of BF548.
struct ata_timing {
unsigned short mode; /* ATA mode */
unsigned short setup; /* t1 */
unsigned short act8b; /* t2 for 8-bit I/O */
unsigned short rec8b; /* t2i for 8-bit I/O */
unsigned short cyc8b; /* t0 for 8-bit I/O */
unsigned short active; /* t2 or tD */
unsigned short recover; /* t2i or tK */
unsigned short cycle; /* t0 */
unsigned short udma; /* t2CYCTYP/2 */
};
BF548 PIO timing registers:
u8 teoc_reg;
u8 t2_reg;
u4 t4_reg;
u8 t2_pio;
u4 t1_reg;
u8 teoc_pio;
BF548 UDMA timing registers:
u8 tenv;
u8 tack;
u8 tcyc_tdvs;
u8 tdvs;
u8 tmli;
u8 tss;
u8 trp;
u8 tzah;
I can't find a simple way to configure bf548 registers with the ata_timing data.
prev parent reply other threads:[~2007-08-15 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1187056118.16255.1.camel@sevens.analog.com>
2007-08-14 2:25 ` Sonic Zhang
2007-08-14 9:30 ` Alan Cox
[not found] ` <4e5ebad50708142314o6bb64b6bocf75166cb9999205@mail.gmail.com>
2007-08-15 6:54 ` Sonic Zhang
2007-08-15 8:55 ` Sonic Zhang [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=4e5ebad50708150155s5cd75a5bt813742b5a02d56d@mail.gmail.com \
--to=sonic.adi@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®