On 05/12/2023 19:47, Markus Mayer wrote: > It has become necessary to distinguish between the various DPFE API > versions by version number. Having just chip-specific compatible strings > and one generic version is no longer meeting our needs. > > Also, a new DPFE API version, v4, needs to be supported by the driver. > > As a result, an intermediate compatible string format is being Introducing new SoC does not justify this. It's not correlated, not related. Stop using some fake arguments to introduce something which we do not want: versions. > introduced: brcm,dpfe-cpu-v<N> where <N> represents the API version > number. This is more specific than the catch-all "brcm,dpfe-cpu" and > more generic than chip-specific compatible strings, such as > "brcm,bcm7271-dpfe-cpu". NAK Best regards, Krzysztof
