From: Roger Quadros <rogerq@kernel.org>
To: Siddharth Vadapalli <s-vadapalli@ti.com>,
trini@konsulko.com, nm@ti.com, sjg@chromium.org, afd@ti.com,
vigneshr@ti.com
Cc: u-boot@lists.denx.de, dannenberg@ti.com, srk@ti.com
Subject: Re: [PATCH 03/10] soc: ti: k3-navss-ringacc: Initialize base address of ring cfg registers
Date: Tue, 16 Jan 2024 13:43:51 +0200 [thread overview]
Message-ID: <121dc2b7-0fc7-42ac-80cb-9c1af64a09eb@kernel.org> (raw)
In-Reply-To: <20240112064759.1801600-4-s-vadapalli@ti.com>
Hi,
On 12/01/2024 08:47, Siddharth Vadapalli wrote:
> From: Kishon Vijay Abraham I <kishon@ti.com>
>
> Initialize base address of ring config registers required to natively
> setup ring cfg registers in the absence of Device Manager (DM) services
> at R5 SPL stage.
>
> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
> ---
> drivers/soc/ti/k3-navss-ringacc.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/soc/ti/k3-navss-ringacc.c b/drivers/soc/ti/k3-navss-ringacc.c
> index 7a2fbb0db6..31e9b372ee 100644
> --- a/drivers/soc/ti/k3-navss-ringacc.c
> +++ b/drivers/soc/ti/k3-navss-ringacc.c
> @@ -1030,8 +1030,8 @@ static int k3_nav_ringacc_init(struct udevice *dev, struct k3_nav_ringacc *ringa
> struct k3_nav_ringacc *k3_ringacc_dmarings_init(struct udevice *dev,
> struct k3_ringacc_init_data *data)
> {
> + void __iomem *base_rt, *base_cfg;
> struct k3_nav_ringacc *ringacc;
> - void __iomem *base_rt;
> int i;
>
> ringacc = devm_kzalloc(dev, sizeof(*ringacc), GFP_KERNEL);
> @@ -1049,6 +1049,10 @@ struct k3_nav_ringacc *k3_ringacc_dmarings_init(struct udevice *dev,
> if (!base_rt)
> return ERR_PTR(-EINVAL);
>
> + base_cfg = dev_read_addr_name_ptr(dev, "cfg");
> + if (!base_cfg)
> + return ERR_PTR(-EINVAL);
> +
Should this be restricted only for R5 SPL case? else we conflict with
Device Manager services?
> ringacc->rings = devm_kzalloc(dev,
> sizeof(*ringacc->rings) *
> ringacc->num_rings * 2,
> @@ -1063,6 +1067,7 @@ struct k3_nav_ringacc *k3_ringacc_dmarings_init(struct udevice *dev,
> for (i = 0; i < ringacc->num_rings; i++) {
> struct k3_nav_ring *ring = &ringacc->rings[i];
>
> + ring->cfg = base_cfg + KNAV_RINGACC_CFG_REGS_STEP * i;
> ring->rt = base_rt + K3_DMARING_RING_RT_REGS_STEP * i;
> ring->parent = ringacc;
> ring->ring_id = i;
--
cheers,
-roger
next prev parent reply other threads:[~2024-01-16 11:44 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 6:47 [PATCH 00/10] Add support for Ethernet Boot on SK-AM62 Siddharth Vadapalli
2024-01-12 6:47 ` [PATCH 01/10] board: ti: am62x: Init DRAM size in R5/A53 SPL Siddharth Vadapalli
2024-01-12 12:26 ` Nishanth Menon
2024-01-12 12:31 ` Siddharth Vadapalli
2024-01-12 12:40 ` Nishanth Menon
2024-01-12 13:26 ` Tom Rini
2024-01-15 8:12 ` Siddharth Vadapalli
2024-01-20 16:41 ` Tom Rini
2024-01-22 4:41 ` Siddharth Vadapalli
2024-04-03 12:48 ` Chintan Vankar
2024-04-11 22:07 ` Tom Rini
2024-04-16 12:22 ` Chintan Vankar
2024-04-16 17:00 ` Tom Rini
2024-04-17 7:50 ` Chintan Vankar
2024-04-17 12:18 ` Sughosh Ganu
2024-04-17 16:04 ` Tom Rini
2024-04-18 10:38 ` Chintan Vankar
2024-04-18 12:00 ` Sughosh Ganu
2024-04-19 10:34 ` Chintan Vankar
2024-04-19 11:34 ` Sughosh Ganu
2024-04-19 11:52 ` Chintan Vankar
2024-04-19 12:00 ` Sughosh Ganu
2024-04-18 18:13 ` Tom Rini
2024-04-22 11:16 ` Chintan Vankar
2024-04-22 15:03 ` Tom Rini
2024-01-12 6:47 ` [PATCH 02/10] firmware: ti_sci: Add No-OP for "RX_FL_CFG" Siddharth Vadapalli
2024-01-12 6:47 ` [PATCH 03/10] soc: ti: k3-navss-ringacc: Initialize base address of ring cfg registers Siddharth Vadapalli
2024-01-16 11:43 ` Roger Quadros [this message]
2024-04-24 12:52 ` Chintan Vankar
2024-01-12 6:47 ` [PATCH 04/10] soc: ti: k3-navss-ringacc: Fix reset ring API Siddharth Vadapalli
2024-01-12 6:47 ` [PATCH 05/10] dma: ti: k3-udma: Add support for native configuration of chan/flow Siddharth Vadapalli
2024-01-12 6:47 ` [PATCH 06/10] arm: mach-k3: am62: Update SoC autogenerated data to enable Ethernet Boot Siddharth Vadapalli
2024-01-12 12:28 ` Nishanth Menon
2024-01-12 6:47 ` [PATCH 07/10] arm: mach-k3: am625_init: Probe AM65 CPSW NUSS Siddharth Vadapalli
2024-01-12 12:30 ` Nishanth Menon
2024-01-22 10:19 ` Chintan Vankar
2024-01-23 20:57 ` Nishanth Menon
2024-02-27 11:24 ` Chintan Vankar
2024-01-12 6:47 ` [PATCH 08/10] configs: am62: Add configs for enabling ETHBOOT in R5SPL Siddharth Vadapalli
2024-01-12 12:31 ` Nishanth Menon
2024-01-12 12:38 ` Siddharth Vadapalli
2024-01-12 6:47 ` [PATCH 09/10] configs: am62x_evm_a53_defconfig: Enable configs required for Ethboot Siddharth Vadapalli
2024-01-12 12:33 ` Nishanth Menon
2024-01-12 12:39 ` Siddharth Vadapalli
2024-01-12 6:47 ` [PATCH 10/10] arm: dts: k3-am625-r5-sk: Enable DM services for main_pktdma Siddharth Vadapalli
2024-01-12 12:32 ` [PATCH 00/10] Add support for Ethernet Boot on SK-AM62 Nishanth Menon
2024-01-12 12:36 ` Siddharth Vadapalli
2024-01-12 12:42 ` Nishanth Menon
2024-01-12 12:47 ` Siddharth Vadapalli
2024-01-12 13:01 ` Nishanth Menon
2024-01-15 8:16 ` Siddharth Vadapalli
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=121dc2b7-0fc7-42ac-80cb-9c1af64a09eb@kernel.org \
--to=rogerq@kernel.org \
--cc=afd@ti.com \
--cc=dannenberg@ti.com \
--cc=nm@ti.com \
--cc=s-vadapalli@ti.com \
--cc=sjg@chromium.org \
--cc=srk@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@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