Skip to content

RFC mtd: bcm47xxnflash: adding support for new NANDs

Rafał Miłecki linux-mtd 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest3 patches 2 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3Revert "mtd: bcm47xxnflash: Use module_platform_driver"drivers/mtd/nand/bcm47xxnflash/main.c+19 -10 replies
2/3mtd: bcm47xxnflash: add separated config for platform driverdrivers/mtd/nand/Kconfig drivers/mtd/nand/bcm47xxnflash/Makefile drivers/mtd/nand/bcm47xxnflash/main.c+25 -70 replies
3/3mtd: bcm47xxnflash: prepare for adding BCMA driverdrivers/mtd/nand/Kconfig drivers/mtd/nand/bcm47xxnflash/main.c+60 -30 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC 0/3] mtd: bcm47xxnflash: adding support for new NANDs

New Broadcom SoCs have NAND flashes attached & programmed in a totally different way. Instead of accessing them with help of ChipCommon core, they can be used directly.

To support them we can extend bcm47xxnflash in the way this patches implements. However almost nothing in the code will be shared between support for old and new devices.

How should we proceed? Implement it that way anyway? Or maybe writing a separated driver (bcm53xxnflash?) would be a better idea?

Rafał Miłecki (3):
Revert "mtd: bcm47xxnflash: Use module_platform_driver"
mtd: bcm47xxnflash: add separated config for platform driver
mtd: bcm47xxnflash: prepare for adding BCMA driver

 drivers/mtd/nand/Kconfig                | 25 ++++++++---
 drivers/mtd/nand/bcm47xxnflash/Makefile |  2 +-
 drivers/mtd/nand/bcm47xxnflash/main.c   | 80 ++++++++++++++++++++++++++++++++-
 3 files changed, 100 insertions(+), 7 deletions(-)
Signature · 1 line
1.8.4.5