On Wed, Nov 20, 2013 at 4:31 AM, Mark Brown wrote:
> On Mon, Oct 21, 2013 at 06:04:35AM +0900, Kukjin Kim wrote:
>
>> Applied this whole series.
>
> This didn't seem to make it into -next or your tree, it'd be really
> helpful to be able to merge into both ASoC and SPI so they can be used
> for so
On Mon, Oct 21, 2013 at 06:04:35AM +0900, Kukjin Kim wrote:
> Applied this whole series.
This didn't seem to make it into -next or your tree, it'd be really
helpful to be able to merge into both ASoC and SPI so they can be used
for some framework work (I already have some patches for ASoC). Woul
On 10/17/13 19:22, Mark Brown wrote:
On Wed, Oct 16, 2013 at 09:10:51PM +0200, Tomasz Figa wrote:
Since the patches extending support of amba-pl08x DMA engine driver to
PL080S DMA engine (PL080 modified by Samsung) found in Samsung S3C64xx
SoCs got merged into Linux 3.12, it is a good time to mi
On Wed, Oct 16, 2013 at 09:10:51PM +0200, Tomasz Figa wrote:
> Since the patches extending support of amba-pl08x DMA engine driver to
> PL080S DMA engine (PL080 modified by Samsung) found in Samsung S3C64xx
> SoCs got merged into Linux 3.12, it is a good time to migrate the
> platform to use this d
Since the patches extending support of amba-pl08x DMA engine driver to
PL080S DMA engine (PL080 modified by Samsung) found in Samsung S3C64xx
SoCs got merged into Linux 3.12, it is a good time to migrate the
platform to use this driver and drop the legacy DMA code.
Due to changes scattered across
