From: Hari Nagalla <hnagalla@ti.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
Martyn Welch <martyn.welch@collabora.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
<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: Thu, 9 Mar 2023 17:18:01 -0600 [thread overview]
Message-ID: <8662e02b-9d28-8ffa-6ec2-5cc6348933fb@ti.com> (raw)
In-Reply-To: <20230308205833.GA1768401@p14s>
On 3/8/23 14:58, Mathieu Poirier wrote:
>> +required:
>> + - compatible
>> + - reg
>> + - reg-names
>> + - ti,sci
>> + - ti,sci-dev-id
>> + - ti,sci-proc-ids
>> + - resets
>> + - firmware-name
>> + - mboxes
> The 'mboxes' property is marked as required but the description section above
> clearly state the M4F can operate without IPC.
>
Well, when the M4F is used as a safety processor it is typically booted
from SBL/u-boot and may isolate the MCU domain from main domain/A53 to
function in higher safety level. In these scenarios there is no remote
proc handling of M4F life cycle management (LCM) and IPC. But, on the
other hand, when the M4F is used as a non safety processor its LCM is
handled by remote proc(main domain) and mailboxes for IPC are required.
next prev parent reply other threads:[~2023-03-09 23:18 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
2023-03-08 20:58 ` Mathieu Poirier
2023-03-09 23:18 ` Hari Nagalla [this message]
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=8662e02b-9d28-8ffa-6ec2-5cc6348933fb@ti.com \
--to=hnagalla@ti.com \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--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