From: Nishanth Menon <nm@ti.com>
To: Jassi Brar <jassisinghbrar@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Nishanth Menon <nm@ti.com>, Suman Anna <s-anna@ti.com>,
Tero Kristo <t-kristo@ti.com>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH V2 0/6] mailbox: ti-msgmgr: Add support for AM654 Secure Proxy
Date: Mon, 16 Jul 2018 13:06:01 -0500 [thread overview]
Message-ID: <20180716180607.16526-1-nm@ti.com> (raw)
The V2 of the series updates a minor comment in binding and picks up Rob's Reviewed-by
Since I have'nt seen additional comments, I am assuming things are fine for v4.19.
The following series enables support for Secure Proxy in newest addition in TI's SoC
portfolio - AM654 SoC (posted previously as RFC).
The series is based on v4.18-rc1 and is available here:
https://github.com/nmenon/linux-2.6-playground/commits/upstream/v4.18-rc1/k3-1-am6-sproxy
There are a couple of follow on patches to be posted as well (Kconfig changes
for K3_ARCH and actual dts node changes).
Changes since RFC are highlighted in each of the patches, but overall:
* The K3 dependency has been broken out into a seperate series independent of
this.
* Binding has been seperated out as it's own file (even though the driver is
reused).
Consolidated all patches (including all series) are available here:
https://github.com/nmenon/linux-2.6-playground/commits/upstream/v4.18-rc1/k3-am6-integ
Full Boot log on AM654 (integrated with all patch series) is available here:
https://pastebin.ubuntu.com/p/bBFmnzYtCd/
Nishanth Menon (6):
mailbox: ti-msgmgr: Get rid of unused structure members
mailbox: ti-msgmgr: Allocate Rx channel resources only on request
mailbox: ti-msgmgr: Change message count mask to be descriptor based
mailbox: ti-msgmgr: Move the memory region name to descriptor
dt-bindings: mailbox: Add support for secure proxy threads
mailbox: ti-msgmgr: Add support for Secure Proxy
.../bindings/mailbox/ti,secure-proxy.txt | 50 +++
drivers/mailbox/ti-msgmgr.c | 353 +++++++++++++++++----
2 files changed, 336 insertions(+), 67 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mailbox/ti,secure-proxy.txt
--
2.15.1
next reply other threads:[~2018-07-16 18:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 18:06 Nishanth Menon [this message]
2018-07-16 18:06 ` [PATCH V2 1/6] mailbox: ti-msgmgr: Get rid of unused structure members Nishanth Menon
2018-07-16 18:06 ` [PATCH V2 2/6] mailbox: ti-msgmgr: Allocate Rx channel resources only on request Nishanth Menon
2018-07-16 18:06 ` [PATCH V2 3/6] mailbox: ti-msgmgr: Change message count mask to be descriptor based Nishanth Menon
2018-07-16 18:06 ` [PATCH V2 4/6] mailbox: ti-msgmgr: Move the memory region name to descriptor Nishanth Menon
2018-07-16 18:06 ` [PATCH V2 5/6] dt-bindings: mailbox: Add support for secure proxy threads Nishanth Menon
2018-07-16 18:06 ` [PATCH V2 6/6] mailbox: ti-msgmgr: Add support for Secure Proxy Nishanth Menon
2018-07-23 13:29 ` [PATCH V2 0/6] mailbox: ti-msgmgr: Add support for AM654 " Nishanth Menon
2018-07-23 13:56 ` Jassi Brar
2018-07-23 14:14 ` Nishanth Menon
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=20180716180607.16526-1-nm@ti.com \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=t-kristo@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
all inboxes | Powered by JetHome®