From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Devarsh Thakkar <devarsht@ti.com>
Cc: andersson@kernel.org, devicetree@vger.kernel.org,
p.zabel@pengutronix.de, linux-remoteproc@vger.kernel.org,
robh+dt@kernel.org, linux-kernel@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org, s-anna@ti.com,
hnagalla@ti.com, praneeth@ti.com, nm@ti.com, vigneshr@ti.com,
a-bhatia1@ti.com, j-luthra@ti.com, rogerq@kernel.org
Subject: Re: [PATCH v8 0/3] Add single core R5F IPC for AM62 SoC family
Date: Wed, 29 Mar 2023 17:21:36 -0600 [thread overview]
Message-ID: <20230329232136.GA3393405@p14s> (raw)
In-Reply-To: <20230327152832.923480-1-devarsht@ti.com>
On Mon, Mar 27, 2023 at 08:58:29PM +0530, Devarsh Thakkar wrote:
> AM62 SoC family don't have a multicore R5F cluster,
> instead they have a single core R5F.
> This enables IPC support with single core R5F for AM62
> family of SoCs.
>
> While at it, also simplify the cluster mode setting usage
> by using soc_data specific checks only at probe.
>
> Devarsh Thakkar (3):
> remoteproc: k3-r5: Simplify cluster mode setting usage
> dt-bindings: remoteproc: ti: Add new compatible for AM62 SoC family
> remoteproc: k3-r5: Use separate compatible string for TI AM62x SoC
> family
>
> .../bindings/remoteproc/ti,k3-r5f-rproc.yaml | 76 ++++++++---
> drivers/remoteproc/ti_k3_r5_remoteproc.c | 127 ++++++++++++------
> 2 files changed, 138 insertions(+), 65 deletions(-)
I have applied this set.
Thanks,
Mathieu
> ---
> V2:
> - dt-bindings: Avoid acronyms, use "Device Manager" instead of "DM"
> V3:
> - dt-bindings: Use separate if block for each compatible for
> ti,cluster-mode property
> - dt-bindings: Rearrange compatibles as per alphabatical order
> V4:
> - dt-bindings: Place each enum in separate line in allOf
> V5:
> - No change (fixing typo in email address)
> V6:
> - dt-bindings: Remove reviewed-by due to new modifications to use
> cluster-mode=3
> Introduce Simplify cluster-mode setting preamble patch per review
> comments
> - Use CLUSTER_MODE_SINGLECORE for AM62x
> - Set PROC_BOOT_CFG_FLAG_R5_SINGLE_CORE for single core.
> V7:
> - Override to appropriate cluster-mode per firmware status flag
> without checking soc_data
> - Set appropriate mode as default if not provided in DT
> - Check mode validity against SoC data during probe
> - Rebase on top of 6.3 linux-next
> V8:
> - Avoid using soc_data while overriding cluster mode for IPC-only mode
> --
> 2.34.1
>
prev parent reply other threads:[~2023-03-29 23:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 15:28 [PATCH v8 0/3] Add single core R5F IPC for AM62 SoC family Devarsh Thakkar
2023-03-27 15:28 ` [PATCH v8 1/3] remoteproc: k3-r5: Simplify cluster mode setting usage Devarsh Thakkar
2023-03-27 15:28 ` [PATCH v8 2/3] dt-bindings: remoteproc: ti: Add new compatible for AM62 SoC family Devarsh Thakkar
2023-03-27 15:28 ` [PATCH v8 3/3] remoteproc: k3-r5: Use separate compatible string for TI AM62x " Devarsh Thakkar
2023-03-29 23:21 ` Mathieu Poirier [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=20230329232136.GA3393405@p14s \
--to=mathieu.poirier@linaro.org \
--cc=a-bhatia1@ti.com \
--cc=andersson@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--cc=j-luthra@ti.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=nm@ti.com \
--cc=p.zabel@pengutronix.de \
--cc=praneeth@ti.com \
--cc=robh+dt@kernel.org \
--cc=rogerq@kernel.org \
--cc=s-anna@ti.com \
--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