From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 4/7] dma: ti: add driver to K3 UDMA
Date: Wed, 6 Feb 2019 18:43:10 -0500 [thread overview]
Message-ID: <20190206234310.GN30838@bill-the-cat> (raw)
In-Reply-To: <20190205120127.13901-5-vigneshr@ti.com>
On Tue, Feb 05, 2019 at 05:31:24PM +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>
Please note that some of these comments apply to patch #2 as well, but I
see a specific thing here
[snip]
> +++ b/drivers/dma/ti/k3-udma-hwdef.h
> @@ -0,0 +1,184 @@
> +/* SPDX-License-Identifier: GPL-2.0+ */
> +/*
> + * Copyright (C) 2018 Texas Instruments Incorporated - http://www.ti.com
> + *
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License version 2 as
> + * published by the Free Software Foundation.
You don't need/want both the SPDX tag and boilerplate.
[snip]
> +/* Generic register access functions */
> +static inline u32 udma_read(void __iomem *base, int reg)
> +{
> + u32 v;
> +
> + v = __raw_readl(base + reg);
> + pr_debug("READL(32): v(%08X)<--reg(%p)\n", v, base + reg);
> + return v;
> +}
> +
> +static inline void udma_write(void __iomem *base, int reg, u32 val)
> +{
> + pr_debug("WRITEL(32): v(%08X)-->reg(%p)\n", val, base + reg);
> + __raw_writel(val, base + reg);
> +}
I wasn't clear enough, sorry. We should be using __raw_readl/writel and
not wrapping them. If things are still in such a state that you need to
dump every read/write, are things really usable? I assume this is just
handy bring-up related work and it's time to drop it. 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/20190206/5332307d/attachment.sig>
next prev parent reply other threads:[~2019-02-06 23:43 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 ` [U-Boot] [U-Boot,v4,2/7] " Tom Rini
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 [this message]
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=20190206234310.GN30838@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