From: Guillaume LECERF <glecerf@gmail.com>
To: linux-mtd@lists.infradead.org
Cc: fggs@terra.com.br, zhangyd6@gmail.com, w.sang@pengutronix.de,
David.Woodhouse@intel.com
Subject: [PATCH 4/4] mtd: cfi_cmdset_0002: add CFI detection for SST 38VF640x chips
Date: Fri, 22 Oct 2010 17:40:30 +0200 [thread overview]
Message-ID: <20101022154030.11097.40767.stgit@dev.siriade.com> (raw)
In-Reply-To: <20101022154015.11097.94660.stgit@dev.siriade.com>
Add support for SST38VF640x chips in CFI mode.
Signed-off-by: Guillaume LECERF <glecerf@gmail.com>
Signed-off-by: yidong zhang <zhangyd6@gmail.com>
---
drivers/mtd/chips/cfi_cmdset_0002.c | 19 +++++++++++++++++++
1 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/drivers/mtd/chips/cfi_cmdset_0002.c b/drivers/mtd/chips/cfi_cmdset_0002.c
index a359967..0248253 100644
--- a/drivers/mtd/chips/cfi_cmdset_0002.c
+++ b/drivers/mtd/chips/cfi_cmdset_0002.c
@@ -296,6 +296,21 @@ static void fixup_sst39vf_rev_b(struct mtd_info *mtd, void *param)
sector_erase_cmd = CMD(0x50);
}
+static void fixup_sst38vf640x_sectorsize(struct mtd_info *mtd, void *param)
+{
+ struct map_info *map = mtd->priv;
+ struct cfi_private *cfi = map->fldrv_priv;
+
+ fixup_sst39vf_rev_b(mtd, param);
+
+ /*
+ * CFI reports 1024 sectors (0x03ff +1) of 64KBytes (0x0100 *256) where
+ * it should report a size of 8KBytes (0x0020 *256).
+ */
+ cfi->cfiq->EraseRegionInfo[0] = 0x002003ff;
+ pr_warning("%s: Bad 38VF640x CFI data, adjust sector size from 64 to 8KBytes\n", mtd->name);
+}
+
static void fixup_s29gl064n_sectors(struct mtd_info *mtd, void *param)
{
struct map_info *map = mtd->priv;
@@ -347,6 +362,10 @@ static struct cfi_fixup cfi_fixup_table[] = {
{ CFI_MFR_AMD, 0x1301, fixup_s29gl064n_sectors, NULL, },
{ CFI_MFR_AMD, 0x1a00, fixup_s29gl032n_sectors, NULL, },
{ CFI_MFR_AMD, 0x1a01, fixup_s29gl032n_sectors, NULL, },
+ { CFI_MFR_SST, 0x536A, fixup_sst38vf640x_sectorsize, NULL, }, /* SST38VF6402 */
+ { CFI_MFR_SST, 0x536B, fixup_sst38vf640x_sectorsize, NULL, }, /* SST38VF6401 */
+ { CFI_MFR_SST, 0x536C, fixup_sst38vf640x_sectorsize, NULL, }, /* SST38VF6404 */
+ { CFI_MFR_SST, 0x536D, fixup_sst38vf640x_sectorsize, NULL, }, /* SST38VF6403 */
#if !FORCE_WORD_WRITE
{ CFI_MFR_ANY, CFI_ID_ANY, fixup_use_write_buffers, NULL, },
#endif
next prev parent reply other threads:[~2010-10-22 15:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 15:40 [PATCH 1/4] mtd: cfi_util: add support for switching SST 39VF640xB chips into QRY mode Guillaume LECERF
2010-10-22 15:40 ` [PATCH 2/4] mtd: cfi_cmdset_0002: make sector erase command variable Guillaume LECERF
2010-10-23 10:24 ` Wolfram Sang
2010-10-25 8:11 ` Guillaume LECERF
2010-10-26 8:34 ` Guillaume LECERF
2010-10-22 15:40 ` [PATCH 3/4] mtd: cfi_cmdset_0002: use 0x50 erase command for SST 39VFxxxxB chips Guillaume LECERF
2010-10-22 15:40 ` Guillaume LECERF [this message]
2010-10-25 1:18 ` [PATCH 4/4] mtd: cfi_cmdset_0002: add CFI detection for SST 38VF640x chips yidong zhang
2010-10-25 8:09 ` Guillaume LECERF
2010-10-25 8:38 ` yidong zhang
2010-10-25 9:17 ` Guillaume LECERF
2010-10-25 10:01 ` yidong zhang
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=20101022154030.11097.40767.stgit@dev.siriade.com \
--to=glecerf@gmail.com \
--cc=David.Woodhouse@intel.com \
--cc=fggs@terra.com.br \
--cc=linux-mtd@lists.infradead.org \
--cc=w.sang@pengutronix.de \
--cc=zhangyd6@gmail.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).