Searched full:onenand (Results 1 – 13 of 13) sorted by relevance
/freebsd/sys/contrib/device-tree/Bindings/mtd/ |
H A D | samsung,s5pv210-onenand.yaml | 4 $id: http://devicetree.org/schemas/mtd/samsung,s5pv210-onenand.yaml# 7 title: Samsung S5Pv210 SoC OneNAND Controller 15 - samsung,s5pv210-onenand 20 - description: OneNAND interface nCE[0] 21 - description: OneNAND interface nCE[1] 29 - const: onenand 51 compatible = "samsung,s5pv210-onenand"; 56 clock-names = "bus", "onenand";
|
H A D | ti,gpmc-onenand.yaml | 4 $id: http://devicetree.org/schemas/mtd/ti,gpmc-onenand.yaml# 7 title: OneNAND over Texas Instruments GPMC bus. 14 GPMC connected OneNAND (found on OMAP boards) are represented 19 pattern: "^onenand@[0-9],[0,9]$" 22 const: ti,omap2-onenand 28 OneNAND register window. 65 ranges = <0 0 0x01000000 0x01000000>, /* 16 MB for OneNAND */ 68 onenand@0,0 { 69 compatible = "ti,omap2-onenand";
|
H A D | gpmc-onenand.txt | 3 GPMC connected OneNAND (found on OMAP boards) are represented as child nodes of 4 the GPMC controller with a name of "onenand". 12 - compatible: "ti,omap2-onenand" 14 - gpmc,device-width: Width of the ONENAND device connected to the GPMC 38 onenand@0 { 39 compatible = "ti,omap2-onenand";
|
/freebsd/sys/contrib/device-tree/src/arm/ti/omap/ |
H A D | omap3430-sdp.dts | 52 <2 0 0x20000000 0x1000000>; /* CS2: 16MB for OneNAND */ 150 onenand@2,0 { 154 compatible = "ti,omap2-onenand"; 175 label = "xloader-onenand"; 179 label = "bootloader-onenand"; 183 label = "params-onenand"; 187 label = "kernel-onenand"; 191 label = "filesystem-onenand";
|
H A D | omap3-gta04a5one.dts | 9 model = "Goldelico GTA04A5/Letux 2804 with OneNAND"; 33 * according to TRM. OneNAND seems to require PIN_INPUT on clock. 42 /* switch inherited setup to OneNAND */ 44 ranges = <0 0 0x04000000 0x1000000>; /* CS0: 16MB for OneNAND */ 50 onenand@0,0 { 54 compatible = "ti,omap2-onenand";
|
H A D | omap2420-n8x0-common.dtsi | 48 ranges = <0 0 0x04000000 0x1000000>; /* CS0: 16MB for OneNAND */ 52 onenand@0,0 { 55 compatible = "ti,omap2-onenand"; 107 label = "omap2-onenand";
|
H A D | omap3-n950-n9.dtsi | 359 ranges = <0 0 0x04000000 0x1000000>; /* CS0: 16MB for OneNAND */ 361 onenand@0,0 { 364 compatible = "ti,omap2-onenand"; 370 * and N9 devices (OneNAND Manufacturer: Samsung): 440 label = "omap2-onenand";
|
H A D | omap3-igep.dtsi | 39 /* OneNAND seems to require PIN_INPUT on clock. */ 140 onenand@0,0 { 141 compatible = "ti,omap2-onenand";
|
H A D | omap3-n900.dts | 256 * according to TRM. OneNAND seems to require PIN_INPUT on clock. 848 ranges = <0 0 0x01000000 0x01000000>, /* 16 MB for OneNAND */ 854 onenand@0,0 { 857 compatible = "ti,omap2-onenand"; 863 * (OneNAND Manufacturer: Samsung):
|
/freebsd/sys/contrib/device-tree/src/arm/samsung/ |
H A D | s5pv210.dtsi | 75 onenand: nand-controller@b0600000 { label 76 compatible = "samsung,s5pv210-onenand"; 83 clock-names = "bus", "onenand";
|
H A D | s5pv210-aquila.dts | 356 &onenand {
|
H A D | s5pv210-goni.dts | 445 &onenand {
|
/freebsd/sys/contrib/device-tree/src/powerpc/fsl/ |
H A D | sbc8641d.dts | 32 7 0 0xe8000000 0x04000000>; // 64MB OneNAND
|