From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.bootlin.com ([62.4.15.54]) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1gUcry-0007f0-NV for linux-mtd@lists.infradead.org; Wed, 05 Dec 2018 19:30:04 +0000 Date: Wed, 5 Dec 2018 20:29:40 +0100 From: Boris Brezillon To: Yong Qin Cc: Yogesh Narayan Gaur , Tudor Ambarus , "cyrille.pitchen@wedev4u.fr" , James Tomasetta , Jimmy Zhao , "linux-mtd@lists.infradead.org" Subject: Re: SPI-NOR FS512S incorrect CR3NV[1] value Message-ID: <20181205202940.0ba2f25d@bbrezillon> In-Reply-To: <20181205202753.47ebe911@bbrezillon> References: <20181203083814.74662f38@bbrezillon> <20181204100330.28acbecd@bbrezillon> <20181205202753.47ebe911@bbrezillon> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 5 Dec 2018 20:27:53 +0100 Boris Brezillon wrote: > On Wed, 5 Dec 2018 19:21:51 +0000 > Yong Qin wrote: > > > Hi Boris, > > > > Thanks for pointing this out. > > > > Confirmed with our product team, this is the part of datasheet > > discrepancy. Since FS512S only has 256KB sector size option, CR3NV[1] > > is don't care in FS512S and default value is set as 0 in factory. > > > > Column 3 (CR3NV[1]) of table 70 in datasheet will be removed. > > > > For software implementation, if identified the device is FS512S, then > > checking the combination of CR3NV[3] & CR1NV[2] is sufficient to > > decide if the device has top/bottom 4KB sectors, or uniform 256KB > > sectors. > > Again, fixing the datasheet is not enough, the SMPT section on the flash > needs to be fixed too. To be honest, it's already too late for this part, but please try to avoid this sort of mistakes on your future chips.