From: viresh kumar <viresh.kumar@st.com>
To: Tejun Heo <tj@kernel.org>
Cc: "jgarzik@pobox.com" <jgarzik@pobox.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"viresh.linux@gmail.com" <viresh.linux@gmail.com>,
Shiraz HASHIM <shiraz.hashim@st.com>,
Armando VISCONTI <armando.visconti@st.com>,
amitgoel <amit.goel@st.com>
Subject: Re: [PATCH V2 2/2] pata_arasan_cf: Adding support for arasan compact flash host controller
Date: Tue, 22 Feb 2011 11:16:56 +0530 [thread overview]
Message-ID: <4D634DD0.60106@st.com> (raw)
In-Reply-To: <20110218143438.GK21209@htj.dyndns.org>
On 02/18/2011 08:04 PM, Tejun Heo wrote:
> On Fri, Feb 18, 2011 at 05:10:14PM +0530, Viresh Kumar wrote:
>> > +static struct scsi_host_template arasan_cf_sht = {
>> > + ATA_PIO_SHT(DRIVER_NAME),
>> > +};
> Hmmm... You probably have different requirements for .sg_tablesize and
> .dma_boundary, likely to be more lax.
>
Tejun,
Actually, we really don't have scatter-gather in our controller.
We have to read/write to the same FIFO address for every 512 bytes, after
which we get buf_avail interrupt. And Controller can do a maximum transfer
of 256 KB after which it gives transfer complete interrupt.
So all sg has to be handled in software, framework or driver.
Also, we will always read/write from/to FIFO. And the external DMA controller
doesn't have any limitation of this dma_boudary.
So i feel i should keep
.sg_tablesize = SG_ALL,
.dma_boundary = 0xFFFFFFFF,
Please correct me if i am wrong.
--
viresh
next prev parent reply other threads:[~2011-02-22 5:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 11:40 [PATCH V2 0/2] add pata_arasan_cf support Viresh Kumar
2011-02-18 11:40 ` [PATCH V1 1/2] libata-sff: add ata_sff_queue_work() & ata_sff_queue_delayed_work() Viresh Kumar
2011-02-18 14:11 ` Tejun Heo
2011-02-18 11:40 ` [PATCH V2 2/2] pata_arasan_cf: Adding support for arasan compact flash host controller Viresh Kumar
2011-02-18 14:34 ` Tejun Heo
2011-02-18 16:58 ` viresh kumar
2011-02-18 17:20 ` ejun Heo
2011-02-19 3:39 ` viresh kumar
2011-02-21 8:31 ` Tejun Heo
2011-02-22 5:46 ` viresh kumar [this message]
2011-02-22 8:58 ` Tejun Heo
2011-02-22 7:03 ` viresh kumar
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=4D634DD0.60106@st.com \
--to=viresh.kumar@st.com \
--cc=amit.goel@st.com \
--cc=armando.visconti@st.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=shiraz.hashim@st.com \
--cc=tj@kernel.org \
--cc=viresh.linux@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.