From: Suman Anna <s-anna@ti.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Lokesh Vutla <lokeshvutla@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
<linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Suman Anna <s-anna@ti.com>
Subject: [PATCH 0/2] Add AM64x SoC support to PRU remoteproc driver
Date: Wed, 23 Jun 2021 12:32:40 -0500 [thread overview]
Message-ID: <20210623173243.7862-1-s-anna@ti.com> (raw)
Hi All,
The following series updates the PRU remoteproc driver to support the
PRU, RTU and Tx_PRU cores present within the ICSSG IP on AM64x SoCs.
Patches are on top of latest rproc-next branch based on v5.13-rc1,
commit 30da589dba53 ("dt-bindings: remoteproc: qcom: pas: Fix indentation
warnings").
There are some minor differences around the PRU cores like different
Broadside RAM (BSRAM) sizes, but otherwise behave functionally the same
as the PRU cores on previous SoCs.
regards,
Suman
Suman Anna (2):
dt-bindings: remoteproc: pru: Update bindings for K3 AM64x SoCs
remoteproc: pru: Add support for various PRU cores on K3 AM64x SoCs
.../devicetree/bindings/remoteproc/ti,pru-rproc.yaml | 5 +++++
drivers/remoteproc/pru_rproc.c | 3 +++
2 files changed, 8 insertions(+)
--
2.30.1
next reply other threads:[~2021-06-23 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 17:32 Suman Anna [this message]
2021-06-23 17:32 ` [PATCH 1/2] dt-bindings: remoteproc: pru: Update bindings for K3 AM64x SoCs Suman Anna
2021-06-23 18:21 ` Grygorii Strashko
2021-06-23 17:32 ` [PATCH 2/2] remoteproc: pru: Add support for various PRU cores on " Suman Anna
2021-06-23 18:21 ` Grygorii Strashko
2021-06-24 19:41 ` 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=20210623173243.7862-1-s-anna@ti.com \
--to=s-anna@ti.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=grzegorz.jaszczyk@linaro.org \
--cc=jan.kiszka@siemens.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=mathieu.poirier@linaro.org \
--cc=robh+dt@kernel.org \
--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