From: Stephan Gerhold <stephan.gerhold@linaro.org>
To: Md Sadre Alam <quic_mdalam@quicinc.com>
Cc: vkoul@kernel.org, kees@kernel.org, fenghua.yu@intel.com,
linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, djakov@kernel.org,
quic_srichara@quicinc.com, quic_varada@quicinc.com
Subject: Re: [PATCH v3] dmaengine: qcom: bam_dma: Fix BAM_RIVISON register handling
Date: Tue, 21 Jan 2025 18:09:43 +0100 [thread overview]
Message-ID: <Z4_U19_QyH2RJvKW@linaro.org> (raw)
In-Reply-To: <20250121091241.2646532-1-quic_mdalam@quicinc.com>
On Tue, Jan 21, 2025 at 02:42:41PM +0530, Md Sadre Alam wrote:
> This patch resolves a bug from the previous commit where the
> BAM_DESC_CNT_TRSHLD register was conditionally written based on BAM-NDP
> mode. The issue was reading the BAM_REVISION register hanging if num-ees
> was not zero, which occurs when the SoCs power on BAM remotely. So the
> BAM_REVISION register read has been moved to inside if condition.
>
> Fixes: 57a7138d0627 ("dmaengine: qcom: bam_dma: Avoid writing unavailable register")
> Reported-by: Georgi Djakov <djakov@kernel.org>
> Link: https://lore.kernel.org/lkml/9ef3daa8-cdb1-49f2-8d19-a72d6210ff3a@kernel.org/
> Signed-off-by: Md Sadre Alam <quic_mdalam@quicinc.com>
I'm afraid there are still two open problems here:
1. In your original commit, you added the if (in_range(...)) checks to
make the BAM_DESC_CNT_TRSHLD register write conditional. With this
patch we only read the bam_revision for the !bdev->num_ees case.
This means that even if we have e.g. a remotely powered BAM-NDP,
we don't initialize BAM_DESC_CNT_TRSHLD anymore.
2. Aside from BAM-NDP and BAM-Lite there is also plain "BAM". You
mentioned we should only skip the register write for BAM-Lite, but
the plain "BAM" isn't handled anywhere yet.
I would recommend inverting the in_range(...) checks to check for if
(!in_range(BAM-LITE) rather than if (in_range(BAM-NDP)). This should
also work for the plain "BAM" type. It will also avoid regressions if we
don't read the bam_revision in the !bdev->num_ees case. (Although
ideally you would lazily initialize the bam_revision to cover all the
configurations.)
Thanks,
Stephan
> ---
>
> Change in [v3]
>
> * Revised commit details
>
> Change in [v2]
>
> * Removed unnecessary if checks.
> * Relocated the BAM_REVISION register read within the if condition.
>
> Change in [v1]
>
> * https://lore.kernel.org/lkml/1a5fc7e9-39fe-e527-efc3-1ea990bbb53b@quicinc.com/
> * Posted initial fixup for BAM revision register read handling
> drivers/dma/qcom/bam_dma.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/dma/qcom/bam_dma.c b/drivers/dma/qcom/bam_dma.c
> index c14557efd577..d227b4f5b6b9 100644
> --- a/drivers/dma/qcom/bam_dma.c
> +++ b/drivers/dma/qcom/bam_dma.c
> @@ -1199,11 +1199,11 @@ static int bam_init(struct bam_device *bdev)
> u32 val;
>
> /* read revision and configuration information */
> - val = readl_relaxed(bam_addr(bdev, 0, BAM_REVISION));
> - if (!bdev->num_ees)
> + if (!bdev->num_ees) {
> + val = readl_relaxed(bam_addr(bdev, 0, BAM_REVISION));
> bdev->num_ees = (val >> NUM_EES_SHIFT) & NUM_EES_MASK;
> -
> - bdev->bam_revision = val & REVISION_MASK;
> + bdev->bam_revision = val & REVISION_MASK;
> + }
>
> /* check that configured EE is within range */
> if (bdev->ee >= bdev->num_ees)
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-01-21 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 9:12 [PATCH v3] dmaengine: qcom: bam_dma: Fix BAM_RIVISON register handling Md Sadre Alam
2025-01-21 10:54 ` Dmitry Baryshkov
2025-01-23 12:08 ` Md Sadre Alam
2025-01-21 17:09 ` Stephan Gerhold [this message]
2025-01-23 12:11 ` Md Sadre Alam
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=Z4_U19_QyH2RJvKW@linaro.org \
--to=stephan.gerhold@linaro.org \
--cc=djakov@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=fenghua.yu@intel.com \
--cc=kees@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_mdalam@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@quicinc.com \
--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