From: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
To: ssantosh@kernel.org, s-anna@ti.com
Cc: grzegorz.jaszczyk@linaro.org, santosh.shilimkar@oracle.com,
robh+dt@kernel.org, lee.jones@linaro.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
praneeth@ti.com, tony@atomide.com
Subject: [PATCH v2 0/7] Add TI PRUSS platform driver
Date: Fri, 21 Aug 2020 16:42:37 +0200 [thread overview]
Message-ID: <1598020964-29877-1-git-send-email-grzegorz.jaszczyk@linaro.org> (raw)
Hi All,
The following is a v2 version of the series [1] that adds the platform driver
for the Programmable Real-Time Unit and Industrial Communication Subsystem
(PRU-ICSS), which is present on various TI SoCs. Please see the v1
cover-letter [1] for details about the features of this subsystem.
Please see the individual patches for exact changes in each patch, following are
the main changes from v1:
- dt-bindings was updated regarding to Rob Herring comments;
- support for K3 J721E SoCs ICSSG was enabled in patch #7.
[1] https://patchwork.kernel.org/cover/11690777/
Best regards,
Grzegorz
Grzegorz Jaszczyk (1):
dt-bindings: soc: ti: Add TI PRUSS bindings
Suman Anna (6):
soc: ti: pruss: Add a platform driver for PRUSS in TI SoCs
soc: ti: pruss: Add support for PRU-ICSSs on AM437x SoCs
soc: ti: pruss: Add support for PRU-ICSS subsystems on AM57xx SoCs
soc: ti: pruss: Add support for PRU-ICSS subsystems on 66AK2G SoC
soc: ti: pruss: Enable support for ICSSG subsystems on K3 AM65x SoCs
soc: ti: pruss: Enable support for ICSSG subsystems on K3 J721E SoCs
.../devicetree/bindings/soc/ti/ti,pruss.yaml | 320 +++++++++++++++++++++
drivers/soc/ti/Kconfig | 11 +
drivers/soc/ti/Makefile | 1 +
drivers/soc/ti/pruss.c | 184 ++++++++++++
include/linux/pruss_driver.h | 48 ++++
5 files changed, 564 insertions(+)
create mode 100644 Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
create mode 100644 drivers/soc/ti/pruss.c
create mode 100644 include/linux/pruss_driver.h
--
2.7.4
next reply other threads:[~2020-08-21 14:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 14:42 Grzegorz Jaszczyk [this message]
2020-08-21 14:42 ` [PATCH v2 1/7] dt-bindings: soc: ti: Add TI PRUSS bindings Grzegorz Jaszczyk
2020-09-04 16:11 ` Suman Anna
2020-09-08 21:30 ` Rob Herring
2020-08-21 14:42 ` [PATCH v2 2/7] soc: ti: pruss: Add a platform driver for PRUSS in TI SoCs Grzegorz Jaszczyk
2020-08-21 14:42 ` [PATCH v2 3/7] soc: ti: pruss: Add support for PRU-ICSSs on AM437x SoCs Grzegorz Jaszczyk
2020-08-21 14:42 ` [PATCH v2 4/7] soc: ti: pruss: Add support for PRU-ICSS subsystems on AM57xx SoCs Grzegorz Jaszczyk
2020-08-21 14:42 ` [PATCH v2 5/7] soc: ti: pruss: Add support for PRU-ICSS subsystems on 66AK2G SoC Grzegorz Jaszczyk
2020-08-21 14:42 ` [PATCH v2 6/7] soc: ti: pruss: Enable support for ICSSG subsystems on K3 AM65x SoCs Grzegorz Jaszczyk
2020-08-21 14:42 ` [PATCH v2 7/7] soc: ti: pruss: Enable support for ICSSG subsystems on K3 J721E SoCs Grzegorz Jaszczyk
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=1598020964-29877-1-git-send-email-grzegorz.jaszczyk@linaro.org \
--to=grzegorz.jaszczyk@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=praneeth@ti.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=santosh.shilimkar@oracle.com \
--cc=ssantosh@kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).