>From: Ezequiel Garcia [mailto:ezequ...@vanguardiasur.com.ar] >>On 24 Jun 05:54 PM, Pekon Gupta wrote: >> +&gpmc { >> + ranges = <0 0 0 0x01000000>; /* address range = 16MB (minimum GPMC >> partition) */ >> + nand@0,0 { >> + status = "disabled"; >> + reg = <0 0 4>; /* device IO registers */ >> + pinctrl-names = "default"; >> + pinctrl-0 = <&bbcape_nand_flash_pins>; >> + ti,nand-ecc-opt = "bch8"; >> + ti,elm-id = <&elm>; > >Don't you need something like this to turn on the elm device? > >&elm { > status = "okay"; >}; > No, This was the intend of these patches to keep cape DTS as "disabled" so that: (1)These patches should not change the behavior of existing DTS (am335x-boneblack.dts or am335x-bone.dts), or conflict with any existing node or other cape DTS. (2) In-case of share-pin mux where multiple capes use same pins Cape DTS should not conflict each other.
Now, to enable the choice of cape without hacking any source file, user can use u-boot commands (refer to example in cover-letter): /* load DTB */ u-boot> tftp 0x81000000 am335x-boneblack.dtb u-boot> fdt addr 0x81000000 /* disabled conflicting MMC2 (eMMC) */ u-boot> fdt set /ocp/mmc@481d8000 status \d\i\s\a\b\l\e\d /* enable NAND cape*/ u-boot> fdt set /ocp/elm status \o\k\a\y u-boot> fdt set /ocp/gpmc status \o\k\a\y u-boot> fdt set /ocp/gpmc/nand status \o\k\a\y And then boot using this DTB loaded at 0x81000000 (you can put all these commands in uEnv as part of $bootcmd) with regards, Pekon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
