[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <62ea74fe-1f3c-e56c-669f-9a2dd9c02412@nvidia.com>
Date: Tue, 4 Feb 2020 09:54:34 +0530
From: Sameer Pujar <spujar@...dia.com>
To: Dmitry Osipenko <digetx@...il.com>, <perex@...ex.cz>,
<tiwai@...e.com>, <robh+dt@...nel.org>
CC: <spujar@...dia.com>, <broonie@...nel.org>, <lgirdwood@...il.com>,
<thierry.reding@...il.com>, <jonathanh@...dia.com>,
<alsa-devel@...a-project.org>, <devicetree@...r.kernel.org>,
<linux-tegra@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<sharadg@...dia.com>, <mkumard@...dia.com>,
<viswanathl@...dia.com>, <rlokhande@...dia.com>,
<dramesh@...dia.com>, <atalambedu@...dia.com>
Subject: Re: [PATCH v2 1/9] dt-bindings: sound: tegra: add DT binding for AHUB
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.
Powered by blists - more mailing lists