linux.git/drivers/mtd/mtdcore.c, branch v4.13

mtd: Fix check in mtd_unpoint()

2017-07-08T00:57:59+00:00

The code checks that ->_point is not NULL, but we should actually check
->_unpoint value which is dereferenced a few lines after the check.

Signed-off-by: Boris Brezillon 
Signed-off-by: Brian Norris

bdi: Drop 'parent' argument from bdi_register[_va]()

2017-04-20T18:09:55+00:00

Drop 'parent' argument of bdi_register() and bdi_register_va().  It is
always NULL.

Reviewed-by: Christoph Hellwig 
Signed-off-by: Jan Kara 
Signed-off-by: Jens Axboe

mtd: Convert to dynamically allocated bdi infrastructure

2017-04-20T18:09:55+00:00

MTD already allocates backing_dev_info dynamically. Convert it to use
generic infrastructure for this including proper refcounting. We drop
mtd->backing_dev_info as its only use was to pass mtd_bdi pointer from
one file into another and if we wanted to keep that in a clean way, we'd
have to make mtd hold and drop bdi reference as needed which seems
pointless for passing one global pointer...

CC: David Woodhouse 
CC: Brian Norris 
CC: linux-mtd@lists.infradead.org
Reviewed-by: Christoph Hellwig 
Signed-off-by: Jan Kara 
Signed-off-by: Jens Axboe

mtd: fix typos in ooblayout comment blocks

2017-02-08T21:32:08+00:00

- "This functions return ..." -> "This function returns ..."
 - "I you want ..." -> "If you want ..."

Signed-off-by: Masahiro Yamada 
Acked-by: Boris Brezillon 
Signed-off-by: Brian Norris

mtd: Allocate bdi objects dynamically

2016-12-01T18:03:17+00:00

The MTD backing dev info objects mtd_bdi was statically allocated.
So when MTD is built as a loadable module, this object fall in the
vmalloc address space.

The problem with that, is that the BDI APIs use wake_up_bit(), which calls
virt_to_page() to retrieve the memory zone of the page containing the
wait_queue to wake up, and virt_to_page() is not valid for vmalloc or
highmem addresses.

Fix this by allocating the BDI objects dynamically with kmalloc. The
objects now fall in the logical address space so that BDI APIs will
work in all cases (mtd builtin or module).

Signed-off-by: Steve Longerbeam 
Signed-off-by: Jim Baxter 
Signed-off-by: Sandeep Jain 
Reviewed-by: Richard Weinberger 
Reviewed-by: Marek Vasut 
Signed-off-by: Brian Norris

mtd: remove unneeded initializer in mtd_ooblayout_count_bytes()

2016-11-19T18:31:34+00:00

There is no need to initialize oobregion since it will be filled by
the iterator.

This function is called with mtd_ooblayout_free or mtd_ooblayout_ecc
for the iterator; both of them calls memset() to clear the oobregion.

Signed-off-by: Masahiro Yamada 
Reviewed-by: Marek Vasut 
Signed-off-by: Boris Brezillon

mtd: use min_t() to refactor mtd_ooblayout_{get, set}_bytes()

2016-11-19T18:31:32+00:00

I hope this will make the code a little more readable.

Signed-off-by: Masahiro Yamada 
Reviewed-by: Marek Vasut 
Signed-off-by: Boris Brezillon

mtd: remove unneeded initializer in mtd_ooblayout_{get, set}_bytes()

2016-11-19T18:31:29+00:00

There is no need to initialize oobregion and section since they will
be filled by mtd_ooblayout_find_region().

Signed-off-by: Masahiro Yamada 
Reviewed-by: Marek Vasut 
Signed-off-by: Boris Brezillon

treewide: remove redundant #include

2016-10-11T22:06:33+00:00

Kernel source files need not include  explicitly
because the top Makefile forces to include it with:

  -include $(srctree)/include/linux/kconfig.h

This commit removes explicit includes except the following:

  * arch/s390/include/asm/facilities_src.h
  * tools/testing/radix-tree/linux/kernel.h

These two are used for host programs.

Link: http://lkml.kernel.org/r/1473656164-11929-1-git-send-email-yamada.masahiro@socionext.com
Signed-off-by: Masahiro Yamada 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

mtd: introduce the mtd_pairing_scheme concept

2016-09-15T14:47:56+00:00

MLC and TLC NAND devices are using NAND cells exposing more than one bit,
but instead of attaching all the bits in a given cell to a single NAND
page, each bit is usually attached to a different page. This concept is
called 'page pairing', and has significant impacts on the flash storage
usage.
The main problem showed by these devices is that interrupting a page
program operation may not only corrupt the page we are programming
but also the page it is paired with, hence the need to expose to MTD
users the pairing scheme information.

The pairing APIs allows one to query pairing information attached to a
given page (here called wunit), or the other way around (the wunit
pointed by pairing information).
It also provides several helpers to help the conversion between absolute
offsets and wunits, and query the number of pairing groups.

Signed-off-by: Boris Brezillon 
Reviewed-by: Brian Norris