Hello Mark, On 10/23/2014 06:16 AM, Mark Rutland wrote: >>>> +NOTE: The bindings described in this document are preliminary and subject to >>>> + change >>> >>> While we've tried that elsewhere, unstable DT bindings have been shown >>> to be a major source of pain. >> >> Agreed >> >>> I'd feel rather uncomfortable accepting a >>> binding that we already believe to be insufficient to describe the >>> hardware. >>> >>> What do you expect to change? >> >> Related bindings seem incomplete. As such, the PAMU binding (pamu.txt) >> covers incompletely a dynamic LIODN assignment/programming model. The >> current driver uses a static assignment scheme that the binding needs to >> include. I also suspect that once the driver starts supporting the >> dynamic LIODN assignment/programming we might find some wrinkles > > Ok. Given that the driver doesn't seem to be in mainline (per a quick > grep), just put "DO NOT MERGE" or something like that in the commit > message. Once this is merged you're going to need to support it. We have a driver and once the bindings get accepted we'll (update the driver as needed and) post the code Cheers, -- 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
