From: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
To: Tudor.Ambarus@microchip.com
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
michael.krummsdorf@tq-group.com, miquel.raynal@bootlin.com,
richard@nod.at, vigneshr@ti.com
Subject: Re: (EXT) Re: [PATCH] mtd: spi-nor: micron-st: enable 4-byte opcodes for n25q512a
Date: Mon, 29 Jun 2020 15:22:01 +0200 [thread overview]
Message-ID: <570474bcc4055527d85ca8cf84b653f56bef3e23.camel@ew.tq-group.com> (raw)
In-Reply-To: <e94d42be-5e40-e2bb-4683-cc7af59e801a@microchip.com>
On Mon, 2020-06-29 at 13:02 +0000, Tudor.Ambarus@microchip.com wrote:
> Hi, Matthias,
>
> On 6/10/20 12:16 PM, Matthias Schiffer wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you
> > know the content is safe
> >
> > From: Michael Krummsdorf <michael.krummsdorf@tq-group.com>
> >
> > Set SPI_NOR_4B_OPCODES, as the flash supports 4-byte opcodes.
>
> I remember that we stripped SPI_NOR_4B_OPCODES intentionally for the
> n25q
> flashes, check https://lkml.org/lkml/2019/12/5/50.
>
> Cheers,
> ta
Ah, thank you for the pointer. Looking at a boot log of a more recent
kernel again, the SPI-NOR flash on our hardware is actually detected as
mt25qu512a and not n25q512a now, so everything should work as expected
without this patch.
prev parent reply other threads:[~2020-06-29 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 9:16 [PATCH] mtd: spi-nor: micron-st: enable 4-byte opcodes for n25q512a Matthias Schiffer
2020-06-29 13:02 ` Tudor.Ambarus
2020-06-29 13:22 ` Matthias Schiffer [this message]
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=570474bcc4055527d85ca8cf84b653f56bef3e23.camel@ew.tq-group.com \
--to=matthias.schiffer@ew.tq-group.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael.krummsdorf@tq-group.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--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).