[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <166904273877.104708.18259766810338058949.b4-ty@microchip.com>
Date: Mon, 21 Nov 2022 16:59:04 +0200
From: Tudor Ambarus <tudor.ambarus@...rochip.com>
To: <richard@....at>, <matthias.bgg@...il.com>,
<linux-mtd@...ts.infradead.org>, <miquel.raynal@...tlin.com>,
<pratyush@...nel.org>, <allen-kh.cheng@...iatek.com>,
<vigneshr@...com>, <michael@...le.cc>
CC: Tudor Ambarus <tudor.ambarus@...rochip.com>,
<linux-mediatek@...ts.infradead.org>, <linux-spi@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<Project_Global_Chrome_Upstream_Group@...iatek.com>,
<linux-kernel@...r.kernel.org>, <bayi.cheng@...iatek.com>
Subject: Re: [PATCH] mtd: spi-nor: Fix the number of bytes for the dummy cycles
On Mon, 31 Oct 2022 20:46:33 +0800, Allen-KH Cheng wrote:
> The number of bytes used by spi_nor_spimem_check_readop() may be
> incorrect for the dummy cycles. Since nor->read_dummy is not initialized
> before spi_nor_spimem_adjust_hwcaps().
>
> We use both mode and wait state clock cycles instead of nor->read_dummy.
>
>
> [...]
Applied to spi-nor/next, thanks!
[1/1] mtd: spi-nor: Fix the number of bytes for the dummy cycles
https://git.kernel.org/mtd/c/fdc20370d93e
Best regards,
--
Tudor Ambarus <tudor.ambarus@...rochip.com>
Powered by blists - more mailing lists