From: Devarsh Thakkar <devarsht@ti.com>
To: <andersson@kernel.org>, <mathieu.poirier@linaro.org>,
<p.zabel@pengutronix.de>, <linux-remoteproc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<s-anna@ti.com>
Cc: <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<hnagalla@ti.com>, <praneeth@ti.com>, <nm@ti.com>,
<vigneshr@ti.com>, <a-bhatia1@ti.com>, <j-luthra@ti.com>
Subject: [PATCH v2 0/2] Add single core R5F IPC for AM62 SoC family
Date: Wed, 30 Nov 2022 19:10:50 +0530 [thread overview]
Message-ID: <20221130134052.7513-1-devarsht@ti.com> (raw)
AM62 SoC family don't have a R5F cluster, instead they have a single
core R5F. This enables IPC support with single core R5F for AM62
family of SoCs.
Devarsh Thakkar (2):
Documentation: dt-bindings: k3-r5f-rproc: Add new compatible for AM62
SoC family
remoteproc: k3-r5: Use separate compatible string for TI AM62 SoC
family
.../bindings/remoteproc/ti,k3-r5f-rproc.yaml | 48 +++++++++++-----
drivers/remoteproc/ti_k3_r5_remoteproc.c | 55 +++++++++++++++----
2 files changed, 77 insertions(+), 26 deletions(-)
--
2.17.1
next reply other threads:[~2022-11-30 13:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 13:40 Devarsh Thakkar [this message]
2022-11-30 13:40 ` [PATCH v2 1/2] Documentation: dt-bindings: k3-r5f-rproc: Add new compatible for AM62 SoC family Devarsh Thakkar
2022-11-30 15:03 ` Krzysztof Kozlowski
2022-12-21 7:42 ` Devarsh Thakkar
2022-12-21 9:36 ` Krzysztof Kozlowski
2022-12-21 16:29 ` Devarsh Thakkar
2022-12-21 17:17 ` Krzysztof Kozlowski
2022-11-30 13:40 ` [PATCH v2 2/2] remoteproc: k3-r5: Use separate compatible string for TI " Devarsh Thakkar
2022-11-30 17:57 ` Tanmay Shah
2022-12-14 11:00 ` Devarsh Thakkar
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=20221130134052.7513-1-devarsht@ti.com \
--to=devarsht@ti.com \
--cc=a-bhatia1@ti.com \
--cc=andersson@kernel.org \
--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=mathieu.poirier@linaro.org \
--cc=nm@ti.com \
--cc=p.zabel@pengutronix.de \
--cc=praneeth@ti.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.