[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <96f61d12-2472-4179-a9ec-0dd7b1fdca8a@kernel.org>
Date: Mon, 8 Dec 2025 09:06:28 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Anshul Dalal <anshuld@...com>
Cc: Nishanth Menon <nm@...com>, Tero Kristo <kristo@...nel.org>,
Santosh Shilimkar <ssantosh@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Andrew Davis <afd@...com>,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, Vignesh Raghavendra <vigneshr@...com>
Subject: Re: [PATCH v4] dt-bindings: arm: keystone: add boot_* mboxes to
ti,sci
On 08/12/2025 07:31, Anshul Dalal wrote:
>>>
>>> mboxes:
>>> minItems: 2
>>> + maxItems: 6
>>>
>>> ti,host-id:
>>> $ref: /schemas/types.yaml#/definitions/uint32
>>> @@ -79,6 +79,42 @@ properties:
>>> type: object
>>> $ref: /schemas/reset/ti,sci-reset.yaml#
>>>
>>> +if:
>>> + properties:
>>> + compatible:
>>> + contains:
>>> + const: ti,am654-sci
>>> +then:
>>> + properties:
>>> + mbox-names:
>>> + minItems: 2
>>
>> Why is this list flexible?
>>
>
> The idea is to make the boot_* mboxes optional so the existing DTs that
Then explain it in the commit msg.
> only have rx and tx remain complaint. Also, the boot_notify mbox is not
> supported by every SoC.
Not really relevant. This is one specific SoC. Not "every"...
Best regards,
Krzysztof
Powered by blists - more mailing lists