> > However, with the yaml stuff, if that is basically becoming "DT > > specification" then it needs to be clearly defined what each value > > actually means for the system, and not this vague airy-fairy thing > > we have now. > I agree with Russell that it seems preferable to make it unambiguous whether > delays are added on the MAC or PHY side, in particular for fine-tuning. If > anything is left to the implementation, we should make the range of acceptable > driver behavior very clear in the documentation. I think we should try the "Informative" route first, see what the DT Maintainers think when we describe in detail how Linux interprets these values. I don't think a whole new set of properties will solve anything. I would say the core of the problem is that there are multiple ways of getting a working system, many of which don't fit the DT binding. But DT developers don't care about that, they are just happy when it works. Adding a different set of properties won't change that. Andrew
