From: Frank Li <Frank.li@oss.nxp.com>
To: Nickolay Goppen <setotau@mainlining.org>
Cc: Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
dmaengine@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Sireesh Kodali <sireeshkodali1@gmail.com>
Subject: Re: [PATCH 2/3] dmaengine: Add support for immediate commands in the client API
Date: Wed, 18 Nov 2026 14:03:22 -0600 [thread overview]
Message-ID: <av4Eis87C7QBxkd4@SMW015318> (raw)
In-Reply-To: <20261115-qcom-bam-dma-immediate-v1-2-9a0df4ca3be1@mainlining.org>
On Sun, Nov 15, 2026 at 05:02:44PM +0300, Nickolay Goppen wrote:
> [You don't often get email from setotau@mainlining.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> From: Sireesh Kodali <sireeshkodali1@gmail.com>
>
> Immediate commands are needed by the IPA network driver, so that it can
> send commands via BAM to the IPA microcontroller.
>
> Signed-off-by: Sireesh Kodali <sireeshkodali1@gmail.com>
> Signed-off-by: Nickolay Goppen <setotau@mainlining.org>
> ---
> include/linux/dmaengine.h | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/include/linux/dmaengine.h b/include/linux/dmaengine.h
> index 805668fbe437..56c49254ed04 100644
> --- a/include/linux/dmaengine.h
> +++ b/include/linux/dmaengine.h
> @@ -200,6 +200,9 @@ struct dma_vec {
> * transaction is marked with DMA_PREP_REPEAT will cause the new transaction
> * to never be processed and stay in the issued queue forever. The flag is
> * ignored if the previous transaction is not a repeated transaction.
> + * @DMA_PREP_IMM_CMD: tell the driver that the data passed to the DMA API is
> + * immediate command data and the descriptor should be in a different format
> + * from the normal data and descriptor
does dmaengine_desc_attach_metadata() work for your case?
Frank
> */
> enum dma_ctrl_flags {
> DMA_PREP_INTERRUPT = (1 << 0),
> @@ -212,6 +215,7 @@ enum dma_ctrl_flags {
> DMA_PREP_CMD = (1 << 7),
> DMA_PREP_REPEAT = (1 << 8),
> DMA_PREP_LOAD_EOT = (1 << 9),
> + DMA_PREP_IMM_CMD = (1 << 10),
> };
>
> /**
>
> --
> 2.56.1
next prev parent reply other threads:[~2026-11-18 20:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 14:02 [PATCH 0/3] dmaengine: Add support for immediate commands Nickolay Goppen
2026-11-15 14:02 ` [PATCH 1/3] doc: dmaengine: client-api: Add immediate commands in the DMA client API Nickolay Goppen
2026-11-15 14:02 ` [PATCH 2/3] dmaengine: Add support for immediate commands in the " Nickolay Goppen
2026-11-18 20:03 ` Frank Li [this message]
2026-11-18 20:20 ` Nickolay Goppen
2026-11-15 14:02 ` [PATCH 3/3] dmaengine: bam_dma: Add support for immediate commands Nickolay Goppen
-- strict thread matches above, loose matches on Subject: below --
2021-09-19 14:43 [RFC PATCH 0/3] DMAengine: Add support for Immediate commands Sireesh Kodali
2021-09-19 14:43 ` [PATCH 2/3] dmaengine: Add support for immediate commands in the client API Sireesh Kodali
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=av4Eis87C7QBxkd4@SMW015318 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@kernel.org \
--cc=corbet@lwn.net \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=setotau@mainlining.org \
--cc=sireeshkodali1@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=vkoul@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®