[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160405213317.GB3873@hector.attlocal.net>
Date: Tue, 5 Apr 2016 16:33:17 -0500
From: Andy Gross <andy.gross@...aro.org>
To: Stanimir Varbanov <stanimir.varbanov@...aro.org>
Cc: linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
dmaengine@...r.kernel.org, Vinod Koul <vinod.koul@...el.com>,
Rob Herring <robh+dt@...nel.org>,
Rob Herring <robh@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Pawel Moll <pawel.moll@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Andy Gross <agross@...eaurora.org>,
Archit Taneja <architt@...eaurora.org>
Subject: Re: [PATCH 0/4] bam dma fixes and one dt extension
On Tue, Dec 01, 2015 at 11:14:55AM +0200, Stanimir Varbanov wrote:
> Here are three bam dma fixes, which I made during testing qcrypto
> driver. The first one is a real fix, the second one is related to
> peripherals on which the BAM IP is initialized by remote execution
> environment, and the third one is a sleeping bug IMO.
>
> The last patch is a extension again for peripherals which BAM is
> remotely controlled by other execution environment.
>
> All patches has been tested on db410c board with apq8016.
>
Stan,
Can you resend these patches w/ updates? Or at least the remote control patch
if you can get that out faster. And also include the dmaengine list.
Regards,
Andy
Powered by blists - more mailing lists