[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220523101516.29934-1-mark-pk.tsai@mediatek.com>
Date: Mon, 23 May 2022 18:15:16 +0800
From: Mark-PK Tsai <mark-pk.tsai@...iatek.com>
To: <hch@....de>
CC: <bjorn.andersson@...aro.org>, <iommu@...ts.linux-foundation.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>,
<linux-mediatek@...ts.infradead.org>,
<linux-remoteproc@...r.kernel.org>, <m.szyprowski@...sung.com>,
<mark-pk.tsai@...iatek.com>, <mathieu.poirier@...aro.org>,
<matthias.bgg@...il.com>, <robin.murphy@....com>,
<yj.chiang@...iatek.com>
Subject: Re: [PATCH 0/2] dma-mapping, remoteproc: Fix dma_mem leak after rproc_shutdown
> Sigh. In theory drivers should never declare coherent memory like
> this, and there has been some work to fix remoteproc in that regard.
>
> But I guess until that is merged we'll need somthing like this fix.
Hi,
Thanks for your comment.
As I didn't see other fix of this issue, should we use this patch
before the remoteproc work you mentioned is merged?
Powered by blists - more mailing lists