All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Yadav <p.yadav@ti.com>
To: u-boot@lists.denx.de
Subject: [PATCH v8 26/28] mtd: spi-nor-core: Add non-uniform erase for Spansion/Cypress
Date: Tue, 6 Apr 2021 16:16:29 +0530	[thread overview]
Message-ID: <20210406104627.qg22m6v7pnb36trk@ti.com> (raw)
In-Reply-To: <79ab6036-a87b-5c3e-7dd0-2c4b76325e59@gmail.com>

On 06/04/21 10:48AM, Takahiro Kuwano wrote:
> On 4/2/2021 4:31 AM, Pratyush Yadav wrote:
> > From: Takahiro Kuwano <Takahiro.Kuwano@infineon.com>
> > 
> > Some of Spansion/Cypress chips have overlaid 4KB sectors at top and/or
> > bottom, depending on the device configuration, while U-Boot supports
> > uniform sector layout only.
> > 
> > The spansion_erase_non_uniform()  erases overlaid 4KB sectors,
> > non-overlaid portion of normal sector, and remaining normal sectors, by
> > selecting correct erase command and size based on the address to erase
> > and size of overlaid portion in parameters. Since different Spansion
> > flashes can use different opcode for erasing the 4K sectors, the opcode
> > must pe passed in as a parameter based on the flash being used.
> > 
> Typo: "must be passed"

Ok.

> 
> > Signed-off-by: Takahiro Kuwano <Takahiro.Kuwano@infineon.com>
> > Signed-off-by: Pratyush Yadav <p.yadav@ti.com>
> > [p.yadav at ti.com: Refactor the function to be compatible with nor->erase,
> > make 4K opcode customizable, call spi_nor_setup_op() before executing
> > the op.]
> > ---
> > 
> Thank you for refactoring. I would like to take this for the next revision
> of my series. I think I need to remove spi_nor_setup_op() for my series.

Yes. It is unfortunate that our series have such interdependency between 
them.

Jagan, which one do you think is more mature and more likely to go in 
first? That can help clear up the dependencies a bit. I also don't mind 
if you take in the "infrastructure" patches first (patches 9-14) to 
clear up the dependencies for Takahiro's series and then take the DTR 
patches later. Of course, if you feel like this series is good enough to 
go in then take them all at the same time ;-)

> 
> > Unfortunately there is a race between this and Takahiro's series [0].
> > Some of his patches depend on this series and I am taking this patch
> > from his series. Not sure how to resolve this problem but I figure it is
> > worth pointing out.
> > 
> > BTW, I changed the #ifdef to CONFIG_SPI_FLASH_S28HS512T instead of
> > CONFIG_SPI_FLASH_SPANSION otherwise there would be build warnings when
> > the S28 config is not enabled. Once Takahiro's series lands it should be
> > changed back to CONFIG_SPI_FLASH_SPANSION.
> > 
> > [0] https://patchwork.ozlabs.org/project/uboot/list/?series=230084&archive=both&state=*
> > 
> >  drivers/mtd/spi/spi-nor-core.c | 61 ++++++++++++++++++++++++++++++++++
> >  1 file changed, 61 insertions(+)
> > 
> > --
> > 2.30.0
> > 
> > diff --git a/drivers/mtd/spi/spi-nor-core.c b/drivers/mtd/spi/spi-nor-core.c
> > index 8934d65ce2..7637539087 100644
> > --- a/drivers/mtd/spi/spi-nor-core.c
> > +++ b/drivers/mtd/spi/spi-nor-core.c
> > @@ -887,6 +887,67 @@ erase_err:
> >  	return ret;
> >  }
> > 
> > +#ifdef CONFIG_SPI_FLASH_S28HS512T
> > +/**
> > + * spansion_erase_non_uniform() - erase non-uniform sectors for Spansion/Cypress
> > + *                                chips
> > + * @nor:	pointer to a 'struct spi_nor'
> > + * @addr:	address of the sector to erase
> > + * @opcode_4k:	opcode for 4K sector erase
> > + * @ovlsz_top:	size of overlaid portion at the top address
> > + * @ovlsz_btm:	size of overlaid portion at the bottom address
> > + *
> > + * Erase an address range on the nor chip that can contain 4KB sectors overlaid
> > + * on top and/or bottom. The appropriate erase opcode and size are chosen by
> > + * address to erase and size of overlaid portion.
> > + *
> > + * Return: number of bytes erased on success, -errno otherwise.
> > + */
> > +static int spansion_erase_non_uniform(struct spi_nor *nor, u32 addr,
> > +				      u8 opcode_4k, u32 ovlsz_top,
> > +				      u32 ovlsz_btm)
> > +{
> > +	struct spi_mem_op op =
> > +		SPI_MEM_OP(SPI_MEM_OP_CMD(nor->erase_opcode, 0),
> > +			   SPI_MEM_OP_ADDR(nor->addr_width, addr, 0),
> > +			   SPI_MEM_OP_NO_DUMMY,
> > +			   SPI_MEM_OP_NO_DATA);
> > +	struct mtd_info *mtd = &nor->mtd;
> > +	u32 erasesize;
> > +	int ret;
> > +
> > +	/* 4KB sectors */
> > +	if (op.addr.val < ovlsz_btm ||
> > +	    op.addr.val >= mtd->size - ovlsz_top) {
> > +		op.cmd.opcode = opcode_4k;
> > +		erasesize = SZ_4K;
> > +
> > +	/* Non-overlaid portion in the normal sector at the bottom */
> > +	} else if (op.addr.val == ovlsz_btm) {
> > +		op.cmd.opcode = nor->erase_opcode;
> > +		erasesize = mtd->erasesize - ovlsz_btm;
> > +
> > +	/* Non-overlaid portion in the normal sector at the top */
> > +	} else if (op.addr.val == mtd->size - mtd->erasesize) {
> > +		op.cmd.opcode = nor->erase_opcode;
> > +		erasesize = mtd->erasesize - ovlsz_top;
> > +
> > +	/* Normal sectors */
> > +	} else {
> > +		op.cmd.opcode = nor->erase_opcode;
> > +		erasesize = mtd->erasesize;
> > +	}
> > +
> > +	spi_nor_setup_op(nor, &op, nor->write_proto);
> > +
> > +	ret = spi_mem_exec_op(nor->spi, &op);
> > +	if (ret)
> > +		return ret;
> > +
> > +	return erasesize;
> > +}
> > +#endif
> > +
> >  #if defined(CONFIG_SPI_FLASH_STMICRO) || defined(CONFIG_SPI_FLASH_SST)
> >  /* Write status register and ensure bits in mask match written values */
> >  static int write_sr_and_check(struct spi_nor *nor, u8 status_new, u8 mask)
> > 
> 
> Best Regards,
> Takahiro

