From: James Hogan <james.hogan@imgtec.com>
To: Shashidhar Hiremath <shashidharh@vayavyalabs.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
Will <will.newton@imgtec.com>
Subject: Re: A few queries dw_mmc driver
Date: Tue, 02 Aug 2011 22:47:57 +0100 [thread overview]
Message-ID: <4E38708D.9070801@imgtec.com> (raw)
In-Reply-To: <CANYdXnrYaqck5ekWtjcP+HDmRcav3kxew6dVuv5jgemURR3uZw@mail.gmail.com>
Hi Shashidhar
(resending in form that won't get bounced from linux-mmc list).
On 08/02/2011 12:53 PM, Shashidhar Hiremath wrote:
> Hi James,
> Sorry for interrupting you,
>
> I had a few queries on mmc driver. Can you please help on this
I've CC'd the linux-mmc list as both questions involve mostly generic MMC.
> 1>
> ------------------------------------------------------------------------------
> What do the following elements in the mmc_host struct signify:
> max_segs,max_block_size,max_block_count,max_seg_size,max_req_size
I'm not familiar with these myself, but as far as I can tell they
signify the limits of the DMAC (which is why they're set differently
depending on whether the internal DMAC or the platform specific DMAC is
used):
http://lxr.linux.no/#linux+v3.0/drivers/mmc/host/dw_mmc.c#L1421
> I was adding the support for Dual_Buffer Descriptors support in dw_mmc
> driver.Does it require a change in the above elements of mmc_host
> structure ?
I don't know, but I'll see if I can find out.
> ------------------------------------------------------------------------------
>
> 2>
> ------------------------------------------------------------------------------
> I have observed in most of the drivers that the switching between PIO
> mode and the DMA mode is being done based on the data_size. Instead can
> this be made independent of data_size and be coded such that ,it only
> depends on the menu-config option and driver uses only one ?
I can see the use of that (I've forced PIO mode myself during debugging
or running mmc_test), but whether this is an acceptable thing to have
upstream as a config option I don't know.
Regards
James
next parent reply other threads:[~2011-08-02 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANYdXnrvEJiehbz53WHMriAqn8F0uhnCFEE=x0gy19hfTXZStw@mail.gmail.com>
[not found] ` <CANYdXnpG2oyXL2wVzdE=h4S1SHR_tsvoBwU4VVDQmTjtU0fL5g@mail.gmail.com>
[not found] ` <CANYdXnrYaqck5ekWtjcP+HDmRcav3kxew6dVuv5jgemURR3uZw@mail.gmail.com>
2011-08-02 21:47 ` James Hogan [this message]
2011-08-04 10:20 ` A few queries dw_mmc driver James Hogan
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=4E38708D.9070801@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=linux-mmc@vger.kernel.org \
--cc=shashidharh@vayavyalabs.com \
--cc=will.newton@imgtec.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