Devicetree: allow one binding to match multiple compatibles

[mbolivar]

Is your enhancement proposal related to a problem? Please describe.

I would like to be able to write a single devicetree bindings file that allows multiple compatibles to match it.

This will allow me to write a single binding for a single compatible family of devices made by multiple vendors. My particular use case is WS2812 and SK6812 LED controllers, so I want to be able to write:

compatible: ["worldsemi,ws2812-spi", "szledcolor,sk6812-spi"]

Describe the solution you'd like

The above should match devicetree nodes with either of the compatibles in the list.

Describe alternatives you've considered

I could write multiple bindings files that each have their own compatible and include a common one. This feels inelegant and repetitive, however.

Additional context

N/A

[mbolivar]

from @galak on slack, for the record:

we need to spec if the list is tried as 'x' OR 'y' OR 'z' ... vs 'x' AND 'y' AND 'z' ...

[ulfalizer]

I had a PR that added this earlier, but it was rejected then. Can't remember which PR it was part of ATM though.

[ulfalizer]

from @galak on slack, for the record:

we need to spec if the list is tried as 'x' OR 'y' OR 'z' ... vs 'x' AND 'y' AND 'z' ...

Should be an OR thing I think. If you want to put other restrictions on compatible, properties: might be a better place to do it, since that's where restrictions on properties are normally added.

[mbolivar]

Should be an OR thing I think.

I think I agree about this. The variant-compatible scheme seems to be along those lines also.

[pabigot]

Cross-link with #20289 and #19904.

[ulfalizer]

I still need to find that old PR too. Had it all implemented, basically.

[zephyrbot]

Hi @galak,

This issue, marked as an Enhancement, was opened a while ago and did not get any traction. Please confirm the issue is correctly assigned and re-assign it otherwise.

Please take a moment to review if the issue is still relevant to the project. If it is, please provide feedback and direction on how to move forward. If it is not, has already been addressed, is a duplicate, or is no longer relevant, please close it with a short comment explaining the reason.

@mbolivar you are also encouraged to help moving this issue forward by providing additional information and confirming this request/issue is still relevant to you.

Thanks!