mtd: docg4: remove badblock_pattern usage

We can extract this information from nand_chip.badblockpos, so don't use
nand_chip.badblock_pattern.

This is part of an effort to eliminate some use of
nand_chip.badblock_pattern.

Signed-off-by: Brian Norris <computersforpeace@gmail.com>
mtd: gpmi-nand: remove badblock_pattern

This bad block pattern can be replicated easily enough with
nand_chip.badblockpos and disabling 2nd- and last-page scanning.

This is part of an effort to remove nand_chip.badblock_pattern.

Signed-off-by: Brian Norris <computersforpeace@gmail.com>
mtd: omap2: remove badblock_pattern

This bad block pattern seems to have found its way into the driver from
some legacy code. This driver sets NAND_SKIP_BBTSCAN anyway, so this bad
block pattern will never be used.

This is part of a clean up process in which the
nand_chip.badblock_pattern field may end up being totally unnecessary.

Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Cc: Ivan Djelic <ivan.djelic@parrot.com>
Cc: Sukumar Ghorai <s-ghorai@ti.com>
mtd: sh_flctl: remove badblock_pattern

These bad block patterns can be re-implemented simply with
nand_chip.badblockpos and nand_chip.options. (Note: the "largepage"
pattern, with len=2, is not replicated properly; normally 8-bit buswidth
implies a single-byte bad block pattern.)

This is part of and effort to remove nand_chip.badblock_pattern.

Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Cc: Bastian Hecht <hechtb@gmail.com>
mtd: nand: tmp - clear out some badblock_pattern