From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Martyn Welch <martyn.welch@collabora.com>,
Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Hari Nagalla <hnagalla@ti.com>
Cc: kernel@collabora.com, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: remoteproc: k3-m4f: Add bindings for K3 AM64x SoCs
Date: Wed, 8 Mar 2023 09:41:23 +0100 [thread overview]
Message-ID: <15374680-b9bc-a7a2-2723-570294456d24@linaro.org> (raw)
In-Reply-To: <c2bebcbf9d463d656ae69d489e0e5a88f2540c2e.camel@collabora.com>
On 07/03/2023 19:26, Martyn Welch wrote:
> On Fri, 2023-03-03 at 09:06 +0100, Krzysztof Kozlowski wrote:
>> On 02/03/2023 18:14, Martyn Welch wrote:
>>
>>> +
>>> + mboxes:
>>> + description: |
>>> + OMAP Mailbox specifier denoting the sub-mailbox, to be used
>>> for
>>
>> OMAP?
>>
>
> This device uses a mailbox compatible with the OMAP Mailbox, as defined
> in Documentation/devicetree/bindings/mailbox/ti,omap-mailbox.yaml.
>
> I note that documents title reads "TI OMAP2+ and K3 Mailbox devices".
> I'll drop the "OMAP" here.
>
>>> + communication with the remote processor. This property
>>> should match
>>> + with the sub-mailbox node used in the firmware image.
>>> + maxItems: 1
>>> +
>>> + memory-region:
>>> + description: |
>>> + phandle to the reserved memory nodes to be associated with
>>> the
>>> + remoteproc device. There should be at least two reserved
>>> memory nodes
>>> + defined.
>>
>> Don't repeat constraints in free form text.
>>
>>> The reserved memory nodes should be carveout nodes, and
>>> + should be defined with a "no-map" property as per the
>>> bindings in
>>> + Documentation/devicetree/bindings/reserved-memory/reserved-
>>> memory.yaml
>>> + minItems: 2
>>> + maxItems: 8
>>> + items:
>>> + - description: region used for dynamic DMA allocations like
>>> vrings and
>>> + vring buffers
>>> + - description: region reserved for firmware image sections
>>> + additionalItems: true
>>
>> And what is the purpose of the rest of reserved nodes?
>>
>
> Up to 8 regions can be specified with their purpose determined by the
> firmware running on the M4F core. The suggestion (and the
> implementation in the example firmware) is to use the first 2 regions
> as defined above for remoteproc with the others available to be used
> for other purposes if necessary. The address translation module used
> can cope with up to 8 regions.
Then mention the rest is just dedicated to the firmware and it's purpose
depends on the firmware.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-03-08 8:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 17:14 [PATCH v3 0/3] TI K3 M4F support on AM64x and AM62x SoCs Martyn Welch
2023-03-02 17:14 ` [PATCH v3 1/3] dt-bindings: remoteproc: k3-m4f: Add bindings for K3 AM64x SoCs Martyn Welch
2023-03-03 8:06 ` Krzysztof Kozlowski
2023-03-07 18:26 ` Martyn Welch
2023-03-08 8:41 ` Krzysztof Kozlowski [this message]
2023-03-08 20:58 ` Mathieu Poirier
2023-03-09 23:18 ` Hari Nagalla
2023-03-10 15:41 ` Mathieu Poirier
2023-03-24 10:31 ` Martyn Welch
2023-03-24 12:01 ` Martyn Welch
2023-03-02 17:14 ` [PATCH v3 2/3] remoteproc: k4: Split out functions common with M4 driver Martyn Welch
2023-03-08 21:45 ` Mathieu Poirier
2023-03-09 18:04 ` Hari Nagalla
2023-03-10 9:46 ` Martyn Welch
2023-03-10 9:53 ` AngeloGioacchino Del Regno
2023-03-10 13:55 ` Martyn Welch
2023-03-02 17:14 ` [PATCH v3 3/3] remoteproc: k4-m4: Add a remoteproc driver for M4F subsystem Martyn Welch
2023-03-09 23:01 ` Mathieu Poirier
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=15374680-b9bc-a7a2-2723-570294456d24@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=martyn.welch@collabora.com \
--cc=mathieu.poirier@linaro.org \
--cc=robh+dt@kernel.org \
/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).