From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/5] RFC spi: sun4i: add DMA support
Date: Thu, 2 Jun 2016 10:18:24 +0200 [thread overview]
Message-ID: <20160602081824.GH4908@lukather> (raw)
In-Reply-To: <CAOMqctSWnbUaOveMUhz+yOJqTOK4EhDd5jUqKoHCohfndNAjWA@mail.gmail.com>
On Tue, May 31, 2016 at 04:19:28PM +0200, Michal Suchanek wrote:
> On 31 May 2016 at 15:27, Mark Brown <broonie@kernel.org> wrote:
> > On Tue, May 31, 2016 at 12:44:54PM +0200, Michal Suchanek wrote:
> >> On 30 May 2016 at 17:50, Mark Brown <broonie@kernel.org> wrote:
> >> > On Mon, May 30, 2016 at 05:28:10PM +0200, Michal Suchanek wrote:
> >
> >> >> It's what the driver did to start with and it was requested to fall
> >> >> back to non-DMA in the case DMA is not available.
> >
> >> > Why? I really can't see any sensible use case for this that doesn't
> >> > have a better solution available.
> >
> >> Of course, the solution is to compile in the DMA driver.
> >
> >> It's been argued that some drivers which use only short transfers will
> >> just work.
> >
> > With nothing else in the system that needs DMA? It's making the
> > performance of the system less reliable for the benefit of a very narrow
> > use case.
>
> Some of the platform devices have dedicated DMA *controller* built
> into the device IP so the DMA engine really is optional on many sunxi
> devices. Besides SPI you definitely need the DMA engine for audio. You
> probably don't need it for storage and graphics. I don't have any idea
> if it's used for USB and Ethernet.
USB and Ethernet have their own dedicated DMA engines. So currently,
the only driver that requires it is the audio codec.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160602/643ba51f/attachment.sig>
next prev parent reply other threads:[~2016-06-02 8:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 22:56 [PATCH 0/5] sunxi spi fixes Michal Suchanek
2016-05-26 19:25 ` [PATCH 1/5] spi: sunxi: fix transfer timeout Michal Suchanek
2016-05-27 2:05 ` [linux-sunxi] " Julian Calaby
2016-05-27 5:05 ` Michal Suchanek
2016-05-27 5:10 ` Julian Calaby
2016-05-30 11:23 ` Mark Brown
2016-05-31 11:52 ` Michal Suchanek
2016-06-01 18:20 ` Maxime Ripard
2016-05-30 9:44 ` Maxime Ripard
2016-05-26 19:25 ` [PATCH 3/5] spi: sunxi: expose maximum transfer size limit Michal Suchanek
2016-05-30 8:37 ` Maxime Ripard
2016-05-30 8:57 ` Michal Suchanek
2016-06-01 18:14 ` Maxime Ripard
2016-05-26 19:25 ` [PATCH 2/5] spi: sun4i: fix FIFO limit Michal Suchanek
2016-05-30 8:37 ` Maxime Ripard
2016-05-26 19:25 ` [PATCH 4/5] spi: sunxi: set maximum and minimum speed of SPI master Michal Suchanek
2016-05-30 9:17 ` Maxime Ripard
2016-05-26 19:25 ` [PATCH 5/5] RFC spi: sun4i: add DMA support Michal Suchanek
2016-05-30 11:26 ` Mark Brown
2016-05-30 12:11 ` Geert Uytterhoeven
2016-05-30 15:03 ` Mark Brown
2016-05-30 15:28 ` Michal Suchanek
2016-05-30 15:50 ` Mark Brown
2016-05-31 10:44 ` Michal Suchanek
2016-05-31 13:27 ` Mark Brown
2016-05-31 14:19 ` Michal Suchanek
2016-06-02 8:18 ` Maxime Ripard [this message]
2016-06-01 18:00 ` Maxime Ripard
2016-06-02 4:42 ` [linux-sunxi] " Priit Laes
2016-06-02 9:18 ` Mark Brown
2016-06-02 12:14 ` Michal Suchanek
2016-06-02 14:26 ` Mark Brown
2016-06-05 11:27 ` Michal Suchanek
2016-06-06 11:36 ` Mark Brown
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=20160602081824.GH4908@lukather \
--to=maxime.ripard@free-electrons.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).