- 24 Oct, 2010 40 commits
-
-
Sebastian Andrzej Siewior authored
it will create an empty BBT table without considering vendor's BBT information. Vendor's information may be unavailable if the NAND controller has a different DATA & OOB layout or this information may be allready purged. Signed-off-by:
Sebastian Andrzej Siewior <bigeasy@linutronix.de> Signed-off-by:
David Woodhouse <David.Woodhouse@intel.com>
-
Sebastian Andrzej Siewior authored
The first (sixt) byte in the OOB area contains vendor's bad block information. During identification of the NAND chip this information is collected by scanning the complete chip. The option NAND_USE_FLASH_BBT is used to store this information in a sector so we don't have to scan the complete flash. Unfortunately the code stores a marker in order to recognize the BBT in the OOB area. This will fail if the OOB area is completely used for ECC. This patch introduces the option NAND_USE_FLASH_BBT_NO_OOB which has to be used with NAND_USE_FLASH_BBT. It will then store BBT on flash without touching the OOB area. The BBT format on flash remains same except the first page starts with the recognition pattern followed by the version byte. This change was tested in nandsim and it looks good so far :) Signed-off-by:
-
Sebastian Andrzej Siewior authored
No code change. Signed-off-by:
Artem Bityutskiy <Artem.Bityutskiy@nokia.com> Signed-off-by:
-
Sebastian Andrzej Siewior authored
Signed-off-by:
-
Kyungmin Park authored
S5PC210 has the same OneNAND controller as S5PC110 Signed-off-by:
Kyungmin Park <kyungmin.park@samsung.com> Signed-off-by:
-
Kyungmin Park authored
Implement DMA interrupt method. previous time it polls the DMA status. It can reduce the CPU power but decrease the performance a little. Signed-off-by:
-
Kyungmin Park authored
When use HIGHMEM, dma_map_single doesn't get the proper DMA address. So use the dma_map_page in this case. Signed-off-by:
-
Kyungmin Park authored
After S5PC110 use the generic method for OneNAND. Signed-off-by:
-
Rohit Hassan Sathyanarayan authored
The MLC NAND Flash differs from the SLC NAND flash in functioning and the cell structure. Therefore we are considering it as a different Flash type. Signed-off-by:
Rohit H.S <rohit.hs@samsung.com> Signed-off-by:
Raghav Gupta <gupta.raghav@samsung.com> Signed-off-by:
-
Rohit Hassan Sathyanarayan authored
MLC NAND Flash has a different cell structure and differs in functioning than the SLC NAND Flash. Hence we are considering it as a different Flash type. Signed-off-by:
-
Kyungmin Park authored
There's no case timeout but add it for some H/W problem or wrong codes implementation Signed-off-by:
-
Huang Shijie authored
Not all the NAND devices have all the information in additional id bytes. So add a hook in the nand_chip{} is a good method to calculate the right value of oobsize, erasesize and so on. Without the hook,you will get the wrong value, and you have to hack in the ->scan_bbt() to change the wrong value which make the code mess. Signed-off-by:Huang Shijie <shijie8@gmail.com> Signed-off-by:
-
Mike Frysinger authored
The jffs2 compression framework provides a "model" argument when compressing and decompressing, but the caller always passes in NULL and the callees never use it. So punt this useless overhead. Signed-off-by:
Mike Frysinger <vapier@gentoo.org> Signed-off-by:
-
Roman Tereshonkov authored
Add support for mtd repartition based on the block device BLKPG interface: BLKPG_ADD_PARTITION - for partition creation; BLKPG_DEL_PARTITION - for partition delete The usage is based on BLKPG ioctl called with struct blkpg_ioctl_arg argument which includes the reference to struct blkpg_partition discribing the partition offset and length. Disadvantage: there is no implementation for mtd flags control. The flags are always borrowed from the master device. Signed-off-by:
Roman Tereshonkov <roman.tereshonkov@nokia.com> Signed-off-by:
-
Roman Tereshonkov authored
mtd_is_master, mtd_add_partition and mtd_del_partition functions are added to give the possibility of partition manipulation by ioctl request. The old partition add function is modified to fit the dynamic allocation. Signed-off-by:
-
Linus Walleij authored
Just as it says, if this is merged along with the other patch, the driver supports the U300 NAND flash interface. Signed-off-by:
Linus Walleij <linus.walleij@stericsson.com> Signed-off-by:
-
Linus Walleij authored
This is the same driver submitted by ST Micros SPEAr team but generalized and tested on the ST-Ericsson U300. It probably easily works on the NHK8815 too. Signed-off-by:
Vipin Kumar <vipin.kumar@st.com> Signed-off-by:
Rajeev Kumar <rajeev-dlh.kumar@st.com> Signed-off-by:
Shiraz Hashim <shiraz.hashim@st.com> Signed-off-by:
Viresh Kumar <viresh.kumar@st.com> Signed-off-by:
-
Wolfram Sang authored
yield() has different semantics meanwhile and even causes RT-kernels to BUG. Replace the only appearance left in jffs2. Signed-off-by:
Wolfram Sang <w.sang@pengutronix.de> Signed-off-by:
-
Thierry Reding authored
This patch adds support for the Winbond W25Q64 serial flash. Signed-off-by:
Thierry Reding <thierry.reding@avionic-design.de> Signed-off-by:
-
Artem Bityutskiy authored
Currently MTD caches the last read NAND page, even if there was an uncorrectable ECC error. This patch prevents caching in case of uncorrectable ECC errors. The reason is that we want to allow the user to re-read the NAND page several times. In case of unstable bits re-trying may help. Moreover, current behavior is wrong because the first read returns -EBADMSG (correctly) but the second read succeeds and incorrectly returns 0 (because we read from the cache). Signed-off-by:
-
Florian Fainelli authored
This patch adds support for parsing Broadcom BCM63xx image tag format and creating MTD partitions accordingly. This driver is a platform_device which can be instantiated accordingly by bcm63xx board support code. Signed-off-by:
Daniel Dickinson <cshore@csolve.net> Signed-off-by:
Mike Albon <malbon@openwrt.org> Signed-off-by:
Florian Fainelli <florian@openwrt.org> Signed-off-by:
-
Dan Carpenter authored
If "ur_idx" is wrong we could go past the end of the array. The "ur_idx" comes from root so it's not a huge deal, but adding a sanity check makes the code more robust. Signed-off-by:
Dan Carpenter <error27@gmail.com> Signed-off-by:
-
Roy Zang authored
Fix the build warning: drivers/mtd/nand/fsl_upm.c: In function 'fun_chip_init': drivers/mtd/nand/fsl_upm.c:190: warning: format '%x' expects type 'unsigned int', but argument 3 has type 'resource_size_t' Signed-off-by:
Roy Zang <tie-fei.zang@freescale.com> Signed-off-by:
-
Florian Fainelli authored
Only 3 warnings are left, one is off by one character, but splitting the line would reduce the readability. One is for a for loop statement, which would also not improve readability. The last one is a false positive on a test. Artem: it is much easier to verify patches against nand_base.c with checkpatch.pl when nand_base.c itself does not have so many checkpatch.pl warnings. Signed-off-by:Florian Fainelli <ffainelli@freebox.fr> Signed-off-by:
-
Florian Fainelli authored
Artem: it is much easier to verify patches against nand_base.c with checkpatch.pl when nand_base.c itself does not have so many checkpatch.pl warnings. Signed-off-by: -
Wolfram Sang authored
Sudhakar found out that 100µs are enough. Sadly, his updated patch was overlooked and an older version still using 100ms was merged. Fix this. Reference: http://patchwork.ozlabs.org/patch/59180/Signed-off-by:
-
Gernot Hoyler authored
This patch adds support for Spansion S25FL016K and S25FL064K SPI flash. It has been tested with physical devices. Note that both parts exhibit a Winbond manufacturer ID so they might also be added to that section. Signed-off-by:
Gernot Hoyler <Gernot.Hoyler@spansion.com> Signed-off-by:
-
Florian Fainelli authored
In order to reduce the indentation and improve the readability of nand_get_ flash_type, split the ONFI detection logic to its own function. The detection logic inside nand_flash_detect_onfi is also rewritten to allow for less indentation. Signed-off-by:
-
Florian Fainelli authored
This patch adds support for reading NAND device ONFI parameters and use the ONFI informations to define its geometry. In case the device supports ONFI, the onfi_version field in struct nand_chip contains the version (BCD) and the onfi_params structure can be used by drivers to set up timings and such. We currently only support ONFI 1.0 parameters. Signed-off-by:
Brian Norris <norris@broadcom.com> Signed-off-by:
Matthieu Castet <matthieu.castet@parrot.com> Signed-off-by:
Maxime Bizon <mbizon@freebox.fr> Signed-off-by:
-
Florian Fainelli authored
Signed-off-by:
-
Florian Fainelli authored
This command is used to read the device ONFI parameters page. Signed-off-by:
-
Kyungmin Park authored
S5PC110 OneNAND controller use the generic functions provided from onenand_base. Signed-off-by:
-
Brian Norris authored
There are some additions to the detection scheme used by Samsung MLC NAND. These simple changes to support the 400- and 436-byte OOB are found in the following data sheet: Samsung K9GBG08U0M (p.40) Signed-off-by:
-
Wolfram Sang authored
Signed-off-by:
-
Dan Carpenter authored
This code isn't reachable. I looked through the git history and it hasn't been reachable for years. Someone removed the label to silence gcc's unused label warning but these few lines accidentally got left behind. Signed-off-by:
Dominik Brodowski <linux@dominikbrodowski.net> Signed-off-by:
-
Julia Lawall authored
Add a call to of_node_put in the error handling code following a call to of_find_compatible_node. Signed-off-by:
Julia Lawall <julia@diku.dk> Acked-by:
-
Lei Wen authored
For different command need different oob requirement, set the proper oob length by different cmd. Signed-off-by:
Lei Wen <leiwen@marvell.com> Acked-by:
Eric Miao <eric.y.miao@gmail.com> Signed-off-by:
-
Lei Wen authored
After probe, all info already transfer to driver structure. There is no need to keep the original flash info. So that we could safely free the flash info in memory, which may grows larger when more flash is suported. Signed-off-by:
Haojian Zhuang <haojian.zhuang@marvell.com> Acked-by:
-
Lei Wen authored
We certainly don't need to send read id command times by times, since we already know what the id is after the first read id... So create a default timing which could ensure it would successfully read id out all supported chip. Then follow the build-in table to reconfigure the timing. Signed-off-by:
-
Lei Wen authored
Adding a new flash definition would need less code. Keep the platform passing flash definition method. If one flash is both defined in platform data and builtin table, driver would select the one from platform data first. By this way, platform could select the timing most suit for itself, not need to follow the common settings. Signed-off-by:
-
