From: "Kumar, Udit" <u-kumar1@ti.com>
To: Karl Mehltretter <kmehltretter@gmail.com>
Cc: Nishanth Menon <nm@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <u-kumar1@ti.com>
Subject: Re: [PATCH 2/2] soc: ti: k3-ringacc: Fix DMA ring initialization kernel-doc
Date: Wed, 23 Sep 2026 09:07:37 +0530 [thread overview]
Message-ID: <bd3b9ea9-2e3d-4d33-adbf-abfd25adde64@ti.com> (raw)
In-Reply-To: <arLTj9qVIE0Yz4vH@gmail.com>
Hi Kari,
On 9/23/2026 12:47 AM, Karl Mehltretter wrote:
> On Tue, Sep 22, 2026 at 09:34:49PM +0100, Kumar, Udit wrote:
>>> + * @num_rings: Number of forward/completion ring pairs
>>
>> Sorry from where you got above definition of num_rings
>
> Hi Udit,
>
> It was inferred from the code. Is the description
> inaccurate? What wording would you suggest?
>
This is just total number of available rings
you can refer
https://elixir.bootlin.com/linux/v7.2.6/source/drivers/dma/ti/k3-udma.c#L5492
https://elixir.bootlin.com/linux/v7.2.6/source/drivers/soc/ti/k3-ringacc.c#L1478
https://elixir.bootlin.com/linux/v7.2.6/source/drivers/soc/ti/k3-ringacc.c#L212
> Thanks,
> Karl
prev parent reply other threads:[~2026-09-23 3:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 16:37 [PATCH 1/2] soc: ti: k3-ringacc: Correct ring API kernel-doc Karl Mehltretter
2026-09-19 16:37 ` [PATCH 2/2] soc: ti: k3-ringacc: Fix DMA ring initialization kernel-doc Karl Mehltretter
2026-09-22 16:04 ` Kumar, Udit
2026-09-22 19:17 ` Karl Mehltretter
2026-09-23 3:37 ` Kumar, Udit [this message]
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=bd3b9ea9-2e3d-4d33-adbf-abfd25adde64@ti.com \
--to=u-kumar1@ti.com \
--cc=grygorii.strashko@ti.com \
--cc=kmehltretter@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=ssantosh@kernel.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
all inboxes | Powered by JetHome®