On Wed, 17 Oct 2018 09:10:45 +0200 Boris Brezillon <boris.brezillon@xxxxxxxxxxx> wrote: > On Wed, 17 Oct 2018 09:07:24 +0200 > Boris Brezillon <boris.brezillon@xxxxxxxxxxx> wrote: > > > On Wed, 17 Oct 2018 02:07:43 +0000 > > Yogesh Narayan Gaur <yogeshnarayan.gaur@xxxxxxx> wrote: > > > > > > > > > Actually there is no entry of s25fs512s in current spi-nor.c file. > > > For my connected flash part, jedec ID read points to s25fl512s. I > > > have asked my board team to confirm the name of exact connected flash > > > part. When I check the data sheet of s25fs512s, it also points to the > > > same Jedec ID information. { "s25fl512s", INFO(0x010220, 0x4d00, 256 > > > * 1024, 256, ....} > > > > > > But as stated earlier, if I skip reading SFDP or read using 1-1-1 > > > protocol then read are always correct. For 1-4-4 protocol read are > > > wrong and on further debugging found that Read code of 0x6C is being > > > send as opcode instead of 0xEC. > > > > > > If I revert this patch, reads are working fine. > > > > Can you try with the following patch? > > > > Hm, nevermind. The problem is actually not related to 4B vs non-4B mode > but 1-1-4 vs 1-4-4 modes. > Can you try with this patch applied? --->8--- diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c index 9407ca5f9443..cf33d834698c 100644 --- a/drivers/mtd/spi-nor/spi-nor.c +++ b/drivers/mtd/spi-nor/spi-nor.c @@ -3132,6 +3132,17 @@ static int spi_nor_parse_sfdp(struct spi_nor *nor, switch (SFDP_PARAM_HEADER_ID(param_header)) { case SFDP_SECTOR_MAP_ID: err = spi_nor_parse_smpt(nor, param_header); + if (err) { + dev_warn(dev, + "failed to parse SMPT (err = %d)\n", + err); + /* + * SMPT parsing is optional, let's not drop + * all information we extracted so far just + * because it failed. + */ + err = 0; + } break; default: ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/