From: Prasanth Mantena <p-mantena@ti.com>
To: Venkatesh Yadav Abbarapu <venkatesh.abbarapu@amd.com>
Cc: <u-boot@lists.denx.de>, <michal.simek@amd.com>,
<jagan@amarulasolutions.com>, <vigneshr@ti.com>,
<u-kumar1@ti.com>, <trini@konsulko.com>, <seanga2@gmail.com>,
<caleb.connolly@linaro.org>, <sjg@chromium.org>,
<william.zhang@broadcom.com>, <stefan_b@posteo.net>,
<quentin.schulz@cherry.de>, <git@amd.com>,
Ashok Reddy Soma <ashok.reddy.soma@xilinx.com>
Subject: Re: [PATCH] mtd: spi-nor: Send write disable cmd after every write enable
Date: Tue, 19 Nov 2024 19:22:22 +0530 [thread overview]
Message-ID: <20241119135222.bpoxymraueeifkcr@prasanth-server> (raw)
In-Reply-To: <20241119063918.12540-1-venkatesh.abbarapu@amd.com>
On 12:09, Venkatesh Yadav Abbarapu wrote:
> Write enable(06h) command will be sent to a flash device to
> set the write enable latch bit before every program, erase,
> write command. After that write disable command (04h) needs
> to be sent to clear the write enable latch.
>
> This write_disable() is missing at the majority of the places
> in the driver, add it to clear write enable latch.
>
> Signed-off-by: Ashok Reddy Soma <ashok.reddy.soma@xilinx.com>
> Signed-off-by: Venkatesh Yadav Abbarapu <venkatesh.abbarapu@amd.com>
> ---
> drivers/mtd/spi/spi-nor-core.c | 23 ++++++++++++++++++++---
> 1 file changed, 20 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/mtd/spi/spi-nor-core.c b/drivers/mtd/spi/spi-nor-core.c
> index ec841fb13b..5977c634c2 100644
> --- a/drivers/mtd/spi/spi-nor-core.c
> +++ b/drivers/mtd/spi/spi-nor-core.c
> @@ -944,6 +944,7 @@ static int spi_nor_erase_chip_wait_till_ready(struct spi_nor *nor, unsigned long
> static int clean_bar(struct spi_nor *nor)
> {
> u8 cmd, bank_sel = 0;
> + int ret;
>
> if (nor->bank_curr == 0)
> return 0;
> @@ -951,7 +952,11 @@ static int clean_bar(struct spi_nor *nor)
> nor->bank_curr = 0;
> write_enable(nor);
>
> - return nor->write_reg(nor, cmd, &bank_sel, 1);
> + ret = nor->write_reg(nor, cmd, &bank_sel, 1);
> + if (ret)
> + return ret;
> +
> + return write_disable(nor);
> }
>
> static int write_bar(struct spi_nor *nor, u32 offset)
> @@ -1270,6 +1275,10 @@ static int write_sr_and_check(struct spi_nor *nor, u8 status_new, u8 mask)
> if (ret)
> return ret;
>
> + ret = write_disable(nor);
> + if (ret)
> + return ret;
> +
> ret = read_sr(nor);
> if (ret < 0)
> return ret;
> @@ -1796,13 +1805,18 @@ static int sst26_lock_ctl(struct spi_nor *nor, loff_t ofs, uint64_t len, enum lo
> if (ctl == SST26_CTL_CHECK)
> return 0;
>
> + /* Write latch enable before write operation */
> + ret = write_enable(nor);
> + if (ret)
> + return ret;
> +
> ret = nor->write_reg(nor, SPINOR_OP_WRITE_BPR, bpr_buff, bpr_size);
> if (ret < 0) {
> dev_err(nor->dev, "fail to write block-protection register\n");
> return ret;
> }
>
> - return 0;
> + return write_disable(nor);
> }
>
> static int sst26_unlock(struct spi_nor *nor, loff_t ofs, uint64_t len)
> @@ -2204,7 +2218,7 @@ static int write_sr_cr(struct spi_nor *nor, u8 *sr_cr)
> return ret;
> }
>
> - return 0;
> + return write_disable(nor);
> }
>
> /**
> @@ -4273,6 +4287,9 @@ static int spi_nor_init(struct spi_nor *nor)
> write_disable(nor);
> }
> }
> + err = write_disable(nor);
> + if (err)
> + return err;
> }
>
> if (nor->quad_enable) {
> --
> 2.17.1
>
>
Tested on j721s2-evm.
Link: https://gist.github.com/PrasanthBabuMantena/c12f39744de188a9d08cd5ca51dc2a7b
Tested-by: Prasanth Babu Mantena <p-mantena@ti.com>
next prev parent reply other threads:[~2024-11-19 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 6:39 [PATCH] mtd: spi-nor: Send write disable cmd after every write enable Venkatesh Yadav Abbarapu
2024-11-19 13:52 ` Prasanth Mantena [this message]
2025-05-06 22:02 ` Tom Rini
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=20241119135222.bpoxymraueeifkcr@prasanth-server \
--to=p-mantena@ti.com \
--cc=ashok.reddy.soma@xilinx.com \
--cc=caleb.connolly@linaro.org \
--cc=git@amd.com \
--cc=jagan@amarulasolutions.com \
--cc=michal.simek@amd.com \
--cc=quentin.schulz@cherry.de \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=stefan_b@posteo.net \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=u-kumar1@ti.com \
--cc=venkatesh.abbarapu@amd.com \
--cc=vigneshr@ti.com \
--cc=william.zhang@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox