From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Jaime Liao <jaimeliao.tw@gmail.com>,
linux-mtd@lists.infradead.org, pratyush@kernel.org,
michael@walle.cc, miquel.raynal@bootlin.com
Cc: leoyu@mxic.com.tw
Subject: Re: [PATCH v1 1/3] mtd: spi-nor: Modify rule for parse sfdp
Date: Thu, 13 Jul 2023 12:25:38 +0100 [thread overview]
Message-ID: <76b5a9e6-bf90-e63f-0669-502bba0bd0dd@linaro.org> (raw)
In-Reply-To: <20230713105058.101321-2-jaimeliao.tw@gmail.com>
On 7/13/23 11:50, Jaime Liao wrote:
> With various vendors adhering to the JEDEC Standard, the percentage
> of SPI-NOR flash devices on the market that can read SFDP table is
> increasing.
> To enhance reliance on SFDP table, remove PARSE_SFDP flag,
> allowing all SPI-NOR flash devices to read SFDP talbe. The exception
> to this ule is for ICs that included SPI_NOR_SKIP_SFDP flag.
> Furthermore, to establish a complementary relationship between ID
> table information and SFDP talbe, organize no_sfdp_flags into
> nor->info->flags.
> The flash parameters are then organized by spi_nor_init_flags.
what are you trying to achieve?
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2023-07-13 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 10:50 [PATCH v1 0/3] mtd: spi-nor: Modify rule of parse SFDP Jaime Liao
2023-07-13 10:50 ` [PATCH v1 1/3] mtd: spi-nor: Modify rule for parse sfdp Jaime Liao
2023-07-13 11:25 ` Tudor Ambarus [this message]
2023-07-17 1:10 ` liao jaime
2023-07-13 10:50 ` [PATCH v1 2/3] mtd: spi-nor: Add features support by " Jaime Liao
2023-07-13 10:50 ` [PATCH v1 3/3] mtd: spi-nor: change MACRO for flash ID tables Jaime Liao
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=76b5a9e6-bf90-e63f-0669-502bba0bd0dd@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=jaimeliao.tw@gmail.com \
--cc=leoyu@mxic.com.tw \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=pratyush@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox