From: Vignesh R <vigneshr@ti.com>
To: Yogesh Narayan Gaur <yogeshnarayan.gaur@nxp.com>,
Boris Brezillon <boris.brezillon@bootlin.com>,
Marek Vasut <marek.vasut@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Brian Norris <computersforpeace@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/3] mtd: spi-nor: Add Octal mode support for mt35xu512aba
Date: Thu, 4 Oct 2018 16:08:31 +0530 [thread overview]
Message-ID: <ad1e560a-9dc8-c99c-acf4-de8be00b934e@ti.com> (raw)
In-Reply-To: <VI1PR04MB1038C20CA97E453FC4C9CEAE99EA0@VI1PR04MB1038.eurprd04.prod.outlook.com>
Hi,
On Thursday 04 October 2018 12:21 PM, Yogesh Narayan Gaur wrote:
> Hi Vignesh,
>
>> -----Original Message-----
>> From: Vignesh R [mailto:vigneshr@ti.com]
>> Sent: Wednesday, October 3, 2018 10:26 PM
>> To: Boris Brezillon <boris.brezillon@bootlin.com>; Marek Vasut
>> <marek.vasut@gmail.com>; Rob Herring <robh+dt@kernel.org>
>> Cc: Brian Norris <computersforpeace@gmail.com>; Yogesh Narayan Gaur
>> <yogeshnarayan.gaur@nxp.com>; Linux ARM Mailing List <linux-arm-
>> kernel@lists.infradead.org>; linux-mtd@lists.infradead.org;
>> devicetree@vger.kernel.org; linux-kernel@vger.kernel.org; Vignesh R
>> <vigneshr@ti.com>
>> Subject: [PATCH 1/3] mtd: spi-nor: Add Octal mode support for mt35xu512aba
>>
>> Micron's mt35xu512aba flash is an Octal flash that has x8 IO lines. It supports
>> read/write over 8 IO lines simulatenously. Add support for Octal read mode for
>> Micron mt35xu512aba.
>> Unfortunately, this flash is only complaint to SFDP JESD216B and does not seem
>> to support newer JESD216C standard that provides auto detection of Octal
>> mode capabilities and opcodes. Therefore, this capability is manually added
>> using new SPI_NOR_OCTAL_READ flag.
>>
>
> Thanks for sending the patch-set of adding octal support.
> If possible, can you share the MT35x datasheet?
>
I dont have datasheet, this patch is based on prior patches from here:
http://patchwork.ozlabs.org/patch/740942/
> I also have the patch ready in which I have added support for Read (1-1-8 and 1-8-8) protocol and Write (1-1-8 and 1-8-8).
> Also have added support of Octal in driver/spi/spi.c framework.
>
> IMO, we would collaborate our patches.
That would be great, thanks!
Regards
Vignesh
> --
> Regards
> Yogesh Gaur
>
>> Signed-off-by: Vignesh R <vigneshr@ti.com>
>> ---
>> drivers/mtd/spi-nor/spi-nor.c | 11 ++++++++++-
>> include/linux/mtd/spi-nor.h | 2 ++
>> 2 files changed, 12 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c index
>> aff5e6ff0b2c..4926e805a8cb 100644
>> --- a/drivers/mtd/spi-nor/spi-nor.c
>> +++ b/drivers/mtd/spi-nor/spi-nor.c
>> @@ -90,6 +90,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 SPI_NOR_OCTAL_READ BIT(15) /* Flash supports Octal Read */
>>
>> int (*quad_enable)(struct spi_nor *nor);
>> };
>> @@ -209,6 +210,7 @@ static inline u8 spi_nor_convert_3to4_read(u8 opcode)
>> { SPINOR_OP_READ_1_2_2, SPINOR_OP_READ_1_2_2_4B },
>> { SPINOR_OP_READ_1_1_4, SPINOR_OP_READ_1_1_4_4B },
>> { SPINOR_OP_READ_1_4_4, SPINOR_OP_READ_1_4_4_4B },
>> + { SPINOR_OP_READ_1_1_8, SPINOR_OP_READ_1_1_8_4B },
>>
>> { SPINOR_OP_READ_1_1_1_DTR,
>> SPINOR_OP_READ_1_1_1_DTR_4B },
>> { SPINOR_OP_READ_1_2_2_DTR,
>> SPINOR_OP_READ_1_2_2_DTR_4B },
>> @@ -1406,7 +1408,7 @@ static const struct flash_info spi_nor_ids[] = {
>> { "mt25qu02g", INFO(0x20bb22, 0, 64 * 1024, 4096, SECT_4K |
>> USE_FSR | SPI_NOR_QUAD_READ | NO_CHIP_ERASE) },
>>
>> /* Micron */
>> - { "mt35xu512aba", INFO(0x2c5b1a, 0, 128 * 1024, 512, SECT_4K |
>> USE_FSR | SPI_NOR_4B_OPCODES) },
>> + { "mt35xu512aba", INFO(0x2c5b1a, 0, 128 * 1024, 512, SECT_4K |
>> USE_FSR
>> +| SPI_NOR_OCTAL_READ | SPI_NOR_4B_OPCODES) },
>>
>> /* PMC */
>> { "pm25lv512", INFO(0, 0, 32 * 1024, 2, SECT_4K_PMC) },
>> @@ -3199,6 +3201,13 @@ static int spi_nor_init_params(struct spi_nor *nor,
>> SNOR_PROTO_1_1_4);
>> }
>>
>> + if (info->flags & SPI_NOR_OCTAL_READ) {
>> + params->hwcaps.mask |= SNOR_HWCAPS_READ_1_1_8;
>> + spi_nor_set_read_settings(¶ms-
>>> reads[SNOR_CMD_READ_1_1_8],
>> + 0, 8, SPINOR_OP_READ_1_1_8,
>> + SNOR_PROTO_1_1_8);
>> + }
>> +
>> /* Page Program settings. */
>> params->hwcaps.mask |= SNOR_HWCAPS_PP;
>> spi_nor_set_pp_settings(¶ms->page_programs[SNOR_CMD_PP],
>> diff --git a/include/linux/mtd/spi-nor.h b/include/linux/mtd/spi-nor.h index
>> 8b1acf68b7ac..ae9861ed7e0f 100644
>> --- a/include/linux/mtd/spi-nor.h
>> +++ b/include/linux/mtd/spi-nor.h
>> @@ -50,6 +50,7 @@
>> #define SPINOR_OP_READ_1_2_2 0xbb /* Read data bytes (Dual I/O
>> SPI) */
>> #define SPINOR_OP_READ_1_1_4 0x6b /* Read data bytes (Quad
>> Output SPI) */
>> #define SPINOR_OP_READ_1_4_4 0xeb /* Read data bytes (Quad I/O
>> SPI) */
>> +#define SPINOR_OP_READ_1_1_8 0x8b /* Read data bytes (Octal
>> Output SPI) */
>> #define SPINOR_OP_PP 0x02 /* Page program (up to 256 bytes) */
>> #define SPINOR_OP_PP_1_1_4 0x32 /* Quad page program */
>> #define SPINOR_OP_PP_1_4_4 0x38 /* Quad page program */
>> @@ -73,6 +74,7 @@
>> #define SPINOR_OP_READ_1_2_2_4B 0xbc /* Read data bytes (Dual I/O
>> SPI) */
>> #define SPINOR_OP_READ_1_1_4_4B 0x6c /* Read data bytes (Quad
>> Output SPI) */
>> #define SPINOR_OP_READ_1_4_4_4B 0xec /* Read data bytes (Quad I/O
>> SPI) */
>> +#define SPINOR_OP_READ_1_1_8_4B 0x7c /* Read data bytes (Octal
>> Output SPI) */
>> #define SPINOR_OP_PP_4B 0x12 /* Page program (up to 256
>> bytes) */
>> #define SPINOR_OP_PP_1_1_4_4B 0x34 /* Quad page program */
>> #define SPINOR_OP_PP_1_4_4_4B 0x3e /* Quad page program */
>> --
>> 2.19.0
>
--
Regards
Vignesh
next prev parent reply other threads:[~2018-10-04 10:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 16:56 [PATCH 0/3] spi-nor: Add Octal SPI support Vignesh R
2018-10-03 16:56 ` [PATCH 1/3] mtd: spi-nor: Add Octal mode support for mt35xu512aba Vignesh R
2018-10-04 6:51 ` Yogesh Narayan Gaur
2018-10-04 7:39 ` Boris Brezillon
2018-10-04 8:47 ` Yogesh Narayan Gaur
2018-10-04 9:10 ` Boris Brezillon
2018-10-04 10:38 ` Vignesh R [this message]
2018-10-04 9:45 ` Boris Brezillon
2018-10-04 11:12 ` Vignesh R
2018-10-04 11:27 ` Boris Brezillon
2018-10-03 16:56 ` [PATCH 2/3] dt-bindings: cadence-quadspi: Add new compatible for AM654 SoC Vignesh R
2018-10-15 19:11 ` Rob Herring
2018-10-03 16:56 ` [PATCH 3/3] mtd: spi-nor: cadence-quadspi: Add support for Octal SPI controller Vignesh R
2018-12-10 8:45 ` Boris Brezillon
2018-12-10 11:19 ` Vignesh R
2018-12-10 11:28 ` Boris Brezillon
2018-10-03 19:20 ` [PATCH 0/3] spi-nor: Add Octal SPI support Boris Brezillon
2018-10-04 10:35 ` Vignesh R
2018-10-04 11:17 ` Boris Brezillon
2018-10-08 15:36 ` Vignesh R
2018-10-12 8:52 ` Boris Brezillon
2018-12-09 8:47 ` Vignesh R
2018-12-10 8:45 ` Boris Brezillon
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=ad1e560a-9dc8-c99c-acf4-de8be00b934e@ti.com \
--to=vigneshr@ti.com \
--cc=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=robh+dt@kernel.org \
--cc=yogeshnarayan.gaur@nxp.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).