mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sireesh Kodali <sireeshkodali1@gmail.com>
To: phone-devel@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht, dmaengine@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Cc: Sireesh Kodali <sireeshkodali1@gmail.com>
Subject: [RFC PATCH 0/3] DMAengine: Add support for Immediate commands
Date: Sun, 19 Sep 2021 20:13:18 +0530	[thread overview]
Message-ID: <20210919144322.31977-1-sireeshkodali1@gmail.com> (raw)

The IPA v2.x block, found on some older Qualcomm SoCs, uses BAM DMA to
send and receive packets from the AP. It also uses BAM to receive
commands from the AP (and possibly the modem). These commands are
encoded as "Immediate Commands". They vary from regular BAM DMA
commands, although I'm not sure as to exactly how they vary. Adding
support for immediate commands is trivial, but requires also adding
Immediate Commands to the dmaengine API, which is what this patch does.

Sireesh Kodali (3):
  doc: dmaengine: client-api: Add immediate commands in the DMA client
    API
  dmaengine: Add support for immediate commands in the client API
  dmaengine: qcom: bam_dma: Add support for immediate commands

 Documentation/driver-api/dmaengine/provider.rst | 10 ++++++++++
 drivers/dma/qcom/bam_dma.c                      |  3 +++
 include/linux/dmaengine.h                       |  4 ++++
 3 files changed, 17 insertions(+)

-- 
2.33.0


             reply	other threads:[~2021-09-19 14:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-19 14:43 Sireesh Kodali [this message]
2021-09-19 14:43 ` [PATCH 1/3] doc: dmaengine: client-api: Add immediate commands in the DMA client API Sireesh Kodali
2021-09-19 14:43 ` [PATCH 2/3] dmaengine: Add support for immediate commands in the " Sireesh Kodali
2021-09-19 14:43 ` [PATCH 3/3] dmaengine: qcom: bam_dma: Add support for immediate commands 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=20210919144322.31977-1-sireeshkodali1@gmail.com \
    --to=sireeshkodali1@gmail.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phone-devel@vger.kernel.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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®