[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bce8c598-9075-d643-59b5-c2397a55b52f@linaro.org>
Date: Wed, 6 Jul 2022 17:06:16 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Vidya Sagar <vidyas@...dia.com>, Rob Herring <robh@...nel.org>
Cc: bhelgaas@...gle.com, lorenzo.pieralisi@....com,
thierry.reding@...il.com, jonathanh@...dia.com, kishon@...com,
vkoul@...nel.org, kw@...ux.com, p.zabel@...gutronix.de,
mperttunen@...dia.com, linux-pci@...r.kernel.org,
devicetree@...r.kernel.org, linux-tegra@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-phy@...ts.infradead.org,
kthota@...dia.com, mmaddireddy@...dia.com, sagar.tv@...il.com,
Thierry Reding <treding@...dia.com>
Subject: Re: [PATCH V3 02/11] dt-bindings: pci: tegra: Convert to json-schema
On 06/07/2022 12:46, Vidya Sagar wrote:
>
>
> On 7/6/2022 3:36 PM, Krzysztof Kozlowski wrote:
>> External email: Use caution opening links or attachments
>>
>>
>> On 06/07/2022 11:53, Vidya Sagar wrote:
>>>>> + nvidia,bpmp:
>>>>> + $ref: /schemas/types.yaml#/definitions/phandle-array
>>>>> + description: |
>>>>> + Must contain a pair of phandle to BPMP controller node followed by controller ID. Following
>>>>> + are the controller IDs for each controller:
>>>>> +
>>>>> + 0: C0
>>>>> + 1: C1
>>>>> + 2: C2
>>>>> + 3: C3
>>>>> + 4: C4
>>>>> + 5: C5
>>>>> + items:
>>>>> + - items:
>>>>> + - minimum: 0
>>>>> + maximum: 0xffffffff
>>>>
>>>> That's already the limit. Just a description is fine.
>>>>
>>>>> + - enum: [ 0, 1, 2, 3, 4, 5 ]
>>>>
>>>> maximum: 5
>>>
>>> Setting the maximum to '5' is resulting in the following error.
>>>
>>> pcie-ep@...a0000: nvidia,bpmp:0:0: 4294967295 is greater than the
>>> maximum of 5
>>>
>>> Could you please help me understand why I'm seeing this error?
>>
>> Trim your replies.
>>
>> Why adding minimum:5 to the phandle? Rob said add a description. Nothing
>> about minimum.
>
> I'm sorry I didn't understand the review comment clearly.
> There is one description added above already. Are you (and Rob) saying
> that one more description is needed?
You have description of entire property. The property consists of
phandles ("items", with only one item) and each phandle of two items
(second nested "items"). The first item in phandle is actual phandle, so
it does not need any constraints/schema, just a description. This was
missing.
Something like this:
https://elixir.bootlin.com/linux/v5.18-rc1/source/Documentation/devicetree/bindings/soc/samsung/exynos-usi.yaml#L42
except that in your case second item (in the nested items) have actual
schema, not description, which is good.
Best regards,
Krzysztof
Powered by blists - more mailing lists