linux.git/drivers/mtd/onenand, branch v4.16

Merge tag 'nand/for-4.16' of git://git.infradead.org/linux-mtd into mtd/next

2018-01-29T08:58:36+00:00

Pull NAND changes from Boris Brezillon:

"
  Core changes:
  * Fix NAND_CMD_NONE handling in nand_command[_lp]() hooks
  * Introduce the ->exec_op() infrastructure
  * Rework NAND buffers handling
  * Fix ECC requirements for K9F4G08U0D
  * Fix nand_do_read_oob() to return the number of bitflips
  * Mark K9F1G08U0E as not supporting subpage writes

  Driver changes:
  * MTK: Rework the driver to support new IP versions
  * OMAP OneNAND: Full rework to use new APIs (libgpio, dmaengine) and fix
    DT support
  * Marvell: Add a new driver to replace the pxa3xx one
"

mtd: onenand: omap2: Remove redundant dev_err call in omap2_onenand_probe()

2018-01-19T08:40:03+00:00

There is a error message within devm_ioremap_resource
already, so remove the dev_err call to avoid redundant
error message.

Signed-off-by: Wei Yongjun 
Signed-off-by: Boris Brezillon

mtd: Remove duplicate checks on mtd_oob_ops parameter

2018-01-16T14:23:22+00:00

Some of the check done in custom ->_read/write_oob() implementation are
already done by the core (in mtd_check_oob_ops()).

Suggested-by: Peter Pan 
[Remove redundant checks done in mtdpart.c]
Signed-off-by: Boris Brezillon 
Tested-by: Ladislav Michl

mtd: Fallback to ->_read/write_oob() when ->_read/write() is missing

2018-01-16T14:23:21+00:00

Some MTD sublayers/drivers are implementing ->_read/write_oob() and
provide dummy wrappers for their ->_read/write() implementations.
Let the core handle this case instead of duplicating the logic.

Signed-off-by: Boris Brezillon 
Acked-by: Robert Jarzmik 
Acked-by: Brian Norris 
Reviewed-by: Miquel Raynal 
Tested-by: Ladislav Michl

mtd: onenand: omap2: print resource using %pR format string

2018-01-16T08:25:12+00:00

The omap2 onenand driver is now available for compile-testing, which
uncovers a warning in configurations that have a 64-bit resource_size_t:

drivers/mtd/onenand/omap2.c: In function 'omap2_onenand_probe':
drivers/mtd/onenand/omap2.c:536:54: error: format '%x' expects argument of type 'unsigned int', but argument 3 has type 'resource_size_t {aka long long unsigned int}' [-Werror=format=]
   dev_err(dev, "Cannot reserve memory region at 0x%08x, size: 0x%x\n",
drivers/mtd/onenand/omap2.c:536:66: error: format '%x' expects argument of type 'unsigned int', but argument 4 has type 'resource_size_t {aka long long unsigned int}' [-Werror=format=]

Changing the format string to the special %pR simplifies the code
and lets it do the right thing in that configuration, while avoiding
the warning.

Fixes: a758f50f10cf ("mtd: onenand: omap2: Configure driver from DT")
Signed-off-by: Arnd Bergmann 
Reviewed-by: Sebastian Reichel 
Reviewed-by: Peter Ujfalusi 
Signed-off-by: Boris Brezillon

mtd: onenand: samsung: remove incorrect __iomem annotation

2018-01-14T14:04:56+00:00

'page_buf' and 'oob_buf' are allocated with 'devm_kzalloc()' and should not
have __iomem decoration.

Remove these decorations and some useless casting.

Signed-off-by: Christophe JAILLET 
Signed-off-by: Boris Brezillon

mtd: onenand: omap2: Configure driver from DT

2018-01-12T15:41:15+00:00

Move away from platform data configuration and use pure DT approach.

Use generic probe function to deal with OneNAND node and remove now useless
gpmc_probe_onenand_child function. Import sync mode timing calculation
function from mach-omap2/gpmc-onenand.c

Signed-off-by: Ladislav Michl 
Reviewed-by: Peter Ujfalusi 
Tested-by: Tony Lindgren 
Tested-by: Aaro Koskinen 
Acked-by: Roger Quadros 
Signed-off-by: Boris Brezillon

mtd: onenand: omap2: Decouple DMA enabling from INT pin availability

2018-01-12T15:40:48+00:00

INT pin (gpio_irq) is not really needed for DMA but only for notification
when a command that needs wait has completed. DMA memcpy can be still used
even without gpio_irq available, so enable it unconditionally.

Signed-off-by: Ladislav Michl 
Reviewed-by: Peter Ujfalusi 
Tested-by: Tony Lindgren 
Tested-by: Aaro Koskinen 
Acked-by: Roger Quadros 
Signed-off-by: Boris Brezillon

mtd: onenand: omap2: Do not make delay for GPIO OMAP3 specific

2018-01-12T14:34:23+00:00

Second commit in driver history (782b7a367d81: "[MTD] [OneNAND] OMAP3:
add delay for GPIO") added quirk for waiting until GPIO line settle.
As DMA was disabled for OMAP2 boards, chances are this problem was
not OMAP3 specific and as it is just one register read, previous
test for SoC type is approximately as expensive as read itself.
Make delay unconditional, which allows removing SoC specific code
alltogether.

Signed-off-by: Ladislav Michl 
Reviewed-by: Peter Ujfalusi 
Reviewed-by: Sebastian Reichel 
Acked-by: Roger Quadros 
Tested-by: Tony Lindgren 
Tested-by: Aaro Koskinen 
Signed-off-by: Boris Brezillon

mtd: onenand: omap2: Convert to use dmaengine for memcpy

2018-01-12T14:34:21+00:00

Do not use the legacy and deprecated omap-dma interface for setting up the
memcpy.

Signed-off-by: Peter Ujfalusi 
Signed-off-by: Ladislav Michl 
Reviewed-by: Sebastian Reichel 
Acked-by: Roger Quadros 
Tested-by: Tony Lindgren 
Tested-by: Aaro Koskinen 
Signed-off-by: Boris Brezillon