From: Tony Lindgren <tony@atomide.com>
To: Shubhrajyoti D <shubhrajyoti@ti.com>
Cc: spi-devel-general@lists.sourceforge.net,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: omap2-mcspi: In case of dma errors fall back to pio
Date: Tue, 7 Aug 2012 00:47:40 -0700 [thread overview]
Message-ID: <20120807074740.GR11011@atomide.com> (raw)
In-Reply-To: <1343197229-15188-1-git-send-email-shubhrajyoti@ti.com>
* Shubhrajyoti D <shubhrajyoti@ti.com> [120724 23:26]:
> In case there are dma errors currently the driver exits.
> Make the spi driver fall back to pio mode in case of dma errors.
>
> If the DMA engine is not selected the driver
> exits.This patch makes the spi fall back to pio in that case.
>
> Also adds a field dma_unusable to struct omap2_mcspi.
>
> Signed-off-by: Shubhrajyoti D <shubhrajyoti@ti.com>
> ---
> drivers/spi/spi-omap2-mcspi.c | 21 +++++++++++++--------
> 1 files changed, 13 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/spi/spi-omap2-mcspi.c b/drivers/spi/spi-omap2-mcspi.c
> index bc47781..f243a39 100644
> --- a/drivers/spi/spi-omap2-mcspi.c
> +++ b/drivers/spi/spi-omap2-mcspi.c
> @@ -129,6 +129,7 @@ struct omap2_mcspi {
> struct omap2_mcspi_dma *dma_channels;
> struct device *dev;
> struct omap2_mcspi_regs ctx;
> + int dma_unusable;
> };
Don't you need to check separately for rx and tx dma? There's a slight
chance that you get a channel for one but not for the other..
Tony
next prev parent reply other threads:[~2012-08-07 7:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 6:20 [PATCH] spi: omap2-mcspi: In case of dma errors fall back to pio Shubhrajyoti D
2012-08-07 7:47 ` Tony Lindgren [this message]
2012-08-07 11:21 ` Shubhrajyoti
2012-08-07 12:02 ` Tony Lindgren
2012-08-07 12:21 ` Felipe Balbi
[not found] ` <1343197229-15188-1-git-send-email-shubhrajyoti-l0cyMroinI0@public.gmane.org>
2012-08-08 14:39 ` Philip, Avinash
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=20120807074740.GR11011@atomide.com \
--to=tony@atomide.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=shubhrajyoti@ti.com \
--cc=spi-devel-general@lists.sourceforge.net \
/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).