On 14-03-22, 11:27, Arnd Bergmann wrote: > I don't think that it was meant to have a fixed order: unlike the other > bindings that define xxx-names properties, dmas require giving > names to allow the DT to specify more than one possible DMA > specifier for a given name. This means that nothing may ever just > rely on an index but has to use the name for lookup. Is there a way to update the yaml or tooling in that case so it doesn't expect a fixed order ? > OTOH, while fixing the order in the binding does not add any > value, it's also harmless as this should never be able to break > anything that worked for any combination of old/new dtb and > kernel, and it's probably easier to express in the binding. I agree, but such a patch shouldn't be required at all, which caught my attention. It is fine to merge it and won't break anything, but it shouldn't be required as well. -- viresh
