From: svenkatr@ti.com (Venkatraman S)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 03/03] omap hsmmc: adaptation of sdma descriptor autoloading feature
Date: Thu, 11 Mar 2010 20:38:02 +0530 [thread overview]
Message-ID: <618f0c911003110708s5015f2bftb443b9ea57cb6477@mail.gmail.com> (raw)
In-Reply-To: <20100310224110.GW2900@atomide.com>
Tony Lindgren wrote:
> * Venkatraman S <svenkatr@ti.com> [100310 06:08]:
>> @@ -1400,14 +1471,23 @@ omap_hsmmc_prepare_data(struct omap_hsmmc_host
>> *host, struct mmc_request *req)
>> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? | (req->data->blocks << 16));
>> ? ? ? set_data_timeout(host, req->data->timeout_ns, req->data->timeout_clks);
>>
>> - ? ? if (host->use_dma) {
>> - ? ? ? ? ? ? ret = omap_hsmmc_start_dma_transfer(host, req);
>> - ? ? ? ? ? ? if (ret != 0) {
>> - ? ? ? ? ? ? ? ? ? ? dev_dbg(mmc_dev(host->mmc), "MMC start dma failure\n");
>> + ? ? if (host->dma_caps & DMA_TYPE_SDMA) {
>> + ? ? ? ? ? ? ret = omap_hsmmc_configure_sdma(host, req);
>> + ? ? ? ? ? ? if (ret)
>> ? ? ? ? ? ? ? ? ? ? ? return ret;
>> - ? ? ? ? ? ? }
>> + ? ? ? ? ? ? host->dma_in_use = DMA_TYPE_SDMA;
>> ? ? ? }
>> - ? ? return 0;
>> + ? ? if ((host->dma_caps & DMA_TYPE_SDMA_DLOAD) &&
>> + ? ? ? ? ? ? host->data->sg_len > 4) {
>> + ? ? ? ? ? ? ret = omap_hsmmc_configure_sdma_sglist(host, req);
>> + ? ? ? ? ? ? if (ret)
>> + ? ? ? ? ? ? ? ? ? ? return ret;
>> + ? ? ? ? ? ? host->dma_in_use = DMA_TYPE_SDMA_DLOAD;
>> +
>> + ? ? }
>> + ? ? ret = omap_hsmmc_start_dma_transfer(host);
>> + ? ? return ret;
>> +
>> ?}
>
> Does the driver still work in PIO mode?
>
> We need to have the drivers capable to fail over to PIO mode
> as the DMA channels can run out.
>
The driver doesn't have an automatic fallback to PIO,
even without my patch. A error return from omap_request_dma is
propogated all the way back to the transfer request.
The decision to use_dma (the variable) is unaltered.
Infact, it would be easier to implement a runtime fallback after
this patch is
merged as I have separated out the capability and runtime selection.
(dma_caps and dma_in_use).
Regards,
Venkat.
next prev parent reply other threads:[~2010-03-11 15:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 14:12 [PATCH 03/03] omap hsmmc: adaptation of sdma descriptor autoloading feature Venkatraman S
2010-03-10 22:41 ` Tony Lindgren
2010-03-11 15:08 ` Venkatraman S [this message]
2010-03-11 18:39 ` Tony Lindgren
2010-03-12 8:18 ` Venkatraman S
-- strict thread matches above, loose matches on Subject: below --
2010-03-01 11:27 Venkatraman S
2010-03-11 1:01 ` Madhusudhan
2010-03-11 10:52 ` Venkatraman S
2010-03-11 16:27 ` Madhusudhan
2010-03-11 17:42 ` Venkatraman S
2010-03-12 2:29 ` Madhusudhan
2010-03-12 6:03 ` Venkatraman S
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=618f0c911003110708s5015f2bftb443b9ea57cb6477@mail.gmail.com \
--to=svenkatr@ti.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).