devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Stephan Gerhold <stephan@gerhold.net>,
	Bhupesh Sharma <bhupesh.sharma@linaro.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
	Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org,
	devicetree@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH v3 0/2] dmaengine: qcom: bam_dma: Add "powered remotely" mode for BAM-DMUX
Date: Mon, 25 Oct 2021 11:18:08 +0530	[thread overview]
Message-ID: <YXZFGFH5lxDKeenw@matsya> (raw)
In-Reply-To: <20211018102421.19848-1-stephan@gerhold.net>

On 18-10-21, 12:24, Stephan Gerhold wrote:
> The BAM Data Multiplexer (BAM-DMUX) provides access to the network data
> channels of modems integrated into many older Qualcomm SoCs, e.g.
> Qualcomm MSM8916 or MSM8974.
> 
> Shortly said, BAM-DMUX is built using a simple protocol layer on top of
> a DMA engine (Qualcomm BAM DMA). For BAM-DMUX, the BAM DMA engine runs in
> a special mode where the modem/remote side is responsible for powering
> on the BAM when needed but we are responsible to initialize it.
> The BAM is powered off when unneeded by coordinating power control
> via bidirectional interrupts from the BAM-DMUX driver.
> 
> This series adds one possible solution for handling the "powered remotely"
> mode in the bam_dma driver.

This looks good me me. Bhupesh/Stephan what was the conclusion on the
the discussion you folks had?

> 
> For more information about BAM-DMUX itself, see the series on netdev:
> https://lore.kernel.org/netdev/20211011141733.3999-5-stephan@gerhold.net/
> 
> Changes in v3:
>   - Split dmaengine changes to a separate series
>   - Address review comments from Bjorn
> 
> v2: https://lore.kernel.org/netdev/20211011141733.3999-1-stephan@gerhold.net/
> RFC: https://lore.kernel.org/netdev/20210719145317.79692-1-stephan@gerhold.net/
> 
> 
> Stephan Gerhold (2):
>   dt-bindings: dmaengine: bam_dma: Add "powered remotely" mode
>   dmaengine: qcom: bam_dma: Add "powered remotely" mode
> 
>  .../devicetree/bindings/dma/qcom_bam_dma.txt  |  2 +
>  drivers/dma/qcom/bam_dma.c                    | 90 ++++++++++++-------
>  2 files changed, 59 insertions(+), 33 deletions(-)
> 
> -- 
> 2.33.0

-- 
~Vinod

  parent reply	other threads:[~2021-10-25  5:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 10:24 [PATCH v3 0/2] dmaengine: qcom: bam_dma: Add "powered remotely" mode for BAM-DMUX Stephan Gerhold
2021-10-18 10:24 ` [PATCH v3 1/2] dt-bindings: dmaengine: bam_dma: Add "powered remotely" mode Stephan Gerhold
2021-10-18 19:51   ` Rob Herring
2021-10-18 10:24 ` [PATCH v3 2/2] dmaengine: qcom: " Stephan Gerhold
2021-10-25  5:48 ` Vinod Koul [this message]
2021-10-25  6:17   ` [PATCH v3 0/2] dmaengine: qcom: bam_dma: Add "powered remotely" mode for BAM-DMUX Stephan Gerhold
2021-10-28  6:50     ` Bhupesh Sharma
2021-10-28  7:15       ` Stephan Gerhold
2021-10-28  7:18         ` Bhupesh Sharma
2021-10-28 17:12 ` Vinod Koul

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=YXZFGFH5lxDKeenw@matsya \
    --to=vkoul@kernel.org \
    --cc=agross@kernel.org \
    --cc=bhupesh.sharma@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=stephan@gerhold.net \
    --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;
as well as URLs for NNTP newsgroup(s).