From: Akinobu Mita <akinobu.mita-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Applied "spi: omap2-mcspi: Undo broken fix for dma transfer of vmalloced buffer" to the spi tree
Date: Fri, 13 May 2016 01:47:07 +0900 [thread overview]
Message-ID: <CAC5umyj0Qn75aPvm50eMSL+wqWvquf9Z7gEV8PCbMnJwPSuccw@mail.gmail.com> (raw)
In-Reply-To: <20160512154436.GE6261-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-05-13 0:44 GMT+09:00 Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>:
> On Thu, May 12, 2016 at 10:49:15PM +0900, Akinobu Mita wrote:
>
>> If we have an optional callback to get the actual DMA transfer length
>> instead of using spi_transfer->len for each spi_transfer in the
>> framework, we can use it to determine the correct map size used by
>> spi_map_buf() in spi.c.
>
> That sounds plausible, we can also do some querying of the dmaengine at
> the same place we call that when we get around to that. Can you try to
> come up with an implementation?
OK, I'll try and see how it looks like.
--
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
prev parent reply other threads:[~2016-05-12 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 18:43 [PATCH] Revert "spi: omap2-mcspi: fix dma transfer for vmalloced buffer" Akinobu Mita
[not found] ` <1460140995-4062-1-git-send-email-akinobu.mita-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-12 1:22 ` Mark Brown
2016-04-12 2:01 ` Applied "spi: omap2-mcspi: Undo broken fix for dma transfer of vmalloced buffer" to the spi tree Mark Brown
2016-05-11 15:39 ` Akinobu Mita
[not found] ` <CAC5umyg2fJxYKOB4J96+3igkNx+eJs5MET8S8NnafZ3hcPPEag-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-05-11 16:20 ` Mark Brown
[not found] ` <20160511162030.GN6261-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-05-12 13:49 ` Akinobu Mita
[not found] ` <CAC5umyjoKfMBbO1JPyTjqsz4zuiZMQDZcKHxonZuEwqGpJxb_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-05-12 15:44 ` Mark Brown
[not found] ` <20160512154436.GE6261-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-05-12 16:47 ` Akinobu Mita [this message]
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=CAC5umyj0Qn75aPvm50eMSL+wqWvquf9Z7gEV8PCbMnJwPSuccw@mail.gmail.com \
--to=akinobu.mita-re5jqeeqqe8avxtiumwx3w@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 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).