public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Yadav <p.yadav@ti.com>
To: Ley Foon Tan <leyfoon.tan@linux.starfivetech.com>
Cc: Tudor Ambarus <tudor.ambarus@microchip.com>,
	Michael Walle <michael@walle.cc>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
	Ley Foon Tan <lftan.linux@gmail.com>
Subject: Re: [PATCH] mtd: spi-nor: macronix: Add support for mx66u1g45g
Date: Tue, 25 Jan 2022 15:31:12 +0530	[thread overview]
Message-ID: <20220125100112.jevrd4knhxytmry2@ti.com> (raw)
In-Reply-To: <20220124060225.149007-1-leyfoon.tan@linux.starfivetech.com>

Hi,

On 24/01/22 02:02PM, Ley Foon Tan wrote:
> The Macronix mx66u1g45g [1] is a 1.8V, 1Gbit (128MB) flash device that
> supports x1, x2, or x4 operation.
> 
> The mx66u1g45g is the smaller sibling of the mx66u2g45g that is
> already supported.
> 
> Tested on StarFive Dubhe hardware on FPGA.
> Validated by erase and read back, write and read back.
> 
> [1] https://www.macronix.com/Lists/Datasheet/Attachments/7877/MX66U1G45G,%201.8V,%201Gb,%20v1.4.pdf
> 
> Signed-off-by: Ley Foon Tan <leyfoon.tan@linux.starfivetech.com>
> ---
>  drivers/mtd/spi-nor/macronix.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/mtd/spi-nor/macronix.c b/drivers/mtd/spi-nor/macronix.c
> index 97dba1ae7fb1..79ee808c5442 100644
> --- a/drivers/mtd/spi-nor/macronix.c
> +++ b/drivers/mtd/spi-nor/macronix.c
> @@ -97,6 +97,9 @@ static const struct flash_info macronix_parts[] = {
>  			      SPI_NOR_QUAD_READ) },
>  	{ "mx66l1g55g",  INFO(0xc2261b, 0, 64 * 1024, 2048)
>  		NO_SFDP_FLAGS(SPI_NOR_QUAD_READ) },
> +	{ "mx66u1g45g",  INFO(0xc2253b, 0, 64 * 1024, 2048)
> +		NO_SFDP_FLAGS(SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ)
> +		FIXUP_FLAGS(SPI_NOR_4B_OPCODES) },

This is the "legacy" way of defining flags. I see from the datasheet 
that SFDP is supported. Please use PARSE_SFDP to allow these parameters 
to be discovered via SFDP. If one of the SFDP table has wrong data then 
please use fixup hooks to correct it.

You also need to dump the SFDP table and some other flash parameters in 
the patch comments. See [0] for an example.

[0] https://patchwork.ozlabs.org/project/linux-mtd/patch/20211209190436.401946-2-tudor.ambarus@microchip.com/

>  	{ "mx66u2g45g",	 INFO(0xc2253c, 0, 64 * 1024, 4096)
>  		NO_SFDP_FLAGS(SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ)
>  		FIXUP_FLAGS(SPI_NOR_4B_OPCODES) },
> -- 
> 2.25.1
> 
> 

-- 
Regards,
Pratyush Yadav
Texas Instruments Inc.

  reply	other threads:[~2022-01-25 10:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24  6:02 [PATCH] mtd: spi-nor: macronix: Add support for mx66u1g45g Ley Foon Tan
2022-01-25 10:01 ` Pratyush Yadav [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-09-16  8:22 niravkumar.l.rabara
2022-11-09 20:23 Dinh Nguyen
2022-11-09 20:23 ` Dinh Nguyen
2022-11-10 17:38   ` kernel test robot

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=20220125100112.jevrd4knhxytmry2@ti.com \
    --to=p.yadav@ti.com \
    --cc=leyfoon.tan@linux.starfivetech.com \
    --cc=lftan.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=michael@walle.cc \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=tudor.ambarus@microchip.com \
    --cc=vigneshr@ti.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