From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 5/8] dt-bindings: mailbox: ti,message-manager: Add support for secure proxy threads
Date: Tue, 12 Jun 2018 15:11:28 -0600 [thread overview]
Message-ID: <20180612211128.GA22038@rob-hp-laptop> (raw)
In-Reply-To: <20180605061629.4759-6-nm@ti.com>
On Tue, Jun 05, 2018 at 01:16:26AM -0500, Nishanth Menon wrote:
> Secure Proxy is another communication scheme in Texas Instrument's
> devices intended to provide an unique communication path from various
> processors in the System on Chip(SoC) to a central System Controller.
>
> Secure proxy is, in effect, an evolution of current generation Message
> Manager hardware block found in K2G devices. However the following
> changes have taken place:
>
> Secure Proxy instance exposes "threads" or "proxies" which is
> primary representation of "a" communication channel. Each thread is
> preconfigured by System controller configuration based on SoC usage
> requirements. Secure proxy by itself represents a single "queue" of
> communication but allows the proxies to be independently operated.
>
> Each Secure proxy thread can uniquely have their own error and threshold
> interrupts allowing for more fine control of IRQ handling.
>
> Provide an hardware description of the same for device tree
> representation.
>
> See AM65x Technical Reference Manual (SPRUID7, April 2018)
> for further details: http://www.ti.com/lit/pdf/spruid7
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
> .../bindings/mailbox/ti,message-manager.txt | 58 +++++++++++++++++++---
> 1 file changed, 50 insertions(+), 8 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/mailbox/ti,message-manager.txt b/Documentation/devicetree/bindings/mailbox/ti,message-manager.txt
> index ebf0e3710cee..de796e90cac6 100644
> --- a/Documentation/devicetree/bindings/mailbox/ti,message-manager.txt
> +++ b/Documentation/devicetree/bindings/mailbox/ti,message-manager.txt
> @@ -7,22 +7,40 @@ manager is broken up into queues in different address regions that are called
> "proxies" - each instance is unidirectional and is instantiated at SoC
> integration level to indicate receive or transmit path.
>
> +This can also be used to describe Texas Instrument's Secure Proxy
> +controller that allows for individually configurable "threads" or
> +"proxies" which allow for independent communication scheme.
There seems to be very little re-use here. I think I would make this
its own doc.
Rob
next prev parent reply other threads:[~2018-06-12 21:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 6:16 [RFC PATCH 0/8] mailbox: ti-msgmgr: Add support for AM654 Secure Proxy Nishanth Menon
2018-06-05 6:16 ` [RFC PATCH 1/8] mailbox: ti-msgmgr: Get rid of unused structure members Nishanth Menon
2018-06-05 6:16 ` [RFC PATCH 2/8] mailbox: ti-msgmgr: Allocate Rx channel resources only on request Nishanth Menon
2018-06-05 6:16 ` [RFC PATCH 3/8] mailbox: ti-msgmgr: Change message count mask to be descriptor based Nishanth Menon
2018-06-05 6:16 ` [RFC PATCH 4/8] mailbox: ti-msgmgr: Move the memory region name to descriptor Nishanth Menon
2018-06-05 6:16 ` [RFC PATCH 5/8] dt-bindings: mailbox: ti, message-manager: Add support for secure proxy threads Nishanth Menon
2018-06-12 21:11 ` Rob Herring [this message]
2018-06-12 22:04 ` [RFC PATCH 5/8] dt-bindings: mailbox: ti,message-manager: " Nishanth Menon
2018-06-05 6:16 ` [RFC PATCH 6/8] mailbox: ti-msgmgr: Add support for Secure Proxy Nishanth Menon
2018-06-05 6:16 ` [RFC PATCH 7/8] drivers: mailbox: Make ti-msgmr driver depend on ARCH_K3 Nishanth Menon
2018-06-05 6:16 ` [RFC PATCH 8/8] arm64: dts: ti: k3-am6: Add Secure Proxy instance 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=20180612211128.GA22038@rob-hp-laptop \
--to=robh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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