On 21/10/13 23:51, Guenter Roeck wrote: > In my opinion, not being able to describe behavior (or what people refer > to as "describe how the hardware is used") is a severe limitation of > devicetree usage in Linux. That is not a devicetree limitation per se, > though, it is simply a matter of choice (or, in some cases, the ability > of those arguing for new bindings to sell those bindings as "hardware > description"). I agree this is a real problem, and I think it hinders upstream submission, since platform data was permitted to describe behaviour as well as describe the hardware, and platform data is being replaced with DT which is only permitted to describe the hardware. How then should we specify the behaviour to the kernel? I've already mentioned specific examples of this on the "Clock DT bindings" thread, and would be very interested if anybody has thoughts about it: http://lkml.kernel.org/r/520E1DF5.4030409@xxxxxxxxxx Cheers James -- 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
