From: Vignesh Raghavendra <vigneshr@ti.com>
To: <linux-mtd@lists.infradead.org>, Mauri Sandberg <sandberg@mailfence.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>, <richard@nod.at>,
<miquel.raynal@bootlin.com>
Subject: Re: [PATCH v2] mtd: cfi_cmdset_0002: AMD chip 0x2201 - write words
Date: Tue, 13 Apr 2021 21:56:14 +0530 [thread overview]
Message-ID: <161833061201.9818.14636884633616951588.b4-ty@ti.com> (raw)
In-Reply-To: <20210309174859.362060-1-sandberg@mailfence.com>
Hi Mauri Sandberg,
On Tue, 9 Mar 2021 19:48:59 +0200, Mauri Sandberg wrote:
> Buffer writes do not work with AMD chip 0x2201. The chip in question
> is a AMD/Spansion/Cypress Semiconductor S29GL256N and datasheet [1]
> talks about writing buffers being possible. While waiting for a neater
> solution resort to writing word-sized chunks only.
>
> Without the patch kernel logs will be flooded with entries like below:
>
> [...]
Reworded the $subject to:
mtd: cfi_cmdset_0002: Disable buffered writes for AMD chip 0x2201
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git cfi/next, thanks!
[1/1] mtd: cfi_cmdset_0002: AMD chip 0x2201 - write words
https://git.kernel.org/mtd/c/7e44041136
--
Regards
Vignesh
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2021-04-13 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 17:00 [PATCH] mtd: chips: AMD chip 0x2201 - write words not buffers Mauri Sandberg
2021-03-08 5:47 ` Vignesh Raghavendra
2021-03-08 17:41 ` Mauri Sandberg
2021-03-09 17:48 ` [PATCH v2] mtd: cfi_cmdset_0002: AMD chip 0x2201 - write words Mauri Sandberg
2021-04-13 16:26 ` Vignesh Raghavendra [this message]
2021-04-16 7:45 ` Mauri Sandberg
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=161833061201.9818.14636884633616951588.b4-ty@ti.com \
--to=vigneshr@ti.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=sandberg@mailfence.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).