From: Tudor Ambarus <tudor.ambarus@microchip.com> To: <p.yadav@ti.com>, <michael@walle.cc> Cc: <miquel.raynal@bootlin.com>, <richard@nod.at>, <vigneshr@ti.com>, <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>, <nicolas.ferre@microchip.com>, Tudor Ambarus <tudor.ambarus@microchip.com> Subject: [PATCH v2 0/4] mtd: spi-nor: Parse BFPT to determine the 4-Byte Address Mode Date: Wed, 9 Mar 2022 16:42:11 +0200 [thread overview] Message-ID: <20220309144215.179449-1-tudor.ambarus@microchip.com> (raw) Get the 4-Byte Address mode method from BFPT and favor it in the detriment of the "default" set_4byte_addr_mode method or the methods set by vendors. This may introduce some regressions if flashes have wrong BFPT data. The fix is to introduce post_bfpt() hooks and fix where needed. We should let the core/sfdp do the params initialization, and do vendor specific updates just where needed. This patch set depends on: https://lore.kernel.org/lkml/20220304093011.198173-1-tudor.ambarus@microchip.com/ which depends on: https://lore.kernel.org/lkml/20220228111712.111737-1-tudor.ambarus@microchip.com/ You can find a branch containing the entire chain at: git@github.com:ambarus/linux-0day.git spi-nor/next-bfpt-4byte-addr v2: drop quad enable patch Tudor Ambarus (4): mtd: spi-nor: Parse BFPT to determine the 4-Byte Address Mode methods mtd: spi-nor: Update name and description of the set_4byte_addr_mode BFPT methods mtd: spi-nor: Favor the BFPT-parsed set_4byte_addr_mode method mtd: spi-nor: sfdp: Keep SFDP definitions private drivers/mtd/spi-nor/core.c | 70 +---------- drivers/mtd/spi-nor/core.h | 1 - drivers/mtd/spi-nor/macronix.c | 9 +- drivers/mtd/spi-nor/micron-st.c | 32 +---- drivers/mtd/spi-nor/sfdp.c | 199 ++++++++++++++++++++++++++++++++ drivers/mtd/spi-nor/sfdp.h | 57 +-------- drivers/mtd/spi-nor/winbond.c | 18 +-- 7 files changed, 234 insertions(+), 152 deletions(-) -- 2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Tudor Ambarus <tudor.ambarus@microchip.com> To: <p.yadav@ti.com>, <michael@walle.cc> Cc: <miquel.raynal@bootlin.com>, <richard@nod.at>, <vigneshr@ti.com>, <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>, <nicolas.ferre@microchip.com>, Tudor Ambarus <tudor.ambarus@microchip.com> Subject: [PATCH v2 0/4] mtd: spi-nor: Parse BFPT to determine the 4-Byte Address Mode Date: Wed, 9 Mar 2022 16:42:11 +0200 [thread overview] Message-ID: <20220309144215.179449-1-tudor.ambarus@microchip.com> (raw) Get the 4-Byte Address mode method from BFPT and favor it in the detriment of the "default" set_4byte_addr_mode method or the methods set by vendors. This may introduce some regressions if flashes have wrong BFPT data. The fix is to introduce post_bfpt() hooks and fix where needed. We should let the core/sfdp do the params initialization, and do vendor specific updates just where needed. This patch set depends on: https://lore.kernel.org/lkml/20220304093011.198173-1-tudor.ambarus@microchip.com/ which depends on: https://lore.kernel.org/lkml/20220228111712.111737-1-tudor.ambarus@microchip.com/ You can find a branch containing the entire chain at: git@github.com:ambarus/linux-0day.git spi-nor/next-bfpt-4byte-addr v2: drop quad enable patch Tudor Ambarus (4): mtd: spi-nor: Parse BFPT to determine the 4-Byte Address Mode methods mtd: spi-nor: Update name and description of the set_4byte_addr_mode BFPT methods mtd: spi-nor: Favor the BFPT-parsed set_4byte_addr_mode method mtd: spi-nor: sfdp: Keep SFDP definitions private drivers/mtd/spi-nor/core.c | 70 +---------- drivers/mtd/spi-nor/core.h | 1 - drivers/mtd/spi-nor/macronix.c | 9 +- drivers/mtd/spi-nor/micron-st.c | 32 +---- drivers/mtd/spi-nor/sfdp.c | 199 ++++++++++++++++++++++++++++++++ drivers/mtd/spi-nor/sfdp.h | 57 +-------- drivers/mtd/spi-nor/winbond.c | 18 +-- 7 files changed, 234 insertions(+), 152 deletions(-) -- 2.25.1 ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2022-03-09 14:42 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-09 14:42 Tudor Ambarus [this message] 2022-03-09 14:42 ` [PATCH v2 0/4] mtd: spi-nor: Parse BFPT to determine the 4-Byte Address Mode Tudor Ambarus 2022-03-09 14:42 ` [PATCH v2 1/4] mtd: spi-nor: Parse BFPT to determine the 4-Byte Address Mode methods Tudor Ambarus 2022-03-09 14:42 ` Tudor Ambarus 2022-04-01 10:54 ` Pratyush Yadav 2022-04-01 10:54 ` Pratyush Yadav 2022-03-09 14:42 ` [PATCH v2 2/4] mtd: spi-nor: Update name and description of the set_4byte_addr_mode BFPT methods Tudor Ambarus 2022-03-09 14:42 ` Tudor Ambarus 2022-04-01 12:26 ` Pratyush Yadav 2022-04-01 12:26 ` Pratyush Yadav 2022-03-09 14:42 ` [PATCH v2 3/4] mtd: spi-nor: Favor the BFPT-parsed set_4byte_addr_mode method Tudor Ambarus 2022-03-09 14:42 ` Tudor Ambarus 2022-04-01 19:55 ` Pratyush Yadav 2022-04-01 19:55 ` Pratyush Yadav 2022-03-09 14:42 ` [PATCH v2 4/4] mtd: spi-nor: sfdp: Keep SFDP definitions private Tudor Ambarus 2022-03-09 14:42 ` Tudor Ambarus 2022-04-01 20:01 ` Pratyush Yadav 2022-04-01 20:01 ` Pratyush Yadav 2022-04-04 6:19 ` Tudor.Ambarus 2022-04-04 6:19 ` Tudor.Ambarus 2022-04-05 19:31 ` Pratyush Yadav 2022-04-05 19:31 ` Pratyush Yadav 2022-04-06 10:31 ` Michael Walle 2022-04-06 10:31 ` Michael Walle 2022-04-06 11:10 ` Tudor.Ambarus 2022-04-06 11:10 ` Tudor.Ambarus 2022-04-06 12:17 ` Pratyush Yadav 2022-04-06 12:17 ` Pratyush Yadav
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=20220309144215.179449-1-tudor.ambarus@microchip.com \ --to=tudor.ambarus@microchip.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mtd@lists.infradead.org \ --cc=michael@walle.cc \ --cc=miquel.raynal@bootlin.com \ --cc=nicolas.ferre@microchip.com \ --cc=p.yadav@ti.com \ --cc=richard@nod.at \ --cc=vigneshr@ti.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: linkBe 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.