From: mdalam@codeaurora.org
To: tudor.ambarus@microchip.com, miquel.raynal@bootlin.com,
richard@nod.at, vigneshr@ti.com, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: sricharan@codeaurora.org
Subject: Re: [PATCH] mtd: spi-nor: gigadevice: Add support for gd25lb256e
Date: Tue, 16 Feb 2021 20:40:04 +0530 [thread overview]
Message-ID: <2df4218ba5ad2a039833bab8c401fa07@codeaurora.org> (raw)
In-Reply-To: <1612869079-19593-1-git-send-email-mdalam@codeaurora.org>
On 2021-02-09 16:41, Md Sadre Alam wrote:
> Add support for gd25lb256e. This device tested on IPQ5018
> platform with dd from/to the flash for read/write respectly,
> and mtd erase for erasing the flash.
>
> Signed-off-by: Md Sadre Alam <mdalam@codeaurora.org>
> ---
> drivers/mtd/spi-nor/gigadevice.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/mtd/spi-nor/gigadevice.c
> b/drivers/mtd/spi-nor/gigadevice.c
> index 447d84b..8f1e7ec 100644
> --- a/drivers/mtd/spi-nor/gigadevice.c
> +++ b/drivers/mtd/spi-nor/gigadevice.c
> @@ -50,6 +50,9 @@ static const struct flash_info gigadevice_parts[] = {
> SPI_NOR_4B_OPCODES | SPI_NOR_HAS_LOCK |
> SPI_NOR_HAS_TB | SPI_NOR_TB_SR_BIT6)
> .fixups = &gd25q256_fixups },
> + { "gd25lb256e", INFO(0xc86719, 0, 64 * 1024, 512,
> + SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ |
> + SPI_NOR_4B_OPCODES) },
> };
>
> const struct spi_nor_manufacturer spi_nor_gigadevice = {
ping! Is there any additional info needed for this ?
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2021-02-16 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 11:11 [PATCH] mtd: spi-nor: gigadevice: Add support for gd25lb256e Md Sadre Alam
2021-02-16 15:10 ` mdalam [this message]
2021-02-16 16:05 ` Tudor.Ambarus
2021-03-08 6:12 ` Tudor.Ambarus
2023-06-13 4:53 ` [PATCH v2] mtd: spi-nor: gigadevice: Add support for gd25lb256 Hao Yao
2023-07-18 17:49 ` 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=2df4218ba5ad2a039833bab8c401fa07@codeaurora.org \
--to=mdalam@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=sricharan@codeaurora.org \
--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;
as well as URLs for NNTP newsgroup(s).