devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Anshul Dalal <anshuld@ti.com>, 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>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH v6] dt-bindings: arm: keystone: add boot_* mboxes to ti,sci
Date: Tue, 23 Dec 2025 14:40:31 +0100	[thread overview]
Message-ID: <e516b73b-2dc3-4ae4-966b-278a946491c8@kernel.org> (raw)
In-Reply-To: <DF5GPF5U7NPA.2ODE22YOF8E1R@ti.com>

On 23/12/2025 09:44, Anshul Dalal wrote:
> On Mon Dec 22, 2025 at 2:23 PM IST, Krzysztof Kozlowski wrote:
>> On 22/12/2025 09:43, Anshul Dalal wrote:
>>> The bootloader on K3 devices makes use of mailboxes as per the ROM spec
>>> which might be different than one's available to the kernel (firmware
>>> spec).
>>>
>>> Therefore, this patch adds the missing mailbox entries to the DT binding
>>> if the matching compatible is ti,am654-sci to represent the mailboxes
>>> exposed by the hardware during boot for the purpose of loading the
>>> firmware.
>>>
>>> The new ti,am642-sci compatible is also added to represent SoCs which do
>>> not expose a "notify" channel as part of their TI-SCI spec such as AM64x
>>> or the AM62 family. The newly added mboxes are made optional by keeping
>>> minItems as 2 to remain compliant with existing device-trees.
>>>
>>> Signed-off-by: Anshul Dalal <anshuld@ti.com>
>>> ---
>>> Changes in v6:
>>> - Added ti,am642-sci compatible to represent SoCs without a "notify" channel
>>> - Added new examples instead of editing existing ones
>>
>> Why? Rob asked not to.
> 
> I had followed what Nishanth had said[1], I'll wait for him and Rob to
> align first before posting the next revision.


Existing examples are fine. There is no rule saying you need to keep
updating examples or keep adding new device to examples. If someone told
you about such rule, tell them to stop inventing rules...

Best regards,
Krzysztof

  reply	other threads:[~2025-12-23 13:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-22  8:43 [PATCH v6] dt-bindings: arm: keystone: add boot_* mboxes to ti,sci Anshul Dalal
2025-12-22  8:53 ` Krzysztof Kozlowski
2025-12-23  8:44   ` Anshul Dalal
2025-12-23 13:40     ` Krzysztof Kozlowski [this message]
2025-12-29 17:46       ` Nishanth Menon
2026-01-05 11:26         ` Anshul Dalal
2026-01-05 14:54           ` Nishanth Menon

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=e516b73b-2dc3-4ae4-966b-278a946491c8@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).