From: Boris Brezillon <boris.brezillon@bootlin.com>
To: James Tomasetta <James.Tomasetta@cypress.com>
Cc: Yogesh Narayan Gaur <yogeshnarayan.gaur@nxp.com>,
Yong Qin <Yong.Qin@cypress.com>,
Tudor Ambarus <tudor.ambarus@microchip.com>,
"cyrille.pitchen@wedev4u.fr" <cyrille.pitchen@wedev4u.fr>,
Jimmy Zhao <jimmy.zhao@nxp.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Pankaj Bansal <pankaj.bansal@nxp.com>
Subject: Re: SPI-NOR FS512S incorrect CR3NV[1] value
Date: Fri, 7 Dec 2018 16:17:03 +0100 [thread overview]
Message-ID: <20181207161703.25efabc5@bbrezillon> (raw)
In-Reply-To: <BN6PR06MB32974DB116D27B9939A23090F6AA0@BN6PR06MB3297.namprd06.prod.outlook.com>
On Fri, 7 Dec 2018 15:02:09 +0000
James Tomasetta <James.Tomasetta@cypress.com> 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.
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.
next prev parent reply other threads:[~2018-12-07 15:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 4:33 FW: SPI-NOR FS512S incorrect CR3NV[1] value Yogesh Narayan Gaur
2018-12-03 7:38 ` Boris Brezillon
2018-12-04 1:37 ` Yong Qin
2018-12-04 9:03 ` Boris Brezillon
2018-12-05 19:21 ` Yong Qin
2018-12-05 19:27 ` Boris Brezillon
2018-12-05 19:29 ` Boris Brezillon
2018-12-05 19:39 ` Yong Qin
2018-12-06 16:30 ` James Tomasetta
2018-12-07 4:37 ` Yogesh Narayan Gaur
2018-12-07 15:02 ` James Tomasetta
2018-12-07 15:17 ` Boris Brezillon [this message]
2018-12-17 6:22 ` Pankaj Bansal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181207161703.25efabc5@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=James.Tomasetta@cypress.com \
--cc=Yong.Qin@cypress.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=jimmy.zhao@nxp.com \
--cc=linux-mtd@lists.infradead.org \
--cc=pankaj.bansal@nxp.com \
--cc=tudor.ambarus@microchip.com \
--cc=yogeshnarayan.gaur@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.