From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 4/7] dma: ti: add driver to K3 UDMA
Date: Fri, 1 Feb 2019 10:35:02 -0500 [thread overview]
Message-ID: <20190201153502.GE30838@bill-the-cat> (raw)
In-Reply-To: <20190129055729.25553-5-vigneshr@ti.com>
On Tue, Jan 29, 2019 at 11:27:26AM +0530, Vignesh R wrote:
> The UDMA-P is intended to perform similar (but significantly upgraded) functions
> as the packet-oriented DMA used on previous SoC devices. The UDMA-P module
> supports the transmission and reception of various packet types.
> The UDMA-P also supports acting as both a UTC and UDMA-C for its internal
> channels. Channels in the UDMA-P can be configured to be either Packet-Based or
> Third-Party channels on a channel by channel basis.
>
> The initial driver supports:
> - MEM_TO_MEM (TR mode)
> - DEV_TO_MEM (Packet mode)
> - MEM_TO_DEV (Packet mode)
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
> Signed-off-by: Vignesh R <vigneshr@ti.com>
[snip]
> +#ifdef DEBUG
> +#define k3_udma_dbg(arg...) pr_err(arg)
> +#define k3_udma_dev_dbg(dev, arg...) dev_err(dev, arg)
> +static void k3_udma_print_buf(ulong addr, const void *data, uint width,
> + uint count, uint linelen)
> +{
> + print_buffer(addr, data, width, count, linelen);
> +}
> +#else
> +#define k3_udma_dbg(arg...)
> +#define k3_udma_dev_dbg(arg...)
> +static void k3_udma_print_buf(ulong addr, const void *data, uint width,
> + uint count, uint linelen)
> +{}
> +#endif
Here too what I've just said in another part of the thread about pr_xxx
and I sent in reply to another thread about print_buffer directly or not
at all. 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/20190201/6b37ab51/attachment.sig>
next prev parent reply other threads:[~2019-02-01 15:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 5:57 [U-Boot] [PATCH v3 0/7] AM65x: Add DMA support Vignesh R
2019-01-29 5:57 ` [U-Boot] [PATCH v3 1/7] firmware: ti_sci: Add support for NAVSS resource management Vignesh R
2019-01-29 5:57 ` [U-Boot] [PATCH v3 2/7] soc: ti: k3: add navss ringacc driver Vignesh R
2019-02-01 15:32 ` Tom Rini
2019-01-29 5:57 ` [U-Boot] [PATCH v3 3/7] soc: ti: k3: add CPPI5 description and helpers Vignesh R
2019-02-01 15:32 ` Tom Rini
2019-01-29 5:57 ` [U-Boot] [PATCH v3 4/7] dma: ti: add driver to K3 UDMA Vignesh R
2019-02-01 15:35 ` Tom Rini [this message]
2019-01-29 5:57 ` [U-Boot] [PATCH v3 5/7] soc: keystone: Merge into TI specific directory Vignesh R
2019-02-01 15:35 ` Tom Rini
2019-01-29 5:57 ` [U-Boot] [PATCH v3 6/7] arm64: dts: ti: k3-am65: add mcu navss nodes Vignesh R
2019-02-01 15:35 ` Tom Rini
2019-01-29 5:57 ` [U-Boot] [PATCH v3 7/7] configs: am65x_evm_a53: Enable DMA related configs Vignesh R
2019-02-01 15:35 ` 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=20190201153502.GE30838@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