| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 8 Oct 2021 16:48:57 +0530
From: Pratyush Yadav <p.yadav@...com>
To: Alexander Stein <Alexander.Stein@...systems.com>
CC: Miquel Raynal <miquel.raynal@...tlin.com>,
Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>,
Rob Herring <robh+dt@...nel.org>,
Michael Walle <michael@...le.cc>,
Tudor Ambarus <tudor.ambarus@...rochip.com>,
Alexander Stein <alexander.stein@...tq-group.com>,
<linux-mtd@...ts.infradead.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] mtd: spi-nor: micron-st: Add support for
output-driver-strength
Hi Alexander,
On 04/10/21 01:15PM, Alexander Stein wrote:
> From: Alexander Stein <alexander.stein@...tq-group.com>
>
> Micron flashes support this by the Bits [2:0] in the Enhanced Volatile
> Configuration Register.
> Checked datasheets:
> - n25q_128mb_3v_65nm.pdf
> - mt25t-qljs-L512-xBA-xxT.pdf
What does changing the impedance do? Does it improve latency? If we use
suboptimal impedance, will the flash still keep working correctly?
In other words, you need to justify why this patch is needed.
>
> Signed-off-by: Alexander Stein <alexander.stein@...tq-group.com>
> ---
> drivers/mtd/spi-nor/micron-st.c | 109 ++++++++++++++++++++++++++++++++
> 1 file changed, 109 insertions(+)
>
> diff --git a/drivers/mtd/spi-nor/micron-st.c b/drivers/mtd/spi-nor/micron-st.c
> index c224e59820a1..5d5e7fbc24a2 100644
> --- a/drivers/mtd/spi-nor/micron-st.c
> +++ b/drivers/mtd/spi-nor/micron-st.c
> @@ -16,6 +16,11 @@
> #define SPINOR_MT_OCT_DTR 0xe7 /* Enable Octal DTR. */
> #define SPINOR_MT_EXSPI 0xff /* Enable Extended SPI (default) */
>
> +struct micron_drive_strength {
> + u32 ohms;
> + u8 val;
> +};
> +
> static int spi_nor_micron_octal_dtr_enable(struct spi_nor *nor, bool enable)
> {
> struct spi_mem_op op;
> @@ -255,8 +260,112 @@ static void micron_st_default_init(struct spi_nor *nor)
> nor->params->set_4byte_addr_mode = st_micron_set_4byte_addr_mode;
> }
>
> +
> +/*
> + * Read Micron enhanced volatile configuration register
> + * Return negative if error occurred or configuration register value
> + */
> +static int micron_read_evcr(struct spi_nor *nor)
> +{
> + int ret;
> +
> + if (nor->spimem) {
> + struct spi_mem_op op =
> + SPI_MEM_OP(SPI_MEM_OP_CMD(SPINOR_OP_RD_EVCR, 1),
> + SPI_MEM_OP_NO_ADDR,
> + SPI_MEM_OP_NO_DUMMY,
> + SPI_MEM_OP_DATA_IN(1, nor->bouncebuf, 1));
Are you always guaranteed to be in 1S-1S-1S mode during register write?
I would suggest calling spi_nor_spimem_setup_op() before this so that it
sets up all the buswidths correctly based on nor->reg_proto.
> +
> + ret = spi_mem_exec_op(nor->spimem, &op);
> + } else {
> + ret = nor->controller_ops->read_reg(nor, SPINOR_OP_RD_EVCR, nor->bouncebuf, 1);
Split into 2 lines?
> + }
> +
> + if (ret < 0) {
> + dev_err(nor->dev, "error %d reading EVCR\n", ret);
> + return ret;
> + }
> +
> + return nor->bouncebuf[0];
> +}
> +
> +/*
> + * Write Micron enhanced volatile configuration register
> + * Return negative if error occurred or configuration register value
> + */
> +static int micron_write_evcr(struct spi_nor *nor, u8 evcr)
> +{
> + nor->bouncebuf[0] = evcr;
> +
> + spi_nor_write_enable(nor);
Check return code.
> +
> + if (nor->spimem) {
> + struct spi_mem_op op =
> + SPI_MEM_OP(SPI_MEM_OP_CMD(SPINOR_OP_WD_EVCR, 1),
> + SPI_MEM_OP_NO_ADDR,
> + SPI_MEM_OP_NO_DUMMY,
> + SPI_MEM_OP_DATA_OUT(1, nor->bouncebuf, 1));
Same as above.
> +
> + return spi_mem_exec_op(nor->spimem, &op);
> + }
> +
> + return nor->controller_ops->write_reg(nor, SPINOR_OP_WD_EVCR, nor->bouncebuf, 1);
Same as above. Split into 2 lines?
> +}
> +
> +/*
> + * Supported values from Enahanced Volatile COnfiguration Register (Bits 2:0)
> + */
> +static const struct micron_drive_strength drive_strength_data[] = {
> + { .ohms = 90, .val = 1 },
> + { .ohms = 45, .val = 3 },
> + { .ohms = 20, .val = 5 },
> + { .ohms = 30, .val = 7 },
> +};
> +
> +static struct micron_drive_strength const *micron_st_find_drive_strength_entry(u32 ohms)
> +{
> + int i;
> +
> + for (i = 0; i < ARRAY_SIZE(drive_strength_data); i++) {
> + if (ohms == drive_strength_data[i].ohms)
> + return &drive_strength_data[i];
> + }
> + return NULL;
> +}
> +
> +static void micron_st_post_sfdp(struct spi_nor *nor)
> +{
> + struct device_node *np = spi_nor_get_flash_node(nor);
> + u32 ohms;
> +
> + if (!np)
> + return;
> +
> + if (!of_property_read_u32(np, "output-driver-strength", &ohms)) {
> + struct micron_drive_strength const *entry =
> + micron_st_find_drive_strength_entry(ohms);
> +
> + if (entry) {
> + int evcrr = micron_read_evcr(nor);
> +
> + if (evcrr >= 0) {
This is a bit confusing. Can you instead do:
if (evcrr < 0)
return evcrr;
...
> + u8 evcr = (u8)(evcrr & 0xf8) | entry->val;
Don't use magic numbers. Define a bitmask, preferably using GENMASK().
> +
> + micron_write_evcr(nor, evcr);
Check return code. Do we need to abort flash probe if this fails, or can
we live with it, despite the suboptimal impedance?
> + dev_dbg(nor->dev, "%s: EVCR 0x%x\n", __func__,
> + (u32)micron_read_evcr(nor));
> + }
> + } else {
> + dev_warn(nor->dev,
> + "Invalid output-driver-strength property specified: %u",
> + ohms);
> + }
> + }
> +}
> +
> static const struct spi_nor_fixups micron_st_fixups = {
> .default_init = micron_st_default_init,
> + .post_sfdp = micron_st_post_sfdp,
NACK. Not every Micron flash has the EVCR register. For example, the
Micron MT35 flash family does not have an EVCR and the output drive
strength is programmed in a separate register. Set this only for the
flashes that need this.
> };
>
> const struct spi_nor_manufacturer spi_nor_micron = {
> --
> 2.25.1
>
--
Regards,
Pratyush Yadav
Texas Instruments Inc.
Powered by blists - more mailing lists