RE: SPI-NOR FS512S incorrect CR3NV[1] value

[Pankaj Bansal <pankaj.bansal@xxxxxxx>]

Hi James,

> -----Original Message-----
> From: Boris Brezillon [mailto:boris.brezillon@xxxxxxxxxxx]
> Sent: Friday, December 7, 2018 8:47 PM
> To: James Tomasetta <James.Tomasetta@xxxxxxxxxxx>
> Cc: Yogesh Narayan Gaur <yogeshnarayan.gaur@xxxxxxx>; Yong Qin
> <Yong.Qin@xxxxxxxxxxx>; Tudor Ambarus <tudor.ambarus@xxxxxxxxxxxxx>;
> cyrille.pitchen@xxxxxxxxxx; Jimmy Zhao <jimmy.zhao@xxxxxxx>; linux-
> mtd@xxxxxxxxxxxxxxxxxxx; Pankaj Bansal <pankaj.bansal@xxxxxxx>
> Subject: Re: SPI-NOR FS512S incorrect CR3NV[1] value
> 
> On Fri, 7 Dec 2018 15:02:09 +0000
> James Tomasetta <James.Tomasetta@xxxxxxxxxxx> wrote:
> 
> > Yogesh,
> >
> > Attached is the latest CY driver for linux which might help.  It does
> > not use the SFDP.
> 
> Yes, and that's exactly what we are trying to address. SFDP was designed to
> provide a generic way to expose various information (memory organization,
> supported cmdset/features, ...). If manufacturers don't take care when
> populating these tables, we're back to the current situation where everything
> has to be described on a per-chip basis (far from ideal).
> 
> > We are working to see if we can update the default value of the device
> > to 1.

Did you find a way to make the default value of Nonvolatile registers same as SFDP header?
We need it for UEFI boot loader.

> 
> I think it's too late for this part (we'll find a way to fixup the SMPT table at
> runtime). But please be careful next time you design a chip.

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/