[PATCH v4 2/2] DW DMAC: add multi-block property to device tree

2016-11-23 Thread Eugeniy Paltsev
Several versions of DW DMAC have multi block transfers hardware support. Hardware support of multi block transfers is disabled by default if we use DT to configure DMAC and software emulation of multi block transfers used instead. Add multi-block property, so it is possible to enable hardware multi

[PATCH v4 1/2] DW DMAC: enable memory-to-memory transfers support

2016-11-23 Thread Eugeniy Paltsev
All known devices, which use DT for configuration, support memory-to-memory transfers. So enable it by default, if we read configuration from DT. Acked-by: Andy Shevchenko Signed-off-by: Eugeniy Paltsev --- drivers/dma/dw/platform.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/driv

[PATCH v4 0/2] DW DMAC: update device tree

2016-11-23 Thread Eugeniy Paltsev
It wasn't possible to enable some features like memory-to-memory transfers or multi block transfers via DT. It is fixed by these patches. Changes for v4: * Fix setting inverted value to "dwc->nollp". My fault - I tested with wrong DTS, so DMAC was configured from autoconfig instead of devi

Re: [PATCH 3/6] arc: Use full path in KBUILD_IMAGE definition

2016-11-23 Thread Alexey Brodkin
Hi Michal, On Tue, 2016-11-22 at 22:34 +0100, Michal Marek wrote: > The KBUILD_IMAGE variable is used by the rpm and deb-pkg targets, which > expect it to point to the image file in the build directory. The > builddeb script has a workaround for architectures which only provide > the basename, but

Re: [PATCH] ARCv2: MCIP: Deprecate setting of affinity in Device Tree

2016-11-23 Thread Vineet Gupta
On 11/22/2016 03:22 AM, Marc Zyngier wrote: >> 2. The kernel will not call idu_irq_set_affinity() for IDU interrupt >> > controller in some cases. It happens when the top interrupt >> > controller does not support setting of the affinity and does not even >> > support propagating of it (e.g. a GPIO