[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <878qqu2bnk.fsf@bootlin.com>
Date: Wed, 29 Jan 2025 10:48:47 +0100
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: "Rabara, Niravkumar L" <niravkumar.l.rabara@...el.com>
Cc: Richard Weinberger <richard@....at>, Vignesh Raghavendra
<vigneshr@...com>, "linux@...blig.org" <linux@...blig.org>, Shen Lichuan
<shenlichuan@...o.com>, Jinjie Ruan <ruanjinjie@...wei.com>,
"u.kleine-koenig@...libre.com" <u.kleine-koenig@...libre.com>,
"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH v2 3/3] mtd: rawnand: cadence: fix incorrect dev context
in dma_unmap_single
Hello,
>> > dma_map_single is using dma_dev->dev, however dma_unmap_single is
>> > using cdns_ctrl->dev, which is incorrect.
>> > Used the correct device context dma_dev->dev for dma_unmap_single.
>>
>> I guess on is the physical/bus device and the other the framework device? It
>> would be nice to clarify this in the commit log.
>>
>
> Noted. Is the commit message below acceptable?
>
> dma_map_single is using physical/bus device (DMA) but dma_unmap_single
> is using framework device(NAND controller), which is incorrect.
> Fixed dma_unmap_single to use correct physical/bus device.
Ok for me.
Thanks,
Miquèl
Powered by blists - more mailing lists