Hi,
On 24.02.2016 13:42, Geert Uytterhoeven wrote:
With CONFIG_DMA_API_DEBUG=y, I sometimes get the below warning
on r8a7795/salvator-x. My tree is based on renesas-drivers-2016-02-23-v4.5-rc5.
Some weeks ago I've had a look at porting the eMMC support from the
4.2 Renesas BSP to the 4.4
Hello,
On Mon, Feb 29, 2016 at 02:44:16PM +0100, Geert Uytterhoeven wrote:
> sata_rcar ee30.sata: DMA-API: cpu touching an active dma mapped
> cacheline [cln=0x0090ff40]
> [ cut here ]
> WARNING: at lib/dma-debug.c:604
> Modules linked in:
>
> CPU: 2 PID: 329
Hi Tejun,
On Fri, Feb 26, 2016 at 9:21 AM, Geert Uytterhoeven
wrote:
> On Thu, Feb 25, 2016 at 10:42 PM, Tejun Heo wrote:
>> On Thu, Feb 25, 2016 at 4:40 PM, Tejun Heo wrote:
>>> Is this the problem fixed by the following patch from
Hi Tejun,
On Thu, Feb 25, 2016 at 10:42 PM, Tejun Heo wrote:
> On Thu, Feb 25, 2016 at 4:40 PM, Tejun Heo wrote:
>> Is this the problem fixed by the following patch from Harvey?
>>
>>
>>
On Thu, Feb 25, 2016 at 4:40 PM, Tejun Heo wrote:
> Is this the problem fixed by the following patch from Harvey?
>
>
> http://lkml.kernel.org/g/CAMuHMdU0=_TJVfy=-zxwhkfjswh_fjulbrl8j9t60qs48wb...@mail.gmail.com
Oops, I meant
Hello,
cc'ing Harvey.
On Wed, Feb 24, 2016 at 01:42:33PM +0100, Geert Uytterhoeven wrote:
> With CONFIG_DMA_API_DEBUG=y, I sometimes get the below warning
> on r8a7795/salvator-x. My tree is based on
> renesas-drivers-2016-02-23-v4.5-rc5.
>
> sata_rcar ee30.sata: DMA-API: cpu touching an