[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b108b840-b8f9-2104-25c3-369bf1683e02@emlix.com>
Date: Thu, 19 Sep 2019 13:42:33 +0200
From: Philipp Puschmann <philipp.puschmann@...ix.com>
To: Fabio Estevam <festevam@...il.com>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
Robin Gong <yibin.gong@....com>,
Fugang Duan <fugang.duan@....com>,
Lucas Stach <l.stach@...gutronix.de>,
Dan Williams <dan.j.williams@...el.com>,
Vinod <vkoul@...nel.org>, Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Sascha Hauer <kernel@...gutronix.de>,
NXP Linux Team <linux-imx@....com>, dmaengine@...r.kernel.or,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v3 1/3] dmaengine: imx-sdma: fix buffer ownership
Hi Fabio,
Am 19.09.19 um 13:37 schrieb Fabio Estevam:
> Hi Philipp,
>
> On Thu, Sep 19, 2019 at 7:45 AM Philipp Puschmann
> <philipp.puschmann@...ix.com> wrote:
>>
>> BD_DONE flag marks ownership of the buffer. When 1 SDMA owns the
>> buffer, when 0 ARM owns it. When processing the buffers in
>> sdma_update_channel_loop the ownership of the currently processed
>> buffer was set to SDMA again before running the callback function of
>> the buffer and while the sdma script may be running in parallel. So
>> there was the possibility to get the buffer overwritten by SDMA before
>> it has been processed by kernel leading to kind of random errors in the
>> upper layers, e.g. bluetooth.
>>
>> Fixes: broken since start
>
> The Fixes tag requires a commit ID like this:
>
> Fixes: 1ec1e82f2510 ("dmaengine: Add Freescale i.MX SDMA support")
>
> Same applies to the other patch.
>
oh okay, thanks. I will fix this with v4.
Regards,
Philipp
Powered by blists - more mailing lists