4 Feb
2020
4 Feb
'20
5:24 a.m.
On 2/4/2020 1:49 AM, Dmitry Osipenko wrote:
External email: Use caution opening links or attachments
30.01.2020 13:33, Sameer Pujar пишет: ...
+properties:
- compatible:
- oneOf:
- items:
const: nvidia,tegra210-i2s
- items:
- enum:
- nvidia,tegra194-i2s
- nvidia,tegra186-i2s
- enum:
- nvidia,tegra210-i2s
Couldn't this be something like this:
properties: compatible: - enum: - nvidia,tegra210-i2s - nvidia,tegra186-i2s - nvidia,tegra194-i2s
I used that way because, For Tegra210: compatible = "nvidia,tegra210-i2s"; For Tegra186: compatible = "nvidia,tegra186-i2s", "nvidia,tegra210-i2s"; (future proof) For Tegra194: compatible = "nvidia,tegra194-i2s", "nvidia,tegra210-i2s"; (future proof)
Currently driver uses "nvidia,tegra210-i2s" alone.
YAML binding check fails otherwise as it does not let me have future proof bindings.