2017-03-16 16:02:41 +08:00
|
|
|
Atmel NAND flash controller bindings
|
|
|
|
|
|
|
|
The NAND flash controller node should be defined under the EBI bus (see
|
|
|
|
Documentation/devicetree/bindings/memory-controllers/atmel,ebi.txt).
|
|
|
|
One or several NAND devices can be defined under this NAND controller.
|
|
|
|
The NAND controller might be connected to an ECC engine.
|
|
|
|
|
|
|
|
* NAND controller bindings:
|
|
|
|
|
|
|
|
Required properties:
|
|
|
|
- compatible: should be one of the following
|
|
|
|
"atmel,at91rm9200-nand-controller"
|
|
|
|
"atmel,at91sam9260-nand-controller"
|
|
|
|
"atmel,at91sam9261-nand-controller"
|
|
|
|
"atmel,at91sam9g45-nand-controller"
|
|
|
|
"atmel,sama5d3-nand-controller"
|
|
|
|
- ranges: empty ranges property to forward EBI ranges definitions.
|
|
|
|
- #address-cells: should be set to 2.
|
|
|
|
- #size-cells: should be set to 1.
|
|
|
|
- atmel,nfc-io: phandle to the NFC IO block. Only required for sama5d3
|
|
|
|
controllers.
|
|
|
|
- atmel,nfc-sram: phandle to the NFC SRAM block. Only required for sama5d3
|
|
|
|
controllers.
|
|
|
|
|
|
|
|
Optional properties:
|
|
|
|
- ecc-engine: phandle to the PMECC block. Only meaningful if the SoC embeds
|
|
|
|
a PMECC engine.
|
|
|
|
|
|
|
|
* NAND device/chip bindings:
|
|
|
|
|
|
|
|
Required properties:
|
|
|
|
- reg: describes the CS lines assigned to the NAND device. If the NAND device
|
|
|
|
exposes multiple CS lines (multi-dies chips), your reg property will
|
|
|
|
contain X tuples of 3 entries.
|
|
|
|
1st entry: the CS line this NAND chip is connected to
|
|
|
|
2nd entry: the base offset of the memory region assigned to this
|
|
|
|
device (always 0)
|
|
|
|
3rd entry: the memory region size (always 0x800000)
|
|
|
|
|
|
|
|
Optional properties:
|
|
|
|
- rb-gpios: the GPIO(s) used to check the Ready/Busy status of the NAND.
|
|
|
|
- cs-gpios: the GPIO(s) used to control the CS line.
|
|
|
|
- det-gpios: the GPIO used to detect if a Smartmedia Card is present.
|
|
|
|
- atmel,rb: an integer identifying the native Ready/Busy pin. Only meaningful
|
|
|
|
on sama5 SoCs.
|
|
|
|
|
|
|
|
All generic properties described in
|
|
|
|
Documentation/devicetree/bindings/mtd/{common,nand}.txt also apply to the NAND
|
|
|
|
device node, and NAND partitions should be defined under the NAND node as
|
|
|
|
described in Documentation/devicetree/bindings/mtd/partition.txt.
|
|
|
|
|
|
|
|
* ECC engine (PMECC) bindings:
|
|
|
|
|
|
|
|
Required properties:
|
|
|
|
- compatible: should be one of the following
|
|
|
|
"atmel,at91sam9g45-pmecc"
|
|
|
|
"atmel,sama5d4-pmecc"
|
|
|
|
"atmel,sama5d2-pmecc"
|
|
|
|
- reg: should contain 2 register ranges. The first one is pointing to the PMECC
|
|
|
|
block, and the second one to the PMECC_ERRLOC block.
|
|
|
|
|
2017-05-30 17:20:51 +08:00
|
|
|
* SAMA5 NFC I/O bindings:
|
|
|
|
|
|
|
|
SAMA5 SoCs embed an advanced NAND controller logic to automate READ/WRITE page
|
|
|
|
operations. This interface to this logic is placed in a separate I/O range and
|
|
|
|
should thus have its own DT node.
|
|
|
|
|
|
|
|
- compatible: should be "atmel,sama5d3-nfc-io", "syscon".
|
|
|
|
- reg: should contain the I/O range used to interact with the NFC logic.
|
|
|
|
|
2017-03-16 16:02:41 +08:00
|
|
|
Example:
|
|
|
|
|
2017-05-30 17:20:51 +08:00
|
|
|
nfc_io: nfc-io@70000000 {
|
|
|
|
compatible = "atmel,sama5d3-nfc-io", "syscon";
|
|
|
|
reg = <0x70000000 0x8000000>;
|
|
|
|
};
|
|
|
|
|
2017-03-16 16:02:41 +08:00
|
|
|
pmecc: ecc-engine@ffffc070 {
|
|
|
|
compatible = "atmel,at91sam9g45-pmecc";
|
|
|
|
reg = <0xffffc070 0x490>,
|
|
|
|
<0xffffc500 0x100>;
|
|
|
|
};
|
|
|
|
|
|
|
|
ebi: ebi@10000000 {
|
|
|
|
compatible = "atmel,sama5d3-ebi";
|
|
|
|
#address-cells = <2>;
|
|
|
|
#size-cells = <1>;
|
|
|
|
atmel,smc = <&hsmc>;
|
|
|
|
reg = <0x10000000 0x10000000
|
|
|
|
0x40000000 0x30000000>;
|
|
|
|
ranges = <0x0 0x0 0x10000000 0x10000000
|
|
|
|
0x1 0x0 0x40000000 0x10000000
|
|
|
|
0x2 0x0 0x50000000 0x10000000
|
|
|
|
0x3 0x0 0x60000000 0x10000000>;
|
|
|
|
clocks = <&mck>;
|
|
|
|
|
|
|
|
nand_controller: nand-controller {
|
|
|
|
compatible = "atmel,sama5d3-nand-controller";
|
|
|
|
atmel,nfc-sram = <&nfc_sram>;
|
|
|
|
atmel,nfc-io = <&nfc_io>;
|
|
|
|
ecc-engine = <&pmecc>;
|
|
|
|
#address-cells = <2>;
|
|
|
|
#size-cells = <1>;
|
|
|
|
ranges;
|
|
|
|
|
|
|
|
nand@3 {
|
|
|
|
reg = <0x3 0x0 0x800000>;
|
|
|
|
atmel,rb = <0>;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Put generic NAND/MTD properties and
|
|
|
|
* subnodes here.
|
|
|
|
*/
|
|
|
|
};
|
|
|
|
};
|
|
|
|
};
|
|
|
|
|
|
|
|
-----------------------------------------------------------------------
|
|
|
|
|
|
|
|
Deprecated bindings (should not be used in new device trees):
|
2012-01-26 02:11:06 +08:00
|
|
|
|
|
|
|
Required properties:
|
2016-02-10 17:56:25 +08:00
|
|
|
- compatible: The possible values are:
|
|
|
|
"atmel,at91rm9200-nand"
|
|
|
|
"atmel,sama5d2-nand"
|
|
|
|
"atmel,sama5d4-nand"
|
2012-01-26 02:11:06 +08:00
|
|
|
- reg : should specify localbus address and size used for the chip,
|
2012-06-29 17:47:54 +08:00
|
|
|
and hardware ECC controller if available.
|
|
|
|
If the hardware ECC is PMECC, it should contain address and size for
|
2014-10-11 18:01:50 +08:00
|
|
|
PMECC and PMECC Error Location controller.
|
|
|
|
The PMECC lookup table address and size in ROM is optional. If not
|
|
|
|
specified, driver will build it in runtime.
|
2012-01-26 02:11:06 +08:00
|
|
|
- atmel,nand-addr-offset : offset for the address latch.
|
|
|
|
- atmel,nand-cmd-offset : offset for the command latch.
|
|
|
|
- #address-cells, #size-cells : Must be present if the device has sub-nodes
|
|
|
|
representing partitions.
|
|
|
|
|
|
|
|
- gpios : specifies the gpio pins to control the NAND device. detect is an
|
|
|
|
optional gpio and may be set to 0 if not present.
|
|
|
|
|
|
|
|
Optional properties:
|
2013-05-09 15:34:55 +08:00
|
|
|
- atmel,nand-has-dma : boolean to support dma transfer for nand read/write.
|
2012-01-26 02:11:06 +08:00
|
|
|
- nand-ecc-mode : String, operation mode of the NAND ecc mode, soft by default.
|
|
|
|
Supported values are: "none", "soft", "hw", "hw_syndrome", "hw_oob_first",
|
|
|
|
"soft_bch".
|
2016-02-10 17:56:24 +08:00
|
|
|
- atmel,has-pmecc : boolean to enable Programmable Multibit ECC hardware,
|
|
|
|
capable of BCH encoding and decoding, on devices where it is present.
|
2012-06-29 17:47:54 +08:00
|
|
|
- atmel,pmecc-cap : error correct capability for Programmable Multibit ECC
|
2016-02-10 17:56:26 +08:00
|
|
|
Controller. Supported values are: 2, 4, 8, 12, 24. If the compatible string
|
|
|
|
is "atmel,sama5d2-nand", 32 is also valid.
|
2012-06-29 17:47:54 +08:00
|
|
|
- atmel,pmecc-sector-size : sector size for ECC computation. Supported values
|
|
|
|
are: 512, 1024.
|
|
|
|
- atmel,pmecc-lookup-table-offset : includes two offsets of lookup table in ROM
|
|
|
|
for different sector size. First one is for sector size 512, the next is for
|
2014-10-11 18:01:50 +08:00
|
|
|
sector size 1024. If not specified, driver will build the table in runtime.
|
2012-01-26 02:11:06 +08:00
|
|
|
- nand-bus-width : 8 or 16 bus width if not present 8
|
|
|
|
- nand-on-flash-bbt: boolean to enable on flash bbt option if not present false
|
2016-02-10 17:56:24 +08:00
|
|
|
|
|
|
|
Nand Flash Controller(NFC) is an optional sub-node
|
|
|
|
Required properties:
|
2016-05-09 14:51:18 +08:00
|
|
|
- compatible : "atmel,sama5d3-nfc".
|
2016-02-10 17:56:24 +08:00
|
|
|
- reg : should specify the address and size used for NFC command registers,
|
|
|
|
NFC registers and NFC SRAM. NFC SRAM address and size can be absent
|
|
|
|
if don't want to use it.
|
|
|
|
- clocks: phandle to the peripheral clock
|
|
|
|
Optional properties:
|
|
|
|
- atmel,write-by-sram: boolean to enable NFC write by SRAM.
|
2012-01-26 02:11:06 +08:00
|
|
|
|
|
|
|
Examples:
|
|
|
|
nand0: nand@40000000,0 {
|
|
|
|
compatible = "atmel,at91rm9200-nand";
|
|
|
|
#address-cells = <1>;
|
|
|
|
#size-cells = <1>;
|
|
|
|
reg = <0x40000000 0x10000000
|
|
|
|
0xffffe800 0x200
|
|
|
|
>;
|
2012-03-22 21:48:47 +08:00
|
|
|
atmel,nand-addr-offset = <21>; /* ale */
|
|
|
|
atmel,nand-cmd-offset = <22>; /* cle */
|
2012-01-26 02:11:06 +08:00
|
|
|
nand-on-flash-bbt;
|
|
|
|
nand-ecc-mode = "soft";
|
2012-03-22 21:48:47 +08:00
|
|
|
gpios = <&pioC 13 0 /* rdy */
|
|
|
|
&pioC 14 0 /* nce */
|
|
|
|
0 /* cd */
|
2012-01-26 02:11:06 +08:00
|
|
|
>;
|
|
|
|
partition@0 {
|
|
|
|
...
|
|
|
|
};
|
|
|
|
};
|
2012-06-29 17:47:54 +08:00
|
|
|
|
|
|
|
/* for PMECC supported chips */
|
|
|
|
nand0: nand@40000000 {
|
|
|
|
compatible = "atmel,at91rm9200-nand";
|
|
|
|
#address-cells = <1>;
|
|
|
|
#size-cells = <1>;
|
|
|
|
reg = < 0x40000000 0x10000000 /* bus addr & size */
|
|
|
|
0xffffe000 0x00000600 /* PMECC addr & size */
|
|
|
|
0xffffe600 0x00000200 /* PMECC ERRLOC addr & size */
|
|
|
|
0x00100000 0x00100000 /* ROM addr & size */
|
|
|
|
>;
|
|
|
|
atmel,nand-addr-offset = <21>; /* ale */
|
|
|
|
atmel,nand-cmd-offset = <22>; /* cle */
|
|
|
|
nand-on-flash-bbt;
|
|
|
|
nand-ecc-mode = "hw";
|
|
|
|
atmel,has-pmecc; /* enable PMECC */
|
|
|
|
atmel,pmecc-cap = <2>;
|
|
|
|
atmel,pmecc-sector-size = <512>;
|
|
|
|
atmel,pmecc-lookup-table-offset = <0x8000 0x10000>;
|
|
|
|
gpios = <&pioD 5 0 /* rdy */
|
|
|
|
&pioD 4 0 /* nce */
|
|
|
|
0 /* cd */
|
|
|
|
>;
|
|
|
|
partition@0 {
|
|
|
|
...
|
|
|
|
};
|
|
|
|
};
|
mtd: atmel_nand: add Nand Flash Controller (NFC) support
Nand Flash Controller (NFC) can handle automatic transfers, sending the
commands and address cycles to the NAND Flash.
To use NFC in this driver, user needs to add NFC child node in nand flash
driver. The NFC child node includes NFC's compatible string and regiters
of the address and size of NFC command registers, NFC registers (embedded
in HSMC) and NFC SRAM.
Also user need to set up the HSMC irq, which use to check whether nfc
command is finish or not.
This driver has been tested on SAMA5D3X-EK board with JFFS2, YAFFS,
UBIFS and mtd-utils.
I put the part of the mtd_speedtest result here for your information.
>From the mtd_speedtest, we can see the NFC will reduce the %50 of cpu load
when writing nand flash. No change when reading.
In the meantime, the speed will be slow about %8.
- commands use to test:
#insmod /mnt/mtd_speedtest.ko dev=2 &
#top -n 30 -d 1 | grep speedtest
- test result:
Before the patch:
=================================================
mtd_speedtest: MTD device: 2
mtd_speedtest: MTD device size 41943040, eraseblock size 131072, page size 2048, count of eraseblocks 320, pages per eraseblock 64, OOB size 64
515 495 root R 1164 0% 93% insmod /mnt/mtd_speedtest.ko dev=2
515 495 root R 1164 0% 98% insmod /mnt/mtd_speedtest.ko dev=2
515 495 root R 1164 0% 99% insmod /mnt/mtd_speedtest.ko dev=2
mtd_speedtest: eraseblock write speed is 5768 KiB/s
mtd_speedtest: testing eraseblock read speed
515 495 root R 1164 0% 92% insmod /mnt/mtd_speedtest.ko dev=2
515 495 root R 1164 0% 91% insmod /mnt/mtd_speedtest.ko dev=2
515 495 root R 1164 0% 94% insmod /mnt/mtd_speedtest.ko dev=2
mtd_speedtest: eraseblock read speed is 5932 KiB/s
mtd_speedtest: testing page write speed
515 495 root R 1164 0% 94% insmod /mnt/mtd_speedtest.ko dev=2
515 495 root R 1164 0% 98% insmod /mnt/mtd_speedtest.ko dev=2
515 495 root R 1164 0% 98% insmod /mnt/mtd_speedtest.ko dev=2
mtd_speedtest: page write speed is 5770 KiB/s
mtd_speedtest: testing page read speed
515 495 root R 1164 0% 91% insmod /mnt/mtd_speedtest.ko dev=2
515 495 root R 1164 0% 89% insmod /mnt/mtd_speedtest.ko dev=2
515 495 root R 1164 0% 91% insmod /mnt/mtd_speedtest.ko dev=2
mtd_speedtest: page read speed is 5910 KiB/s
After the patch:
=================================================
mtd_speedtest: MTD device: 2
mtd_speedtest: MTD device size 41943040, eraseblock size 131072, page size 2048, count of eraseblocks 320, pages per eraseblock 64, OOB size 64
mtd_speedtest: testing eraseblock write speed
509 495 root D 1164 0% 49% insmod /mnt/mtd_speedtest.ko dev=2
509 495 root D 1164 0% 50% insmod /mnt/mtd_speedtest.ko dev=2
509 495 root D 1164 0% 47% insmod /mnt/mtd_speedtest.ko dev=2
mtd_speedtest: eraseblock write speed is 5370 KiB/s
mtd_speedtest: testing eraseblock read speed
509 495 root R 1164 0% 92% insmod /mnt/mtd_speedtest.ko dev=2
509 495 root R 1164 0% 91% insmod /mnt/mtd_speedtest.ko dev=2
509 495 root R 1164 0% 95% insmod /mnt/mtd_speedtest.ko dev=2
mtd_speedtest: eraseblock read speed is 5715 KiB/s
mtd_speedtest: testing page write speed
509 495 root D 1164 0% 48% insmod /mnt/mtd_speedtest.ko dev=2
509 495 root D 1164 0% 47% insmod /mnt/mtd_speedtest.ko dev=2
509 495 root D 1164 0% 50% insmod /mnt/mtd_speedtest.ko dev=2
mtd_speedtest: page write speed is 5224 KiB/s
mtd_speedtest: testing page read speed
509 495 root R 1164 0% 89% insmod /mnt/mtd_speedtest.ko dev=2
509 495 root R 1164 0% 94% insmod /mnt/mtd_speedtest.ko dev=2
509 495 root R 1164 0% 93% insmod /mnt/mtd_speedtest.ko dev=2
mtd_speedtest: page read speed is 5641 KiB/s
Signed-off-by: Josh Wu <josh.wu@atmel.com>
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
2013-08-05 19:14:35 +08:00
|
|
|
|
|
|
|
/* for NFC supported chips */
|
|
|
|
nand0: nand@40000000 {
|
|
|
|
compatible = "atmel,at91rm9200-nand";
|
|
|
|
#address-cells = <1>;
|
|
|
|
#size-cells = <1>;
|
|
|
|
ranges;
|
|
|
|
...
|
|
|
|
nfc@70000000 {
|
|
|
|
compatible = "atmel,sama5d3-nfc";
|
|
|
|
#address-cells = <1>;
|
|
|
|
#size-cells = <1>;
|
2014-09-13 07:23:59 +08:00
|
|
|
clocks = <&hsmc_clk>
|
mtd: atmel_nand: add Nand Flash Controller (NFC) support
Nand Flash Controller (NFC) can handle automatic transfers, sending the
commands and address cycles to the NAND Flash.
To use NFC in this driver, user needs to add NFC child node in nand flash
driver. The NFC child node includes NFC's compatible string and regiters
of the address and size of NFC command registers, NFC registers (embedded
in HSMC) and NFC SRAM.
Also user need to set up the HSMC irq, which use to check whether nfc
command is finish or not.
This driver has been tested on SAMA5D3X-EK board with JFFS2, YAFFS,
UBIFS and mtd-utils.
I put the part of the mtd_speedtest result here for your information.
>From the mtd_speedtest, we can see the NFC will reduce the %50 of cpu load
when writing nand flash. No change when reading.
In the meantime, the speed will be slow about %8.
- commands use to test:
#insmod /mnt/mtd_speedtest.ko dev=2 &
#top -n 30 -d 1 | grep speedtest
- test result:
Before the patch:
=================================================
mtd_speedtest: MTD device: 2
mtd_speedtest: MTD device size 41943040, eraseblock size 131072, page size 2048, count of eraseblocks 320, pages per eraseblock 64, OOB size 64
515 495 root R 1164 0% 93% insmod /mnt/mtd_speedtest.ko dev=2
515 495 root R 1164 0% 98% insmod /mnt/mtd_speedtest.ko dev=2
515 495 root R 1164 0% 99% insmod /mnt/mtd_speedtest.ko dev=2
mtd_speedtest: eraseblock write speed is 5768 KiB/s
mtd_speedtest: testing eraseblock read speed
515 495 root R 1164 0% 92% insmod /mnt/mtd_speedtest.ko dev=2
515 495 root R 1164 0% 91% insmod /mnt/mtd_speedtest.ko dev=2
515 495 root R 1164 0% 94% insmod /mnt/mtd_speedtest.ko dev=2
mtd_speedtest: eraseblock read speed is 5932 KiB/s
mtd_speedtest: testing page write speed
515 495 root R 1164 0% 94% insmod /mnt/mtd_speedtest.ko dev=2
515 495 root R 1164 0% 98% insmod /mnt/mtd_speedtest.ko dev=2
515 495 root R 1164 0% 98% insmod /mnt/mtd_speedtest.ko dev=2
mtd_speedtest: page write speed is 5770 KiB/s
mtd_speedtest: testing page read speed
515 495 root R 1164 0% 91% insmod /mnt/mtd_speedtest.ko dev=2
515 495 root R 1164 0% 89% insmod /mnt/mtd_speedtest.ko dev=2
515 495 root R 1164 0% 91% insmod /mnt/mtd_speedtest.ko dev=2
mtd_speedtest: page read speed is 5910 KiB/s
After the patch:
=================================================
mtd_speedtest: MTD device: 2
mtd_speedtest: MTD device size 41943040, eraseblock size 131072, page size 2048, count of eraseblocks 320, pages per eraseblock 64, OOB size 64
mtd_speedtest: testing eraseblock write speed
509 495 root D 1164 0% 49% insmod /mnt/mtd_speedtest.ko dev=2
509 495 root D 1164 0% 50% insmod /mnt/mtd_speedtest.ko dev=2
509 495 root D 1164 0% 47% insmod /mnt/mtd_speedtest.ko dev=2
mtd_speedtest: eraseblock write speed is 5370 KiB/s
mtd_speedtest: testing eraseblock read speed
509 495 root R 1164 0% 92% insmod /mnt/mtd_speedtest.ko dev=2
509 495 root R 1164 0% 91% insmod /mnt/mtd_speedtest.ko dev=2
509 495 root R 1164 0% 95% insmod /mnt/mtd_speedtest.ko dev=2
mtd_speedtest: eraseblock read speed is 5715 KiB/s
mtd_speedtest: testing page write speed
509 495 root D 1164 0% 48% insmod /mnt/mtd_speedtest.ko dev=2
509 495 root D 1164 0% 47% insmod /mnt/mtd_speedtest.ko dev=2
509 495 root D 1164 0% 50% insmod /mnt/mtd_speedtest.ko dev=2
mtd_speedtest: page write speed is 5224 KiB/s
mtd_speedtest: testing page read speed
509 495 root R 1164 0% 89% insmod /mnt/mtd_speedtest.ko dev=2
509 495 root R 1164 0% 94% insmod /mnt/mtd_speedtest.ko dev=2
509 495 root R 1164 0% 93% insmod /mnt/mtd_speedtest.ko dev=2
mtd_speedtest: page read speed is 5641 KiB/s
Signed-off-by: Josh Wu <josh.wu@atmel.com>
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
2013-08-05 19:14:35 +08:00
|
|
|
reg = <
|
|
|
|
0x70000000 0x10000000 /* NFC Command Registers */
|
|
|
|
0xffffc000 0x00000070 /* NFC HSMC regs */
|
|
|
|
0x00200000 0x00100000 /* NFC SRAM banks */
|
|
|
|
>;
|
|
|
|
};
|
|
|
|
};
|