From: <Tudor.Ambarus@microchip.com>
To: <zhengxunli@mxic.com.tw>, <linux-mtd@lists.infradead.org>,
<linux-spi@vger.kernel.org>
Cc: <p.yadav@ti.com>, <miquel.raynal@bootlin.com>,
<broonie@kernel.org>, <jaimeliao@mxic.com.tw>
Subject: Re: [PATCH v5 1/2] mtd: spi-nor: macronix: add support for Macronix octaflash
Date: Tue, 29 Jun 2021 06:37:01 +0000 [thread overview]
Message-ID: <59855ba0-31d8-25b4-3000-ca493a83fe00@microchip.com> (raw)
In-Reply-To: <1621232088-12567-2-git-send-email-zhengxunli@mxic.com.tw>
On 5/17/21 9:14 AM, Zhengxun Li wrote:
> + { "mx66lm1g45g", INFO(0xc2853b, 0, 32 * 1024, 4096,
> + SECT_4K | SPI_NOR_OCTAL_DTR_READ |
> + SPI_NOR_OCTAL_DTR_PP | SPI_NOR_4B_OPCODES)
> + .fixups = &octaflash_fixups },
I have a mx66lm1g45g which does not define SFDP tables, how you'll differentiate
between the two? Mine will fail after reset. I'm working to address the flash ID
collisions, will send patches soon. I won't queue any new flash additions until
we'll solve the ID collisions problem.
WARNING: multiple messages have this Message-ID (diff)
From: <Tudor.Ambarus@microchip.com>
To: <zhengxunli@mxic.com.tw>, <linux-mtd@lists.infradead.org>,
<linux-spi@vger.kernel.org>
Cc: <p.yadav@ti.com>, <miquel.raynal@bootlin.com>,
<broonie@kernel.org>, <jaimeliao@mxic.com.tw>
Subject: Re: [PATCH v5 1/2] mtd: spi-nor: macronix: add support for Macronix octaflash
Date: Tue, 29 Jun 2021 06:37:01 +0000 [thread overview]
Message-ID: <59855ba0-31d8-25b4-3000-ca493a83fe00@microchip.com> (raw)
In-Reply-To: <1621232088-12567-2-git-send-email-zhengxunli@mxic.com.tw>
On 5/17/21 9:14 AM, Zhengxun Li wrote:
> + { "mx66lm1g45g", INFO(0xc2853b, 0, 32 * 1024, 4096,
> + SECT_4K | SPI_NOR_OCTAL_DTR_READ |
> + SPI_NOR_OCTAL_DTR_PP | SPI_NOR_4B_OPCODES)
> + .fixups = &octaflash_fixups },
I have a mx66lm1g45g which does not define SFDP tables, how you'll differentiate
between the two? Mine will fail after reset. I'm working to address the flash ID
collisions, will send patches soon. I won't queue any new flash additions until
we'll solve the ID collisions problem.
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2021-06-29 6:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 6:14 [PATCH v5 0/2] Add octal DTR support for Macronix flash Zhengxun Li
2021-05-17 6:14 ` Zhengxun Li
2021-05-17 6:14 ` [PATCH v5 1/2] mtd: spi-nor: macronix: add support for Macronix octaflash Zhengxun Li
2021-05-17 6:14 ` Zhengxun Li
2021-05-17 7:33 ` Pratyush Yadav
2021-05-17 7:33 ` Pratyush Yadav
2021-06-29 2:06 ` zhengxunli
2021-06-29 2:06 ` zhengxunli
2021-06-29 6:37 ` Tudor.Ambarus [this message]
2021-06-29 6:37 ` Tudor.Ambarus
2021-06-29 9:33 ` zhengxunli
2021-06-29 9:33 ` zhengxunli
2021-06-30 9:03 ` zhengxunli
2021-06-30 9:03 ` zhengxunli
2021-05-17 6:14 ` [PATCH v5 2/2] spi: mxic: patch for octal DTR mode support Zhengxun Li
2021-05-17 6:14 ` Zhengxun Li
2021-05-17 15:49 ` Mark Brown
2021-05-17 15:49 ` Mark Brown
2021-05-17 16:06 ` Pratyush Yadav
2021-05-17 16:06 ` Pratyush Yadav
2021-05-18 2:47 ` zhengxunli
2021-05-18 2:47 ` zhengxunli
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=59855ba0-31d8-25b4-3000-ca493a83fe00@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=broonie@kernel.org \
--cc=jaimeliao@mxic.com.tw \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=p.yadav@ti.com \
--cc=zhengxunli@mxic.com.tw \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.