From: cyrille.pitchen@microchip.com (Cyrille Pitchen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] mtd: spi-nor: add Global Block Unlock support
Date: Wed, 25 Jul 2018 14:26:36 +0200 [thread overview]
Message-ID: <8e0ff8be-34d1-7de9-6120-a067540a75d2@microchip.com> (raw)
In-Reply-To: <20180717162831.17947-1-tudor.ambarus@microchip.com>
Hi Tudor,
Le 17/07/2018 ? 18:28, Tudor Ambarus a ?crit?:
> We can't determine this purely by manufacturer type and it's not
> autodetectable by anything like SFDP, so make a new flag for it:
> UNLOCK_GLOBAL_BLOCK.
>
> Note that the Global Block Unlock command has different names
> depending on the manufacturer, but always the same command value:
> 0x98. Macronix's MX25U12835F names it Gang Block Unlock,
> Winbound's W25Q128FV names it Global Block Unlock and
> Microchip's SST26VF064B names it Global Block Protection Unlock.
>
> Based on initial work done by Anurag Kumar Vulisha:
> https://patchwork.kernel.org/patch/7611271/
>
> Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
Reviewed-by: Cyrille Pitchen <cyrille.pitchen@microchip.com>
Best regards,
Cyrille
> ---
> drivers/mtd/spi-nor/spi-nor.c | 21 +++++++++++++++++++++
> include/linux/mtd/spi-nor.h | 1 +
> 2 files changed, 22 insertions(+)
>
> diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
> index d9c368c..6648251 100644
> --- a/drivers/mtd/spi-nor/spi-nor.c
> +++ b/drivers/mtd/spi-nor/spi-nor.c
> @@ -89,6 +89,7 @@ struct flash_info {
> #define NO_CHIP_ERASE BIT(12) /* Chip does not support chip erase */
> #define SPI_NOR_SKIP_SFDP BIT(13) /* Skip parsing of SFDP tables */
> #define USE_CLSR BIT(14) /* use CLSR command */
> +#define UNLOCK_GLOBAL_BLOCK BIT(15) /* Unlock global block protection */
>
> int (*quad_enable)(struct spi_nor *nor);
> };
> @@ -2730,6 +2731,17 @@ static int spi_nor_setup(struct spi_nor *nor, const struct flash_info *info,
> return 0;
> }
>
> +static int spi_nor_unlock_global_block_protection(struct spi_nor *nor)
> +{
> + int ret;
> +
> + write_enable(nor);
> + ret = nor->write_reg(nor, SPINOR_OP_GBULK, NULL, 0);
> + if (ret < 0)
> + return ret;
> + return spi_nor_wait_till_ready(nor);
> +}
> +
> static int spi_nor_init(struct spi_nor *nor)
> {
> int err;
> @@ -2747,6 +2759,15 @@ static int spi_nor_init(struct spi_nor *nor)
> spi_nor_wait_till_ready(nor);
> }
>
> + if (nor->info->flags & UNLOCK_GLOBAL_BLOCK) {
> + err = spi_nor_unlock_global_block_protection(nor);
> + if (err) {
> + dev_err(nor->dev,
> + "Cannot unlock the global block protection\n");
> + return err;
> + }
> + }
> +
> if (nor->quad_enable) {
> err = nor->quad_enable(nor);
> if (err) {
> diff --git a/include/linux/mtd/spi-nor.h b/include/linux/mtd/spi-nor.h
> index e60da0d..e8dd11d 100644
> --- a/include/linux/mtd/spi-nor.h
> +++ b/include/linux/mtd/spi-nor.h
> @@ -64,6 +64,7 @@
> #define SPINOR_OP_CLFSR 0x50 /* Clear flag status register */
> #define SPINOR_OP_RDEAR 0xc8 /* Read Extended Address Register */
> #define SPINOR_OP_WREAR 0xc5 /* Write Extended Address Register */
> +#define SPINOR_OP_GBULK 0x98 /* Global Block Unlock Protection */
>
> /* 4-byte address opcodes - used on Spansion and some Macronix flashes. */
> #define SPINOR_OP_READ_4B 0x13 /* Read data bytes (low frequency) */
>
next prev parent reply other threads:[~2018-07-25 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 16:28 [PATCH 1/3] mtd: spi-nor: add Global Block Unlock support Tudor Ambarus
2018-07-17 16:28 ` [PATCH 2/3] mtd: spi-nor: unlock global block protection on sst26vf064b Tudor Ambarus
2018-07-17 16:28 ` [PATCH 3/3] mtd: spi-nor: add support for Microchip SST26 QSPI flash memories Tudor Ambarus
2018-07-25 12:26 ` Cyrille Pitchen [this message]
2019-02-14 7:25 ` [PATCH 1/3] mtd: spi-nor: add Global Block Unlock support Tudor.Ambarus
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=8e0ff8be-34d1-7de9-6120-a067540a75d2@microchip.com \
--to=cyrille.pitchen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).