[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220309144215.179449-1-tudor.ambarus@microchip.com>
Date: Wed, 9 Mar 2022 16:42:11 +0200
From: Tudor Ambarus <tudor.ambarus@...rochip.com>
To: <p.yadav@...com>, <michael@...le.cc>
CC: <miquel.raynal@...tlin.com>, <richard@....at>, <vigneshr@...com>,
<linux-mtd@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
<nicolas.ferre@...rochip.com>,
Tudor Ambarus <tudor.ambarus@...rochip.com>
Subject: [PATCH v2 0/4] mtd: spi-nor: Parse BFPT to determine the 4-Byte Address Mode
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@...hub.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
Powered by blists - more mailing lists