[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMRc=Mc641VWZp_2cMxrvs2ErwwkE04903GZ8BzDAZg3+H19NQ@mail.gmail.com>
Date: Fri, 7 Mar 2025 14:37:37 +0100
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Md Sadre Alam <quic_mdalam@...cinc.com>
Cc: vkoul@...nel.org, corbet@....net, thara.gopinath@...il.com,
herbert@...dor.apana.org.au, davem@...emloft.net, martin.petersen@...cle.com,
enghua.yu@...el.com, u.kleine-koenig@...libre.com, dmaengine@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-crypto@...r.kernel.org, linux-arm-msm@...r.kernel.org,
quic_utiwari@...cinc.com, quic_srichara@...cinc.com, quic_varada@...cinc.com
Subject: Re: [PATCH v6 03/12] dmaengine: qcom: bam_dma: add bam_pipe_lock flag support
On Wed, Jan 15, 2025 at 11:33 AM Md Sadre Alam <quic_mdalam@...cinc.com> wrote:
>
> BAM IP version 1.4.0 and above only supports this LOCK/UNLOCK
> feature. So adding check for the same and setting bam_pipe_lock
> based on BAM SW Version.
>
Why do we need to read it at run-time if we already know the version
of the IP from the compatible?
Bartosz
Powered by blists - more mailing lists