-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge tag 'for-linus-20161216' of git://git.infradead.org/linux-mtd
Pull MTD updates from Brian Norris: "Nothing enormous here, though notably we have some of the first work of a few new maintainers. I think for now I'll still be sending pull requests, but that's open to change in the future. Summary: Core: - dynamic BDI object allocation (resolves some problems when built as a module) - cleanups in the ooblayout handling NAND: - new tango NAND controller driver - new ox820 NAND controller driver - addition of a new full-ID entry in the nand_ids table - rework of the s3c240 driver to support DT - extension of the nand_sdr_timings to expose tCCS, tPROG and tR - addition of a new flag to ask the core to wait for tCCS when sending a RNDIN/RNDOUT command - addition of a new flag to ask the core to let the controller driver send the READ/PROGPAGE command Minor fixes/cleanup/cosmetic changes: - properly support 512 ECC step size in the sunxi driver - improve the error messages in the PXA probe path - fix module autoload in the omap2 driver - cleanup of several nand drivers to return nand_scan{_tail}() error code instead of returning -EIO - various cleanups in the denali driver - fix an error check in nandsim SPI NOR: - new flash IDs - wait for Spansion flash to be ready after quad-enable - error handling fixes for Candence QSPI - constify some structures in Freescale QSPI driver" * tag 'for-linus-20161216' of git://git.infradead.org/linux-mtd: (71 commits) mtd: Allocate bdi objects dynamically mtd: nand: tango: Add standard legalese header mtd: maps: add missing iounmap() in error path mtd: spi-nor: constify fsl_qspi_devtype_data mtd: spi-nor: Add support for mr25h40 mtd: spi-nor: Add support for N25Q016A mtd: spi-nor: Add at25df321 spi-nor flash support mtd: spi-nor: Fix some error codes in cqspi_setup_flash() mtd: spi-nor: Off by one in cqspi_setup_flash() mtd: spi-nor: add support for s25fl208k mtd: spi-nor: fix flags for s25fl128s mtd: spi-nor: fix spansion quad enable mtd: spi-nor: add Macronix mx25u25635f to list of known devices. mtd: mtdswap: fix spelling mistake "erassure" -> "erasure" mtd: bcm47xxpart: fix parsing first block after aligned TRX mtd: nand: tango: Use nand_to_mtd() instead of directly accessing chip->mtd mtd: remove unneeded initializer in mtd_ooblayout_count_bytes() mtd: use min_t() to refactor mtd_ooblayout_{get, set}_bytes() mtd: remove unneeded initializer in mtd_ooblayout_{get, set}_bytes() mtd: nand: nandsim: fix error check ...
- Loading branch information
Showing
64 changed files
with
1,555 additions
and
351 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
* Oxford Semiconductor OXNAS NAND Controller | ||
|
||
Please refer to nand.txt for generic information regarding MTD NAND bindings. | ||
|
||
Required properties: | ||
- compatible: "oxsemi,ox820-nand" | ||
- reg: Base address and length for NAND mapped memory. | ||
|
||
Optional Properties: | ||
- clocks: phandle to the NAND gate clock if needed. | ||
- resets: phandle to the NAND reset control if needed. | ||
|
||
Example: | ||
|
||
nandc: nand-controller@41000000 { | ||
compatible = "oxsemi,ox820-nand"; | ||
reg = <0x41000000 0x100000>; | ||
clocks = <&stdclk CLK_820_NAND>; | ||
resets = <&reset RESET_NAND>; | ||
#address-cells = <1>; | ||
#size-cells = <0>; | ||
|
||
nand@0 { | ||
reg = <0>; | ||
#address-cells = <1>; | ||
#size-cells = <1>; | ||
nand-ecc-mode = "soft"; | ||
nand-ecc-algo = "hamming"; | ||
|
||
partition@0 { | ||
label = "boot"; | ||
reg = <0x00000000 0x00e00000>; | ||
read-only; | ||
}; | ||
|
||
partition@e00000 { | ||
label = "ubi"; | ||
reg = <0x00e00000 0x07200000>; | ||
}; | ||
}; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,56 @@ | ||
* Samsung S3C2410 and compatible NAND flash controller | ||
|
||
Required properties: | ||
- compatible : The possible values are: | ||
"samsung,s3c2410-nand" | ||
"samsung,s3c2412-nand" | ||
"samsung,s3c2440-nand" | ||
- reg : register's location and length. | ||
- #address-cells, #size-cells : see nand.txt | ||
- clocks : phandle to the nand controller clock | ||
- clock-names : must contain "nand" | ||
|
||
Optional child nodes: | ||
Child nodes representing the available nand chips. | ||
|
||
Optional child properties: | ||
- nand-ecc-mode : see nand.txt | ||
- nand-on-flash-bbt : see nand.txt | ||
|
||
Each child device node may optionally contain a 'partitions' sub-node, | ||
which further contains sub-nodes describing the flash partition mapping. | ||
See partition.txt for more detail. | ||
|
||
Example: | ||
|
||
nand-controller@4e000000 { | ||
compatible = "samsung,s3c2440-nand"; | ||
reg = <0x4e000000 0x40>; | ||
|
||
#address-cells = <1>; | ||
#size-cells = <0>; | ||
|
||
clocks = <&clocks HCLK_NAND>; | ||
clock-names = "nand"; | ||
|
||
nand { | ||
nand-ecc-mode = "soft"; | ||
nand-on-flash-bbt; | ||
|
||
partitions { | ||
compatible = "fixed-partitions"; | ||
#address-cells = <1>; | ||
#size-cells = <1>; | ||
|
||
partition@0 { | ||
label = "u-boot"; | ||
reg = <0 0x040000>; | ||
}; | ||
|
||
partition@40000 { | ||
label = "kernel"; | ||
reg = <0x040000 0x500000>; | ||
}; | ||
}; | ||
}; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
Sigma Designs Tango4 NAND Flash Controller (NFC) | ||
|
||
Required properties: | ||
|
||
- compatible: "sigma,smp8758-nand" | ||
- reg: address/size of nfc_reg, nfc_mem, and pbus_reg | ||
- dmas: reference to the DMA channel used by the controller | ||
- dma-names: "nfc_sbox" | ||
- clocks: reference to the system clock | ||
- #address-cells: <1> | ||
- #size-cells: <0> | ||
|
||
Children nodes represent the available NAND chips. | ||
See Documentation/devicetree/bindings/mtd/nand.txt for generic bindings. | ||
|
||
Example: | ||
|
||
nandc: nand-controller@2c000 { | ||
compatible = "sigma,smp8758-nand"; | ||
reg = <0x2c000 0x30 0x2d000 0x800 0x20000 0x1000>; | ||
dmas = <&dma0 3>; | ||
dma-names = "nfc_sbox"; | ||
clocks = <&clkgen SYS_CLK>; | ||
#address-cells = <1>; | ||
#size-cells = <0>; | ||
|
||
nand@0 { | ||
reg = <0>; /* CS0 */ | ||
nand-ecc-strength = <14>; | ||
nand-ecc-step-size = <1024>; | ||
}; | ||
|
||
nand@1 { | ||
reg = <1>; /* CS1 */ | ||
nand-ecc-strength = <14>; | ||
nand-ecc-step-size = <1024>; | ||
}; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.