-- 
Regards,
Pratyush Yadav
Texas Instruments Inc.

  reply	other threads:[~2021-04-06 10:46 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01 19:31 [PATCH v8 00/28] mtd: spi-nor-core: add xSPI Octal DTR support Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 01/28] spi: spi-mem: allow specifying whether an op is DTR or not Pratyush Yadav
2021-04-02 22:21   ` Sean Anderson
2021-04-05  8:25     ` Pratyush Yadav
2021-04-05 11:47       ` Tom Rini
2021-04-05 13:12         ` Sean Anderson
2021-04-05 13:57           ` Pratyush Yadav
2021-04-05 14:58             ` Tom Rini
2021-04-01 19:31 ` [PATCH v8 02/28] spi: spi-mem: allow specifying a command's extension Pratyush Yadav
2021-04-02 22:29   ` Sean Anderson
2021-04-05  8:18     ` Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 03/28] spi: spi-mem: export spi_mem_default_supports_op() Pratyush Yadav
2021-04-02 22:09   ` Sean Anderson
2021-04-01 19:31 ` [PATCH v8 04/28] spi: spi-mem: add spi_mem_dtr_supports_op() Pratyush Yadav
2021-04-02 22:31   ` Sean Anderson
2021-04-05  7:40     ` Pratyush Yadav
2021-04-05 13:16       ` Sean Anderson
2021-04-01 19:31 ` [PATCH v8 05/28] spi: cadence-qspi: Do not calibrate when device tree sets read delay Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 06/28] spi: cadence-qspi: Add a small delay before indirect writes Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 07/28] spi: cadence-qspi: Add support for octal DTR flashes Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 08/28] arm: mvebu: x530: Use tiny SPI NOR Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 09/28] mtd: spi-nor-core: Fix address width on flash chips > 16MB Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 10/28] mtd: spi-nor-core: Add a ->setup() hook Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 11/28] mtd: spi-nor-core: Move SFDP related declarations to top Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 12/28] mtd: spi-nor-core: Introduce flash-specific fixup hooks Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 13/28] mtd: spi-nor-core: Rework hwcaps selection Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 14/28] mtd: spi-nor-core: Do not set data direction when there is no data Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 15/28] mtd: spi-nor-core: Add support for DTR protocol Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 16/28] mtd: spi-nor-core: prepare BFPT parsing for JESD216 rev D Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 17/28] mtd: spi-nor-core: Get command opcode extension type from BFPT Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 18/28] mtd: spi-nor-core: Parse xSPI Profile 1.0 table Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 19/28] mtd: spi-nor-core: Prepare Read SR and FSR for Octal DTR mode Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 20/28] mtd: spi-nor-core: Enable octal DTR mode when possible Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 21/28] mtd: spi-nor-core: Do not make invalid quad enable fatal Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 22/28] mtd: spi-nor-core: Detect Soft Reset sequence support from BFPT Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 23/28] mtd: spi-nor-core: Perform a Soft Reset on shutdown Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 24/28] mtd: spi-nor-core: Perform a Soft Reset on boot Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 25/28] mtd: spi-nor-core: allow truncated erases Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 26/28] mtd: spi-nor-core: Add non-uniform erase for Spansion/Cypress Pratyush Yadav
2021-04-06  1:48   ` Takahiro Kuwano
2021-04-06 10:46     ` Pratyush Yadav [this message]
2021-04-01 19:31 ` [PATCH v8 27/28] mtd: spi-nor-core: Add support for Cypress Semper flash Pratyush Yadav
2021-04-01 19:31 ` [PATCH v8 28/28] mtd: spi-nor-core: Allow using Micron mt35xu512aba in Octal DTR mode Pratyush Yadav
2021-04-02 22:28 ` [PATCH v8 00/28] mtd: spi-nor-core: add xSPI Octal DTR support Sean Anderson
2021-04-05  7:43   ` Pratyush Yadav
2021-04-05 13:17     ` Sean Anderson

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=20210406104627.qg22m6v7pnb36trk@ti.com \
    --to=p.yadav@ti.com \
    --cc=u-boot@lists.denx.de \
    /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.