1Device tree bindings for GPMC connected OneNANDs 2 3GPMC connected OneNAND (found on OMAP boards) are represented as child nodes of 4the GPMC controller with a name of "onenand". 5 6All timing relevant properties as well as generic gpmc child properties are 7explained in a separate documents - please refer to 8Documentation/devicetree/bindings/memory-controllers/omap-gpmc.txt 9 10Required properties: 11 12 - compatible: "ti,omap2-onenand" 13 - reg: The CS line the peripheral is connected to 14 - gpmc,device-width: Width of the ONENAND device connected to the GPMC 15 in bytes. Must be 1 or 2. 16 17Optional properties: 18 19 - int-gpios: GPIO specifier for the INT pin. 20 21For inline partition table parsing (optional): 22 23 - #address-cells: should be set to 1 24 - #size-cells: should be set to 1 25 26Example for an OMAP3430 board: 27 28 gpmc: gpmc@6e000000 { 29 compatible = "ti,omap3430-gpmc"; 30 ti,hwmods = "gpmc"; 31 reg = <0x6e000000 0x1000000>; 32 interrupts = <20>; 33 gpmc,num-cs = <8>; 34 gpmc,num-waitpins = <4>; 35 #address-cells = <2>; 36 #size-cells = <1>; 37 38 onenand@0 { 39 compatible = "ti,omap2-onenand"; 40 reg = <0 0 0>; /* CS0, offset 0 */ 41 gpmc,device-width = <2>; 42 43 #address-cells = <1>; 44 #size-cells = <1>; 45 46 /* partitions go here */ 47 }; 48 }; 49