u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot,v4,2/7] soc: ti: k3: add navss ringacc driver
Date: Fri, 12 Apr 2019 12:27:57 -0400	[thread overview]
Message-ID: <20190412162757.GW4664@bill-the-cat> (raw)
In-Reply-To: <20190205120127.13901-3-vigneshr@ti.com>

On Tue, Feb 05, 2019 at 05:31:22PM +0530, Vignesh R wrote:

> From: Grygorii Strashko <grygorii.strashko@ti.com>
> 
> The Ring Accelerator (RINGACC or RA) provides hardware acceleration to
> enable straightforward passing of work between a producer and a consumer.
> There is one RINGACC module per NAVSS on TI AM65x SoCs.
> 
> The RINGACC converts constant-address read and write accesses to equivalent
> read or write accesses to a circular data structure in memory. The RINGACC
> eliminates the need for each DMA controller which needs to access ring
> elements from having to know the current state of the ring (base address,
> current offset). The DMA controller performs a read or write access to a
> specific address range (which maps to the source interface on the RINGACC)
> and the RINGACC replaces the address for the transaction with a new address
> which corresponds to the head or tail element of the ring (head for reads,
> tail for writes). Since the RINGACC maintains the state, multiple DMA
> controllers or channels are allowed to coherently share the same rings as
> applicable. The RINGACC is able to place data which is destined towards
> software into cached memory directly.
> 
> Supported ring modes:
>  - Ring Mode
>  - Messaging Mode
>  - Credentials Mode
>  - Queue Manager Mode
> 
> TI-SCI integration:
> 
> Texas Instrument's System Control Interface (TI-SCI) Message Protocol now
> has control over Ringacc module resources management (RM) and Rings
> configuration.
> 
> The Ringacc driver manages Rings allocation by itself now and requests
> TI-SCI firmware to allocate and configure specific Rings only. It's done
> this way because, Linux driver implements two stage Rings allocation and
> configuration (allocate ring and configure ring) while TI-SCI Message
> Protocol supports only one combined operation (allocate+configure).
> 
> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
> Signed-off-by: Vignesh R <vigneshr@ti.com>

Applied to u-boot/master, thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190412/2fe23985/attachment.sig>

  reply	other threads:[~2019-04-12 16:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 12:01 [U-Boot] [PATCH v4 0/7] AM65x: Add DMA support Vignesh R
2019-02-05 12:01 ` [U-Boot] [PATCH v4 1/7] firmware: ti_sci: Add support for NAVSS resource management Vignesh R
2019-04-12 16:27   ` [U-Boot] [U-Boot, v4, " Tom Rini
2019-02-05 12:01 ` [U-Boot] [PATCH v4 2/7] soc: ti: k3: add navss ringacc driver Vignesh R
2019-04-12 16:27   ` Tom Rini [this message]
2019-02-05 12:01 ` [U-Boot] [PATCH v4 3/7] soc: ti: k3: add CPPI5 description and helpers Vignesh R
2019-04-12 16:28   ` [U-Boot] [U-Boot, v4, " Tom Rini
2019-02-05 12:01 ` [U-Boot] [PATCH v4 4/7] dma: ti: add driver to K3 UDMA Vignesh R
2019-02-06 23:43   ` Tom Rini
2019-04-12 16:28   ` [U-Boot] [U-Boot,v4,4/7] " Tom Rini
2019-02-05 12:01 ` [U-Boot] [PATCH v4 5/7] soc: keystone: Merge into ti specific directory Vignesh R
2019-04-12 16:28   ` [U-Boot] [U-Boot, v4, " Tom Rini
2019-02-05 12:01 ` [U-Boot] [PATCH v4 6/7] arm64: dts: ti: k3-am65: add mcu navss nodes Vignesh R
2019-04-12 16:28   ` [U-Boot] [U-Boot, v4, " Tom Rini
2019-02-05 12:01 ` [U-Boot] [PATCH v4 7/7] configs: am65x_evm_a53: Enable DMA related configs Vignesh R
2019-04-12 16:28   ` [U-Boot] [U-Boot, v4, " Tom Rini

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=20190412162757.GW4664@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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).