All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v1 0/2] spi: dw-mid: fix simplex DMA transfers
Date: Wed, 29 Oct 2014 15:20:48 +0200	[thread overview]
Message-ID: <1414588848.2396.64.camel@linux.intel.com> (raw)
In-Reply-To: <20141029111712.GE18557-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>

On Wed, 2014-10-29 at 11:17 +0000, Mark Brown wrote:
> On Wed, Oct 29, 2014 at 12:37:56PM +0200, Andy Shevchenko wrote:
> > On Tue, 2014-10-28 at 22:41 +0000, Mark Brown wrote:
> 
> > >   Can you please also send a patch for Linus
> > > setting SPI_MASTER_MUST_RX and SPI_MASTER_MUST_TX - this is a bug which
> > > should be fixed in mainline but these seem a bit big for merge right
> > > now, those flags will cause the core to always ensure that both
> > > directions have data avoiding the issue?
> 
> > I'm sorry I didn't quite understand that bug.
> 
> > When those bits are set the core will always provide valid tx_buf and
> > rx_buf pointers. How would it help us? Currently driver relies on tx_dma
> > and rx_dma which are provided by clients if I understood correctly.
> 
> Uh, are you sure

There is a function in spi-dw.c called map_dma_buffers() which uses
tx_dma and rx_dma pointers. I don't see where they are initialized.

>  - how exactly has this been tested?  

I don't know how it was tested before, but, besides intel-mid-dma is
somehow broken (I won't spend time to patch it), I'm using patch I
already published which converts driver to use dw_dmac driver. With it I
run tests on a loop back.

> tx_dma and rx_dma
> *can* be provided by users but vanishingly few actually do so.  Drivers
> must not rely on the caller doing this, the feature will be going away
> apart from anything else.  If the driver is relying on this it probably
> needs to have the DMA support that's there removed as a fix and should
> be converted to use the core DMA mapping functionality in -next.

So, regarding to above what would you like me to do as next step?

-- 
Andy Shevchenko <andriy.shevchenko-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Intel Finland Oy

--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-10-29 13:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28 16:25 [PATCH v1 0/2] spi: dw-mid: fix simplex DMA transfers Andy Shevchenko
     [not found] ` <1414513502-595-1-git-send-email-andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2014-10-28 16:25   ` [PATCH v1 1/2] spi: dw-mid: refactor to use helpers Andy Shevchenko
2014-10-28 16:25   ` [PATCH v1 2/2] spi: dw-mid: split rx and tx callbacks when DMA Andy Shevchenko
2014-10-28 22:41   ` [PATCH v1 0/2] spi: dw-mid: fix simplex DMA transfers Mark Brown
     [not found]     ` <20141028224156.GN18557-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-10-29 10:37       ` Andy Shevchenko
     [not found]         ` <1414579076.2396.62.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2014-10-29 11:17           ` Mark Brown
     [not found]             ` <20141029111712.GE18557-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-10-29 13:20               ` Andy Shevchenko [this message]
     [not found]                 ` <1414588848.2396.64.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2014-10-29 22:15                   ` Mark Brown
     [not found]                     ` <20141029221530.GQ18557-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-10-30  7:10                       ` Andy Shevchenko

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=1414588848.2396.64.camel@linux.intel.com \
    --to=andriy.shevchenko-vuqaysv1563yd54fqh9/ca@public.gmane.org \
    --cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.