From: Krzysztof Kozlowski <krzk@kernel.org>
To: Anshul Dalal <anshuld@ti.com>
Cc: Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Andrew Davis <afd@ti.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH v4] dt-bindings: arm: keystone: add boot_* mboxes to ti,sci
Date: Mon, 8 Dec 2025 09:06:28 +0100 [thread overview]
Message-ID: <96f61d12-2472-4179-a9ec-0dd7b1fdca8a@kernel.org> (raw)
In-Reply-To: <DESMHL7FCYXE.3TE3SG6TDVJ39@ti.com>
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
prev parent reply other threads:[~2025-12-08 8:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 6:15 [PATCH v4] dt-bindings: arm: keystone: add boot_* mboxes to ti,sci Anshul Dalal
2025-12-05 13:01 ` Nishanth Menon
2025-12-05 14:58 ` Andrew Davis
2025-12-08 6:20 ` Krzysztof Kozlowski
2025-12-08 6:31 ` Anshul Dalal
2025-12-08 8:06 ` Krzysztof Kozlowski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=96f61d12-2472-4179-a9ec-0dd7b1fdca8a@kernel.org \
--to=krzk@kernel.org \
--cc=afd@ti.com \
--cc=anshuld@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=ssantosh@kernel.org \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).