[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJsYDVLsBm9pnjd5hbDptXXN3Vd7e=cpuDMc-d-XZ-k46j9ztQ@mail.gmail.com>
Date: Tue, 22 Sep 2020 20:37:02 +0800
From: Chuanhong Guo <gch981213@...il.com>
To: Mark Brown <broonie@...nel.org>
Cc: linux-spi@...r.kernel.org,
Bayi Cheng (程八意)
<bayi.cheng@...iatek.com>, stable@...r.kernel.org,
Matthias Brugger <matthias.bgg@...il.com>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@...ts.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@...ts.infradead.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] spi: spi-mtk-nor: fix timeout calculation overflow
On Tue, Sep 22, 2020 at 8:02 PM Mark Brown <broonie@...nel.org> wrote:
> (which we should pay attention to in the core for flash
> stuff but IIRC we didn't do that yet).
BTW we do have that taken care. spi_mem_adjust_op_size will
adjust the transfer size according to max_transfer/message_size
if no custom adjust_op_size hook is defined in the driver. If a custom
adjust_op_size is defined, the driver adjusts the transfer size for it's
exec_op hook. The size limit between exec_op and transfer_one_message
can be different. (this spi-mtk-nor is an example of that.)
--
Regards,
Chuanhong Guo
Powered by blists - more mailing lists