On Fri, Oct 23, 2026 at 08:39:27AM +0200, Tomeu Vizoso wrote:
Allow specifying a second sub-mailbox that could be used by the firmware in addition to the first one, which is taken by remoteproc.
This is required by firmware that doesn't use rpmsg for their communication with the Linux kernel.
Assisted-by: LLM
Drop
Signed-off-by: Tomeu Vizoso tomeu@tomeuvizoso.net
DCO mismatch.
v3:
- Initial version
.../devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/Documentation/devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml b/Documentation/devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml index 278b88b7f906..d6319c8e96f8 100644 --- a/Documentation/devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml +++ b/Documentation/devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml @@ -51,10 +51,12 @@ properties: mboxes: description: |
OMAP Mailbox specifier denoting the sub-mailbox, to be used forcommunication with the remote processor. This property should matchwith the sub-mailbox node used in the firmware image.- maxItems: 1
OMAP Mailbox specifiers denoting the sub-mailboxes allotted tocommunication with the remote processor. The first is the one theremoteproc core uses and should match the sub-mailbox node used in thefirmware image. The second is optional.
Instead list the items with description and minItems: 1. Don't repeat constraints in free form text.
- minItems: 1
Best regards, Krzysztof