Skip to content

RFC: exynos multiplatform support

Arnd Bergmann linux-arm-kernel linux-media linux-samsung-soc 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 23 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 23 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 00/23] RFC: exynos multiplatform support
Quoted 3 lines · Heiko St?bner

If I remember correctly Kgene mentioning some time back, that someone was working on converting the s3c dma to dmaengine, but I never heard anything more about it.

Ok, let's see if we can find out what happened to that.

Quoted 1 line

So personally I would be grateful, for people not breaking my devices :-) .

I'm sure we can find a way. It's also clear that the current s3c_dma does not have a bright future.

Quoted 4 lines

On an unrelated note, exists some sort of documentation for creating dmaengine drivers somewhere? Documentation/* seems to always be only targetted at device driver writers and my own DMA knowledge is still stuck at the theoretical level they teach in generic operating-systems university courses.

I think we only have Documentation/dmaengine.txt, which is targetted at people using the dmaengine API, not at someone writing a driver.

I have only limited experience myself, but I know that it comes down to filling the operations of a struct dma_device. A slight complication is that the dmaengine interface handles both memory-to-memory transfers and slave device transfers (the slave being the device that you are talking to), and you have to know which parts are relevant for your use case. You probably only need the slave interface, but it can seem like it's bolted to the side of the original API.

drivers/dma/mxs-dma.c looks like a reasonable driver that one can use as an example. The s3c64xx_dma code is also interesting because it has both an implementation of the s3c_dma interface in arch/arm/mach-s3c64xx/dma.c and one using the generic interface in drivers/dma/amba-pl08x.c. The latter also implements a "virtual channel" concept that you probably don't need.

Arnd