From: David Lechner <dlechner@baylibre.com>
To: Dharma Balasubiramani <dharma.b@microchip.com>,
Kamel Bouhara <kamel.bouhara@bootlin.com>,
William Breathitt Gray <wbg@kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>
Cc: linux-arm-kernel@lists.infradead.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] TCB: Add DMA support to read the capture register AB
Date: Thu, 29 May 2025 10:26:44 -0500 [thread overview]
Message-ID: <b9b9aea9-e02d-4d5f-9f07-ef1c54e46b89@baylibre.com> (raw)
In-Reply-To: <20250528-mchp-tcb-dma-v1-0-083a41fb7b51@microchip.com>
Please include the counter: prefix in the subject of the cover letter
as well. It makes it easier to see at a glance what this series might
be about.
On 5/28/25 1:13 AM, Dharma Balasubiramani wrote:
> This patch series adds support to enable the DMA support for TCB.
>
> When DMA is used, the Register AB (TC_RAB) address must be configured as
> source address of the transfer. TC_RAB provides the next unread value from
> TC_RA and TC_RB. It may be read by the DMA after a request has been
> triggered upon loading TC_RA or TC_RB.
Can you please explain what problem this series is solving and why we
need this change?
next prev parent reply other threads:[~2025-05-29 15:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 6:13 Dharma Balasubiramani
2025-05-28 6:13 ` [PATCH 1/2] counter: microchip-tcb-capture: Retrieve and map parent base address Dharma Balasubiramani
2025-05-28 6:13 ` [PATCH 2/2] counter: microchip-tcb-capture: Add DMA support for TC_RAB register reads Dharma Balasubiramani
2025-05-29 9:21 ` kernel test robot
2025-05-29 15:33 ` David Lechner
2025-06-04 6:15 ` Dharma.B
2025-06-04 13:21 ` David Lechner
2025-05-29 15:26 ` David Lechner [this message]
2025-06-04 6:17 ` [PATCH 0/2] TCB: Add DMA support to read the capture register AB Dharma.B
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=b9b9aea9-e02d-4d5f-9f07-ef1c54e46b89@baylibre.com \
--to=dlechner@baylibre.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=dharma.b@microchip.com \
--cc=kamel.bouhara@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=wbg@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®