[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <14e5ccbe-8275-c316-e3e1-f77461309249@microchip.com>
Date: Wed, 18 May 2022 06:21:36 +0000
From: <Tudor.Ambarus@...rochip.com>
To: <peda@...ntia.se>, <regressions@...mhuis.info>,
<Nicolas.Ferre@...rochip.com>, <alexandre.belloni@...tlin.com>
CC: <du@...ntia.se>, <Patrice.Vilchez@...rochip.com>,
<Cristian.Birsan@...rochip.com>, <Ludovic.Desroches@...rochip.com>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<gregkh@...uxfoundation.org>, <saravanak@...gle.com>
Subject: Re: Regression: memory corruption on Atmel SAMA5D31
On 5/17/22 17:50, Peter Rosin wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> 2022-04-11 at 08:21, Tudor.Ambarus@...rochip.com wrote:
>> There are some concurrency bugs in the at-hdmac (DMA) driver, I'm handling them
>> and will come with a resolution. Disabling the DMA showed the bug is no more
>> reproducible.
>
> Any news?
>
I'm now allocated on this, so I started looking around what has to be done.
I'm thinking of using virt-dma to manage the channels and the request queues.
Will get back to you after I'll have something working.
Cheers,
ta
Powered by blists - more mailing lists