reverted.
Signed-off-by: Sergei Ianovich
CC: Daniel Mack
CC: Haojian Zhuang
CC: Arnd Bergmann
---
v3..v4
* no changes
v2..v3
* split into good (PATCH 07/21) and temporary (this one) parts
v1..v2
* add binding for next-gen dma controller
* use correct dma declararion
* n
Daniel,
On Tue, 2013-12-17 at 23:37 +0400, Sergei Ianovich wrote:
> The existing PXA MMC driver cannot get DMA channels in a proper
> way from the respective device tree binding.
>
> This patch provides temporary workaround which allows using the
> existing driver in DT machines
reverted.
Signed-off-by: Sergei Ianovich
CC: Daniel Mack
CC: Arnd Bergmann
---
v2..v3
* split into good (PATCH 07/21) and temporary (this one) parts
v1..v2
* add binding for next-gen dma controller
* use correct dma declararion
* number changed from 5 to 3
drive
On Mon, 2013-12-16 at 12:58 +0100, Lars-Peter Clausen wrote:
> Btw. any driver that parses the dmas property manually should be considered
> broken. This is a classical layering violation. The layout of the dma
> specifier is DMA controller specific and should be completely transparent to
> the dev
On Mon, 2013-12-16 at 10:58 +0100, Daniel Mack wrote:
> On 12/14/2013 08:34 PM, Sergei Ianovich wrote:
> > On Sat, 2013-12-14 at 20:06 +0100, Arnd Bergmann wrote:
>
> >> The patch looks ok in case we are merging your patches for 3.14
> >> and Daniel's patches
On Sat, 2013-12-14 at 20:06 +0100, Arnd Bergmann wrote:
> On Friday 13 December 2013, Sergei Ianovich wrote:
> > Non-dts implementation supply required DMA channel numbers as
> > IORESOURCE_DMA. However, there is was no way to get them from
> > device tree.
>
> P
Non-dts implementation supply required DMA channel numbers as
IORESOURCE_DMA. However, there is was no way to get them from
device tree.
Signed-off-by: Sergei Ianovich
CC: Daniel Mack
CC: Arnd Bergmann
---
v1..v2
* add binding for next-gen dma controller
* use correct dma declararion
