On 3/18/2016 7:25 AM, Robin Murphy wrote:
> On 18/03/16 09:30, Boris Brezillon wrote:
>> On Thu, 17 Mar 2016 23:50:20 +
>> Russell King - ARM Linux wrote:
>>
>>> On Thu, Mar 17, 2016 at 07:17:24PM -0400, ok...@codeaurora.org wrote:
What is the correct way? I don't want to write engine->sr
On 3/18/2016 9:51 AM, Sinan Kaya wrote:
> Another option is I can write
>
> engine->sram_dma = swiotlb_dma_to_phys(res->start)
I realized that I made a mistake in the commit message and the code above.
The code is trying to find DMA address from physical address. Not the other
way around. I
On Fri, 18 Mar 2016 11:25:48 +
Robin Murphy wrote:
> On 18/03/16 09:30, Boris Brezillon wrote:
> > On Thu, 17 Mar 2016 23:50:20 +
> > Russell King - ARM Linux wrote:
> >
> >> On Thu, Mar 17, 2016 at 07:17:24PM -0400, ok...@codeaurora.org wrote:
> >>> What is the correct way? I don't want
On 18/03/16 09:30, Boris Brezillon wrote:
On Thu, 17 Mar 2016 23:50:20 +
Russell King - ARM Linux wrote:
On Thu, Mar 17, 2016 at 07:17:24PM -0400, ok...@codeaurora.org wrote:
What is the correct way? I don't want to write engine->sram_dma = sram
Well, what the driver _is_ wanting to do
Hi Sinan,
[auto build test ERROR on arm64/for-next/core]
[also build test ERROR on v4.5 next-20160318]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Sinan-Kaya/crypto-marvell-cesa-replace-dma
On 2016-03-17 18:54, Russell King - ARM Linux wrote:
On Thu, Mar 17, 2016 at 06:02:15PM -0400, Sinan Kaya wrote:
Getting ready to remove dma_to_phys API. Drivers should not be
using this API for DMA operations. Instead, they should go
through the dma_map or dma_alloc APIs.
Signed-off-by: Sinan
Getting ready to remove dma_to_phys API. Drivers should not be
using this API for DMA operations. Instead, they should go
through the dma_map or dma_alloc APIs.
Signed-off-by: Sinan Kaya
---
drivers/crypto/marvell/cesa.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dri
On Thu, Mar 17, 2016 at 07:17:24PM -0400, ok...@codeaurora.org wrote:
> What is the correct way? I don't want to write engine->sram_dma = sram
Well, what the driver _is_ wanting to do is to go from a CPU physical
address to a device DMA address. phys_to_dma() looks like the correct
thing there to
On Fri, 18 Mar 2016 09:51:37 -0400
Sinan Kaya wrote:
> On 3/18/2016 7:25 AM, Robin Murphy wrote:
> > On 18/03/16 09:30, Boris Brezillon wrote:
> >> On Thu, 17 Mar 2016 23:50:20 +
> >> Russell King - ARM Linux wrote:
> >>
> >>> On Thu, Mar 17, 2016 at 07:17:24PM -0400, ok...@codeaurora.org wr
On Thu, Mar 17, 2016 at 06:02:15PM -0400, Sinan Kaya wrote:
> Getting ready to remove dma_to_phys API. Drivers should not be
> using this API for DMA operations. Instead, they should go
> through the dma_map or dma_alloc APIs.
>
> Signed-off-by: Sinan Kaya
> ---
> drivers/crypto/marvell/cesa.c |
On Thu, 17 Mar 2016 23:50:20 +
Russell King - ARM Linux wrote:
> On Thu, Mar 17, 2016 at 07:17:24PM -0400, ok...@codeaurora.org wrote:
> > What is the correct way? I don't want to write engine->sram_dma = sram
>
> Well, what the driver _is_ wanting to do is to go from a CPU physical
> addres
On 3/18/2016 10:20 AM, Boris Brezillon wrote:
> On Fri, 18 Mar 2016 09:51:37 -0400
> Sinan Kaya wrote:
>
>> On 3/18/2016 7:25 AM, Robin Murphy wrote:
>>> On 18/03/16 09:30, Boris Brezillon wrote:
On Thu, 17 Mar 2016 23:50:20 +
Russell King - ARM Linux wrote:
> On Thu, Mar
12 matches
Mail list logo
