From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 03/03] omap hsmmc: adaptation of sdma descriptor autoloading feature
Date: Thu, 11 Mar 2010 10:39:44 -0800 [thread overview]
Message-ID: <20100311183944.GJ2900@atomide.com> (raw)
In-Reply-To: <618f0c911003110708s5015f2bftb443b9ea57cb6477@mail.gmail.com>
* Venkatraman S <svenkatr@ti.com> [100311 07:04]:
> Tony Lindgren wrote:
> >
> > 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.
OK, that might explain some nasty surprises then..
With these patches, does the driver still work in PIO mode though?
> 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).
Sounds good to me, thanks for looking into it.
Regards,
Tony
next prev parent reply other threads:[~2010-03-11 18:39 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
2010-03-11 18:39 ` Tony Lindgren [this message]
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=20100311183944.GJ2900@atomide.com \
--to=tony@atomide.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).