From: masonccyang@mxic.com.tw
To: boris.brezillon@bootlin.com, miquel.raynal@bootlin.com,
richard@nod.at, dwmw2@infradead.org, computersforpeace@gmail.com,
marek.vasut@gmail.com, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org, juliensu@mxic.com.tw,
zhengxunli@mxic.com.tw
Cc: masonccyang@mxic.com.tw
Subject: [PATCH] mtd: rawnand: Add All 1.8V AC chips have a broken GET_FEATURES(TIMINGS)
Date: Thu, 25 Oct 2018 14:44:31 +0800 [thread overview]
Message-ID: <1540449871-7224-2-git-send-email-masonccyang@mxic.com.tw> (raw)
In-Reply-To: <1540449871-7224-1-git-send-email-masonccyang@mxic.com.tw>
From: Mason Yang <masonccyang@mxic.com.tw>
Make sure we flag all 1.8V broken chips as not supporting this features.
Signed-off-by: Mason Yang <masonccyang@mxic.com.tw>
---
drivers/mtd/nand/raw/nand_macronix.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/mtd/nand/raw/nand_macronix.c b/drivers/mtd/nand/raw/nand_macronix.c
index 49c546c..3836544 100644
--- a/drivers/mtd/nand/raw/nand_macronix.c
+++ b/drivers/mtd/nand/raw/nand_macronix.c
@@ -33,6 +33,13 @@ static void macronix_nand_fix_broken_get_timings(struct nand_chip *chip)
"MX30LF4G18AC",
"MX30LF4G28AC",
"MX60LF8G18AC",
+ "MX30UF1G18AC",
+ "MX30UF1G16AC",
+ "MX30UF2G18AC",
+ "MX30UF2G16AC",
+ "MX30UF4G18AC",
+ "MX30UF4G16AC",
+ "MX30UF4G28AC",
};
if (!chip->parameters.supports_set_get_features)
--
1.9.1
next prev parent reply other threads:[~2018-10-25 6:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 6:44 [PATCH] mtd: rawnand: Add all 1.8V AC chips have a broken GET_FEATURES(TIMINGS) masonccyang
2018-10-25 6:44 ` masonccyang [this message]
2018-11-11 20:55 ` [PATCH] mtd: rawnand: Add All " Miquel Raynal
2018-10-25 7:16 ` [PATCH] mtd: rawnand: Add all " Boris Brezillon
2018-10-25 7:17 ` 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=1540449871-7224-2-git-send-email-masonccyang@mxic.com.tw \
--to=masonccyang@mxic.com.tw \
--cc=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=juliensu@mxic.com.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--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 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).