>> From: Jaewon
>>
>> There was an alignment mismatch issue for CMA and it was fixed by
>> commit 1cc8e3458b51 ("drivers: of: of_reserved_mem: fixup the alignment with
>> CMA setup").
>> However the way of the commit considers not only dma-contiguous(CMA) but also
>>
>> From: Jaewon
>>
>> There was an alignment mismatch issue for CMA and it was fixed by
>> commit 1cc8e3458b51 ("drivers: of: of_reserved_mem: fixup the alignment with
>> CMA setup").
>> However the way of the commit considers not only dma-contiguous(CMA) but also
>> dma-coherent which has no
On Tue, May 24, 2016 at 11:29 PM, Jaewon Kim wrote:
> From: Jaewon
>
> There was an alignment mismatch issue for CMA and it was fixed by
> commit 1cc8e3458b51 ("drivers: of: of_reserved_mem: fixup the alignment with
> CMA setup").
> However
On Tue, May 24, 2016 at 11:29 PM, Jaewon Kim wrote:
> From: Jaewon
>
> There was an alignment mismatch issue for CMA and it was fixed by
> commit 1cc8e3458b51 ("drivers: of: of_reserved_mem: fixup the alignment with
> CMA setup").
> However the way of the commit considers not only
2016-05-25 12:29 GMT+08:00 Jaewon Kim :
> From: Jaewon
>
> There was an alignment mismatch issue for CMA and it was fixed by
> commit 1cc8e3458b51 ("drivers: of: of_reserved_mem: fixup the alignment with
> CMA setup").
> However the way of the
2016-05-25 12:29 GMT+08:00 Jaewon Kim :
> From: Jaewon
>
> There was an alignment mismatch issue for CMA and it was fixed by
> commit 1cc8e3458b51 ("drivers: of: of_reserved_mem: fixup the alignment with
> CMA setup").
> However the way of the commit considers not only dma-contiguous(CMA) but
>Hello,
>
>
>On 2016-05-25 16:38, Rob Herring wrote:
>> On Tue, May 24, 2016 at 11:29 PM, Jaewon Kim
>> wrote:
>>> From: Jaewon
>>>
>>> There was an alignment mismatch issue for CMA and it was fixed by
>>> commit 1cc8e3458b51 ("drivers: of:
>Hello,
>
>
>On 2016-05-25 16:38, Rob Herring wrote:
>> On Tue, May 24, 2016 at 11:29 PM, Jaewon Kim
>> wrote:
>>> From: Jaewon
>>>
>>> There was an alignment mismatch issue for CMA and it was fixed by
>>> commit 1cc8e3458b51 ("drivers: of: of_reserved_mem: fixup the alignment
>>> with CMA
Hello,
On 2016-05-25 16:38, Rob Herring wrote:
On Tue, May 24, 2016 at 11:29 PM, Jaewon Kim wrote:
From: Jaewon
There was an alignment mismatch issue for CMA and it was fixed by
commit 1cc8e3458b51 ("drivers: of: of_reserved_mem: fixup
Hello,
On 2016-05-25 16:38, Rob Herring wrote:
On Tue, May 24, 2016 at 11:29 PM, Jaewon Kim wrote:
From: Jaewon
There was an alignment mismatch issue for CMA and it was fixed by
commit 1cc8e3458b51 ("drivers: of: of_reserved_mem: fixup the alignment with CMA
setup").
However the way of
On Tue, May 24, 2016 at 11:29 PM, Jaewon Kim wrote:
> From: Jaewon
>
> There was an alignment mismatch issue for CMA and it was fixed by
> commit 1cc8e3458b51 ("drivers: of: of_reserved_mem: fixup the alignment with
> CMA setup").
> However
On Tue, May 24, 2016 at 11:29 PM, Jaewon Kim wrote:
> From: Jaewon
>
> There was an alignment mismatch issue for CMA and it was fixed by
> commit 1cc8e3458b51 ("drivers: of: of_reserved_mem: fixup the alignment with
> CMA setup").
> However the way of the commit considers not only
From: Jaewon
There was an alignment mismatch issue for CMA and it was fixed by
commit 1cc8e3458b51 ("drivers: of: of_reserved_mem: fixup the alignment with
CMA setup").
However the way of the commit considers not only dma-contiguous(CMA) but also
dma-coherent which has
From: Jaewon
There was an alignment mismatch issue for CMA and it was fixed by
commit 1cc8e3458b51 ("drivers: of: of_reserved_mem: fixup the alignment with
CMA setup").
However the way of the commit considers not only dma-contiguous(CMA) but also
dma-coherent which has no that requirement.
14 matches
Mail list logo