On Fri, Dec 10, 2021 at 12:42 PM Rafał Miłecki <zajec5@xxxxxxxxx> wrote: > This binding change is meant to introduce a generic way of describing > pinctrl blocks details. Every pinmux block is expected to have: > 1. Named pins > 2. Named groups containing one or more pins > 3. Named functions referencing one or more groups > > It doesn't describe how hw should be programmed. That remains binding > and driver specific. So what this does is to take a large chunk of data that we known to be associated with the compatible string (names of pins, groups and functions, etc) and put it into the device tree instead of the alternative, which is what most drivers do, and that is to compile in the data into the operating system and just look it up by using a compatible string. The DT maintainers have already indicated that this is not desirable and I don't see it getting merged before it has a Reviewed-by tag from one of the DT binding maintainers. I think we need to know what the USP (unique selling point) is? Would it be something like not having to duplicate work across some boot loaders and operating systems? (Well they all need to parse this type of description but that can be put into a library.) Or something else? Yours, Linus Walleij
