23 Sep, 2014
2 commits
-
Previously, the only way to map a NOR device as a simple ROM was to
use the obsolete "direct-mapped" compatible binding (which further
requires device_type = "nor" and probe-type = "NOR" properties).This patch adds an "mtd-rom" compatible binding to the "map_rom"
probe type.Signed-off-by: Aaron Sierra
Signed-off-by: Brian Norris -
The "ROM" and unknown probe types within the obsolete "direct-mapped"
probe function used the nonexistent "mtd_rom" probe instead of the
intended "map_rom".Signed-off-by: Aaron Sierra
Signed-off-by: Brian Norris
20 Aug, 2014
3 commits
-
Fix the bug in handling gpio flash read/write when offset + len
from MTD exceeds the window sizeSigned-off-by: Aaron Wu
[Brian: made some commentary edits. Also note that the BUG_ON() was
provably false for all non-negative inputs (since x % y -
Already depends on SOLUTION_ENGINE, so we don't need the SUPERH
dependency too.Signed-off-by: Brian Norris
-
Use NULL instead of 0 when returning an address. This fixes a
sparse warning.Signed-off-by: Martin Kepplinger
Signed-off-by: Brian Norris
03 Jul, 2014
1 commit
-
Signed-off-by: Atsushi Nemoto
Signed-off-by: Brian Norris
29 May, 2014
1 commit
-
Since (a few releases before) v2.6.0 there have been checks for
CONFIG_MTD_SUPERH_RESERVE. One check is still present. But a Kconfig
symbol MTD_SUPERH_RESERVE has never been added. So a few lines of dead
code can be removed.Signed-off-by: Paul Bolle
Signed-off-by: Brian Norris
28 May, 2014
1 commit
-
On m86k, and maybe a few other architectures, we get this kind of
warning, due to misuse of volatile:drivers/mtd/maps/sc520cdp.c: In function 'sc520cdp_setup_par':
>> drivers/mtd/maps/sc520cdp.c:223:2: warning: passing argument 1 of 'iounmap' discards 'volatile' qualifier from pointer target type [enabled by default]
arch/m68k/include/asm/raw_io.h:22:13: note: expected 'void *' but argument is of type 'volatile long unsigned int *'Rather than annotating the variable declaration, let's just use the
proper accessors, which add the 'volatile' qualifier to the operation.Signed-off-by: Brian Norris
13 May, 2014
1 commit
-
Anyone working with an AMD Elan SC520 development or evaluation board
would be building a dedicated kernel for it, so we can make the
sc520cdp and netsc520 maps depend on MELAN. SC520_CPUFREQ already
depends on MELAN so it makes things more consistent. It also makes
kernel configuration for every other x86 user easier.Signed-off-by: Jean Delvare
Cc: David Woodhouse
Signed-off-by: Brian Norris
11 Mar, 2014
4 commits
-
Up to now mtd-ram devices described in device trees were only accessible
if mtd-flash or mtd-rom were also configured at linux configuration
time, because MTD_PHYSMAP_OF was only available if (MTD_CFI ||
MTD_JEDECPROBE || MTD_ROM). Allow MTD_PHYSMAP_OF selection also
when only MTD_RAM is set.Signed-off-by: Philippe De Muyter
Signed-off-by: Brian Norris -
There is no point in displaying the TS5500-specific driver entries if
TS5500 board support itself isn't enabled.Signed-off-by: Jean Delvare
Cc: David Woodhouse
Cc: Vivien Didelot
Signed-off-by: Brian Norris -
The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message.Signed-off-by: Jingoo Han
Signed-off-by: Brian Norris -
None of these files are actually using any __init type directives
and hence don't need to include . Most are just a
left over from __devinit and __cpuinit removal, or simply due to
code getting copied from one driver to the next.Cc: David Woodhouse
Cc: Brian Norris
Cc: linux-mtd@lists.infradead.org
Signed-off-by: Paul Gortmaker
[Brian: dropped one incorrect hunk]
Signed-off-by: Brian Norris
29 Jan, 2014
1 commit
-
Pull MTD updates from Brian Norris:
- Add me (Brian Norris) as an additional MTD maintainer (it'd be nice to get
David's "ack" for this; I'm sure he approves, but he's been pretty silent
lately)
- Add Ezequiel Garcie as maintainer for the pxa3xx NAND driver
- Last (?) round of pxa3xx improvements for supporting Armada 370/XP
- Typical churn in driver boilerplate (OOM messages, printk()'s, devm_*, etc.)
- Quad read mode support for SPI NOR driver (m25p80)
- Update Davinci NAND driver to prepare for use on new platforms
- Begin to kill off NAND_MAX_{PAGE,OOB}SIZE macros; more work is pending
- Miscellaneous NAND device support (new IDs)
- Add READ RETRY support for Micron MLC NAND
- Support new GPMI NAND ECC layout device-tree binding
- Avoid mapping stack/vmalloc() memory for GPMI NAND DMA* tag 'for-linus-20140127' of git://git.infradead.org/linux-mtd: (151 commits)
mtd: gpmi: add sanity check when mapping DMA for read_buf/write_buf
mtd: gpmi: allocate a proper buffer for non ECC read/write
mtd: m25p80: Set rx_nbits for Quad SPI transfers
mtd: m25p80: Enable Quad SPI read transfers for s25fl512s
mtd: s3c2410: Merge plat/regs-nand.h into s3c2410.c
mtd: mtdram: add missing 'const'
mtd: m25p80: assign default read command
mtd: nuc900_nand: remove redundant return value check of platform_get_resource()
mtd: plat_nand: remove redundant return value check of platform_get_resource()
mtd: nand: add Intel manufacturer ID
mtd: nand: add SanDisk manufacturer ID
mtd: nand: add support for Samsung K9LCG08U0B
mtd: nand: pxa3xx: Add support for 2048 bytes page size devices
mtd: m25p80: Use OPCODE_QUAD_READ_4B for 4-byte addressing
mtd: nand: don't use {read,write}_buf for 8-bit transfers
mtd: nand: use __packed shorthand
mtd: nand: support Micron READ RETRY
mtd: nand: add generic READ RETRY support
mtd: nand: add ONFI vendor block for Micron
mtd: nand: localize ECC failures per page
...
08 Jan, 2014
1 commit
-
Use devm_*() functions to make cleanup paths simpler.
Signed-off-by: Jingoo Han
Signed-off-by: Brian Norris
05 Jan, 2014
1 commit
-
ioremap_cache is more aligned with other architectures.
There are only 2 users of this in the kernel: pxa2xx-flash and Xen.This fixes Xen build failures on arm64:
drivers/tty/hvc/hvc_xen.c:233:2: error: implicit declaration of function 'ioremap_cached' [-Werror=implicit-function-declaration]
drivers/xen/grant-table.c:1174:3: error: implicit declaration of function 'ioremap_cached' [-Werror=implicit-function-declaration]
drivers/xen/xenbus/xenbus_probe.c:778:4: error: implicit declaration of function 'ioremap_cached' [-Werror=implicit-function-declaration]Signed-off-by: Rob Herring
Signed-off-by: Stefano Stabellini
Signed-off-by: Russell King
04 Jan, 2014
2 commits
-
Use devm_kzalloc() to make cleanup paths simpler. Also, checking
return value of devm_kzalloc() is added in order to check if the
allocation succeded.Signed-off-by: Jingoo Han
Acked-by: John Crispin
Signed-off-by: Brian Norris -
map_info.name is "const char *"
Signed-off-by: Geert Uytterhoeven
Cc: David Woodhouse
Cc: linux-mtd@lists.infradead.org
Signed-off-by: Brian Norris
07 Nov, 2013
4 commits
-
module_platform_driver simplifies the code by removing boiler
plate.Signed-off-by: Sachin Kamat
Signed-off-by: Brian Norris -
The driver core clears the driver data to NULL after device_release
or on probe failure. Thus, it is not needed to manually clear the
device driver data to NULL.Signed-off-by: Jingoo Han
Signed-off-by: Brian Norris -
The driver core clears the driver data to NULL after device_release
or on probe failure. Thus, it is not needed to manually clear the
device driver data to NULL.Signed-off-by: Jingoo Han
Signed-off-by: Brian Norris -
The driver core clears the driver data to NULL after device_release
or on probe failure. Thus, it is not needed to manually clear the
device driver data to NULL.Signed-off-by: Jingoo Han
Signed-off-by: Brian Norris
28 Oct, 2013
1 commit
-
Casting the return value which is a void pointer is redundant.
The conversion from void pointer to any other pointer type is
guaranteed by the C programming language.Signed-off-by: Jingoo Han
Signed-off-by: Brian Norris
31 Aug, 2013
3 commits
-
Added missing __iomem annotation and staticized local symbols
in order to fix the following sparse warnings:drivers/mtd/maps/cfi_flagadm.c:58:17: warning: symbol 'flagadm_map' was not declared. Should it be static?
drivers/mtd/maps/cfi_flagadm.c:64:22: warning: symbol 'flagadm_parts' was not declared. Should it be static?
drivers/mtd/maps/cfi_flagadm.c:115:18: warning: cast removes address space of expression
drivers/mtd/maps/cfi_flagadm.c:115:18: warning: incorrect type in argument 1 (different address spaces)
drivers/mtd/maps/cfi_flagadm.c:115:18: expected void volatile [noderef] *addr
drivers/mtd/maps/cfi_flagadm.c:115:18: got void *
drivers/mtd/maps/cfi_flagadm.c:126:26: warning: cast removes address space of expression
drivers/mtd/maps/cfi_flagadm.c:126:26: warning: incorrect type in argument 1 (different address spaces)
drivers/mtd/maps/cfi_flagadm.c:126:26: expected void volatile [noderef] *addr
drivers/mtd/maps/cfi_flagadm.c:126:26: got void *
drivers/mtd/maps/cfi_flagadm.c:127:36: warning: Using plain integer as NULL pointerSigned-off-by: Jingoo Han
Signed-off-by: Brian Norris
Signed-off-by: David Woodhouse -
Added missing __iomem annotation and used NULL instead of 0
in order to fix the following sparse warnings:drivers/mtd/maps/impa7.c:82:32: warning: Using plain integer as NULL pointer
drivers/mtd/maps/impa7.c:96:34: warning: cast removes address space of expression
drivers/mtd/maps/impa7.c:96:34: warning: incorrect type in argument 1 (different address spaces)
drivers/mtd/maps/impa7.c:96:34: expected void volatile [noderef] *addr
drivers/mtd/maps/impa7.c:96:34: got void *
drivers/mtd/maps/impa7.c:108:34: warning: cast removes address space of expression
drivers/mtd/maps/impa7.c:108:34: warning: incorrect type in argument 1 (different address spaces)
drivers/mtd/maps/impa7.c:108:34: expected void volatile [noderef] *addr
drivers/mtd/maps/impa7.c:108:34: got void *
drivers/mtd/maps/impa7.c:109:45: warning: Using plain integer as NULL pointerSigned-off-by: Jingoo Han
Signed-off-by: Brian Norris
Signed-off-by: David Woodhouse -
Use the wrapper function for retrieving the platform data instead of
accessing dev->platform_data directly.Signed-off-by: Jingoo Han
Signed-off-by: Brian Norris
Signed-off-by: David Woodhouse
06 Aug, 2013
8 commits
-
JEDEC device support was removed in v2.6.22. (It had been marked as
BROKEN (indirectly) since at least v2.6.12.)When it was removed the two JEDEC mapping drivers that depended on it
should have been removed too. Do so now.Signed-off-by: Paul Bolle
Acked-by: Brian Norris
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse -
The driver core clears the driver data to NULL after device_release
or on probe failure, since commit 0998d0631001288a5974afc0b2a5f568bcdecb4d
(device-core: Ensure drvdata = NULL when no driver is bound).
Thus, it is not needed to manually clear the device driver data to NULL.Signed-off-by: Jingoo Han
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse -
The driver core clears the driver data to NULL after device_release
or on probe failure, since commit 0998d0631001288a5974afc0b2a5f568bcdecb4d
(device-core: Ensure drvdata = NULL when no driver is bound).
Thus, it is not needed to manually clear the device driver data to NULL.Signed-off-by: Jingoo Han
Acked-by: Marc Kleine-Budde
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse -
The driver core clears the driver data to NULL after device_release
or on probe failure, since commit 0998d0631001288a5974afc0b2a5f568bcdecb4d
(device-core: Ensure drvdata = NULL when no driver is bound).
Thus, it is not needed to manually clear the device driver data to NULL.Signed-off-by: Jingoo Han
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse -
The driver core clears the driver data to NULL after device_release
or on probe failure, since commit 0998d0631001288a5974afc0b2a5f568bcdecb4d
(device-core: Ensure drvdata = NULL when no driver is bound).
Thus, it is not needed to manually clear the device driver data to NULL.Signed-off-by: Jingoo Han
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse -
The driver core clears the driver data to NULL after device_release
or on probe failure, since commit 0998d0631001288a5974afc0b2a5f568bcdecb4d
(device-core: Ensure drvdata = NULL when no driver is bound).
Thus, it is not needed to manually clear the device driver data to NULL.Signed-off-by: Jingoo Han
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse -
The driver core clears the driver data to NULL after device_release
or on probe failure, since commit 0998d0631001288a5974afc0b2a5f568bcdecb4d
(device-core: Ensure drvdata = NULL when no driver is bound).
Thus, it is not needed to manually clear the device driver data to NULL.Signed-off-by: Jingoo Han
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse -
The driver core clears the driver data to NULL after device_release
or on probe failure, since commit 0998d0631001288a5974afc0b2a5f568bcdecb4d
(device-core: Ensure drvdata = NULL when no driver is bound).
Thus, it is not needed to manually clear the device driver data to NULL.Signed-off-by: Jingoo Han
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse
12 Jun, 2013
1 commit
-
This patch provide migration to using "mtd-ram" driver instead of using
special driver for handling NVRAM memory.Signed-off-by: Alexander Shiyan
Signed-off-by: Olof Johansson
10 May, 2013
1 commit
-
Pull MTD update from David Woodhouse:
- Lots of cleanups from Artem, including deletion of some obsolete
drivers- Support partitions larger than 4GiB in device tree
- Support for new SPI chips
* tag 'for-linus-20130509' of git://git.infradead.org/linux-mtd: (83 commits)
mtd: omap2: Use module_platform_driver()
mtd: bf5xx_nand: Use module_platform_driver()
mtd: denali_dt: Remove redundant use of of_match_ptr
mtd: denali_dt: Change return value to fix smatch warning
mtd: denali_dt: Use module_platform_driver()
mtd: denali_dt: Fix incorrect error check
mtd: nand: subpage write support for hardware based ECC schemes
mtd: omap2: use msecs_to_jiffies()
mtd: nand_ids: use size macros
mtd: nand_ids: improve LEGACY_ID_NAND macro a bit
mtd: add 4 Toshiba nand chips for the full-id case
mtd: add the support to parse out the full-id nand type
mtd: add new fields to nand_flash_dev{}
mtd: sh_flctl: Use of_match_ptr() macro
mtd: gpio: Use of_match_ptr() macro
mtd: gpio: Use devm_kzalloc()
mtd: davinci_nand: Use of_match_ptr()
mtd: dataflash: Use of_match_ptr() macro
mtd: remove h720x flash support
mtd: onenand: remove OneNAND simulator
...
16 Apr, 2013
1 commit
-
GENERIC_GPIO is now equivalent to GPIOLIB and features that depended on
GENERIC_GPIO can now depend on GPIOLIB to allow removal of this option.Signed-off-by: Alexandre Courbot
Acked-by: Linus Walleij
Acked-by: Grant Likely
05 Apr, 2013
3 commits
-
The h720x platform support is going away in linux-3.10, so the
MTD driver will also not be needed any more.Signed-off-by: Arnd Bergmann
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse -
Be a bit stricter and add few more 'const' qualifiers.
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse -
Be a bit stricter and add few more 'const' qualifiers.
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse
