Dear Rob, and other DT maintainers, (apologies, fixed typos in earlier mail) >>From: Rob Herring >[...] >>> +- onfi,nand-timing-mode : mandatory if the chip does not support the ONFI >>> + standard. >> >>Add to generic nand binding. >> >>> +- allwinner,rb : shall contain the native Ready/Busy ids. >>> + or >>> +- rb-gpios : shall contain the gpios used as R/B pins. >> >>Isn't allwinner,rb implied by a lack of rb-gpios property. Or no R/B >>pin is an option? If so, don't you need some fixed time delay >>properties like max erase time? >> >>rb-gpios could be added to the generic nand binding as well. >> I do _not_ think this should go into generic nand binding, as this is controller specific. Some controllers have dedicated R/B pin (Ready/Busy) while others may use GPIO instead. It's the way a hardware controller is designed. Request you to please consider Ack from MTD Maintainers 'at-least' for generic NAND DT bindings. There is already a discussion going in a separate thread for which there are still no replies [1]. [1] http://lists.infradead.org/pipermail/linux-mtd/2014-January/051625.html with regards, pekon -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
