From: Rohit Hassan Sathyanarayan <rohit.hs@samsung.com>
To: dedekind1@gmail.com, linux-mtd@lists.infradead.org
Cc: v.dalal@samsung.com, gupta.raghav@samsung.com
Subject: [PATCH RESEND][MTD]MLC device check in OneNAND driver
Date: Fri, 24 Sep 2010 17:10:10 +0530 [thread overview]
Message-ID: <001701cb5bdd$3fd69a80$bf83cf80$%hs@samsung.com> (raw)
Signed-off-by: Rohit HS <rohit.hs@samsung.com>
Signed-off-by: Raghav Gupta <gupta.raghav@samsung.com>
---
drivers/mtd/onenand/onenand_base.c | 2 +-
include/mtd/mtd-abi.h | 1 +
2 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/mtd/onenand/onenand_base.c b/drivers/mtd/onenand/onenand_base.c
index a2bb520..33e0dbb 100644
--- a/drivers/mtd/onenand/onenand_base.c
+++ b/drivers/mtd/onenand/onenand_base.c
@@ -4027,7 +4027,7 @@ int onenand_scan(struct mtd_info *mtd, int maxchips)
mtd->ecclayout = this->ecclayout;
/* Fill in remaining MTD driver data */
- mtd->type = MTD_NANDFLASH;
+ mtd->type = ONENAND_IS_MLC(this) ? MTD_MLCNANDFLASH : MTD_NANDFLASH;
mtd->flags = MTD_CAP_NANDFLASH;
mtd->erase = onenand_erase;
mtd->point = NULL;
diff --git a/include/mtd/mtd-abi.h b/include/mtd/mtd-abi.h
index 4debb45..8d8161c 100644
--- a/include/mtd/mtd-abi.h
+++ b/include/mtd/mtd-abi.h
@@ -52,6 +52,7 @@ struct mtd_oob_buf64 {
#define MTD_NANDFLASH 4
#define MTD_DATAFLASH 6
#define MTD_UBIVOLUME 7
+#define MTD_MLCNANDFLASH 8
#define MTD_WRITEABLE 0x400 /* Device is writeable */
#define MTD_BIT_WRITEABLE 0x800 /* Single bits can be flipped */
--
1.6.6.1
next reply other threads:[~2010-09-24 11:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 11:40 Rohit Hassan Sathyanarayan [this message]
2010-09-24 11:52 ` [PATCH RESEND][MTD]MLC device check in OneNAND driver Artem Bityutskiy
2010-10-07 4:32 ` Rohit Hassan Sathyanarayan
2010-10-07 19:18 ` Artem Bityutskiy
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='001701cb5bdd$3fd69a80$bf83cf80$%hs@samsung.com' \
--to=rohit.hs@samsung.com \
--cc=dedekind1@gmail.com \
--cc=gupta.raghav@samsung.com \
--cc=linux-mtd@lists.infradead.org \
--cc=v.dalal@samsung.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).