dmaengine.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephan Gerhold <stephan@gerhold.net>
To: Bhupesh Sharma <bhupesh.sharma@linaro.org>
Cc: Vinod Koul <vkoul@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Andy Gross <agross@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: qcom: bam_dma: make channels/EEs optional in DT with clock
Date: Thu, 18 May 2023 13:21:38 +0200	[thread overview]
Message-ID: <ZGYKQkgRrBqO2rsx@gerhold.net> (raw)
In-Reply-To: <CAH=2Ntya7bqHVri_F8BOUJ6kJxtG2_usV08do+=OgkaoVJvxBQ@mail.gmail.com>

On Thu, May 18, 2023 at 04:43:57PM +0530, Bhupesh Sharma wrote:
> On Thu, 18 May 2023 at 14:56, Stephan Gerhold <stephan@gerhold.net> wrote:
> >
> > If we have a BAM clock in the DT we are able to turn on the BAM
> > controller while probing, so there is no need to read "num-channels"
> > and "qcom,num-ees" from the DT. It can be read more accurately directly
> > from the identification registers of the BAM.
> >
> > This simplifies setting up typical controlled-remotely BAM DMAs in the
> > DT that can be turned on via a clock (e.g. the BLSP DMA).
> 
> Can you please list which qcom board(s) you tested this patch on?
> 

It works fine at least on MSM8916/DB410c (for blsp_dma) and MDM9607
(blsp_dma and qpic_dma (for NAND)). More testing would be much
appreciated of course!

Personally I don't see much of a risk: If enabling the clock doesn't
actually enable the BAM controller, then the clock probably does not
belong to the BAM in the first place... :)

Thanks,
Stephan

  reply	other threads:[~2023-05-18 11:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18  9:26 [PATCH] dmaengine: qcom: bam_dma: make channels/EEs optional in DT with clock Stephan Gerhold
2023-05-18 11:13 ` Bhupesh Sharma
2023-05-18 11:21   ` Stephan Gerhold [this message]
2023-05-19  9:10     ` Bhupesh Sharma
2023-05-19 10:15       ` Stephan Gerhold

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=ZGYKQkgRrBqO2rsx@gerhold.net \
    --to=stephan@gerhold.net \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bhupesh.sharma@linaro.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).