From: David Lechner <david@lechnology.com>
To: linux-arm-kernel@lists.infradead.org
Cc: David Lechner <david@lechnology.com>,
Rob Herring <robh+dt@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
Suman Anna <s-anna@ti.com>,
Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>,
Sekhar Nori <nsekhar@ti.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Add support for TI AM18XX/OMAP-L138 PRUSS
Date: Mon, 4 Jan 2021 12:30:19 -0600 [thread overview]
Message-ID: <20210104183021.330112-1-david@lechnology.com> (raw)
This is the first step for adding support for the PRUSS on TI AM18XX/OMAP-L138
SoCs. This series adds support in the top-level PRUSS driver. (Patches for the
interrupt controller and individual PRUs are independent of this change and
will be submitted separately.)
David Lechner (2):
dt-bindings: soc: ti: ti,pruss: add ti,am1806-pruss
soc: ti: pruss: add support for AM18XX/OMAP-L138 PRUSS
.../devicetree/bindings/soc/ti/ti,pruss.yaml | 2 +
drivers/soc/ti/Kconfig | 2 +-
drivers/soc/ti/pruss.c | 76 +++++++++++--------
3 files changed, 47 insertions(+), 33 deletions(-)
--
2.25.1
next reply other threads:[~2021-01-04 18:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 18:30 David Lechner [this message]
2021-01-04 18:30 ` [PATCH 1/2] dt-bindings: soc: ti: ti,pruss: add ti,am1806-pruss David Lechner
2021-01-11 22:39 ` Rob Herring
2021-01-15 16:45 ` Suman Anna
2021-01-16 20:18 ` David Lechner
2021-01-18 4:58 ` Sekhar Nori
2021-01-04 18:30 ` [PATCH 2/2] soc: ti: pruss: add support for AM18XX/OMAP-L138 PRUSS David Lechner
2021-01-16 0:52 ` Suman Anna
2021-01-16 20:15 ` David Lechner
2021-01-25 4:42 ` [PATCH 0/2] Add support for TI " santosh.shilimkar
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=20210104183021.330112-1-david@lechnology.com \
--to=david@lechnology.com \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=grzegorz.jaszczyk@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=ssantosh@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;
as well as URLs for NNTP newsgroup(s).