Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Md Sadre Alam <quic_mdalam@quicinc.com>
To: Stephan Gerhold <stephan.gerhold@linaro.org>
Cc: <vkoul@kernel.org>, <robin.murphy@arm.com>,
	<u.kleine-koenig@baylibre.com>, <martin.petersen@oracle.com>,
	<fenghua.yu@intel.com>, <av2082000@gmail.com>,
	<linux-arm-msm@vger.kernel.org>, <dmaengine@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <quic_mmanikan@quicinc.com>,
	<quic_srichara@quicinc.com>, <quic_varada@quicinc.com>
Subject: Re: [PATCH v4] dmaengine: qcom: bam_dma: Avoid writing unavailable register
Date: Fri, 10 Jan 2025 17:53:21 +0530	[thread overview]
Message-ID: <1964d238-d56a-b9ea-cda8-0b9ff32481cb@quicinc.com> (raw)
In-Reply-To: <Z4ENabbDjT8kfpQF@linaro.org>



On 1/10/2025 5:37 PM, Stephan Gerhold wrote:
> On Fri, Jan 10, 2025 at 05:29:29PM +0530, Md Sadre Alam wrote:
>> On 1/10/2025 3:59 PM, Stephan Gerhold wrote:
>>> On Fri, Dec 20, 2024 at 03:12:03PM +0530, Md Sadre Alam wrote:
>>>> Avoid writing unavailable register in BAM-Lite mode.
>>>> BAM_DESC_CNT_TRSHLD register is unavailable in BAM-Lite
>>>> mode. Its only available in BAM-NDP mode. So only write
>>>> this register for clients who is using BAM-NDP.
>>>>
>>>> Signed-off-by: Md Sadre Alam <quic_mdalam@quicinc.com>
>>>
>>> What are we actually fixing here? Which platform is affected? Is there a
>>> crash, reset, or incorrect behavior?
>> On SDX75, QPIC use BAM-Lite and as per HW description this
>> BAM_DESC_CNT_TRSHLD register is not available, and writing to this
>> SDX75 was hanging.
>>>
>>> We have had this code for years without reported issues, with both
>>> BAM-NDP and BAM-Lite instances. The register documentation on APQ8016E
>>> documents the BAM_DESC_CNT_TRSHLD register even for the BAM-Lite
>>> instance. There is a comment that it doesn't apply to BAM-Lite, but I
>>> would expect the written value just ends up being ignored in that case.
>> With older xPU it was being ignored but with new xPU its hanging. HW
>> team suggested don't write this register for BAM-Lite mode since its not
>> available.
>>>
> 
> OK, thanks for the explanation.
> 
>>> Also, there is not just BAM-NDP and BAM-Lite, but also plain "BAM". What
>>> about that one? Should we write to BAM_DESC_CNT_TRSHLD?
>> Apart from BAM-Lite this register available in all the BAM
> 
> Please check again if we need to check for additional revision numbers
> for the non-NDP BAM types then. Or alternatively, change the check to
> write the register on if (!BAM-Lite) instead of if (BAM-NDP). That might
> be easier.
Ok Thanks. will check once again this and post in next revision.
> 
> Thanks,
> Stephan

      reply	other threads:[~2025-01-10 12:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20  9:42 [PATCH v4] dmaengine: qcom: bam_dma: Avoid writing unavailable register Md Sadre Alam
2024-12-24 10:41 ` Vinod Koul
2025-01-07 21:30 ` Georgi Djakov
2025-01-08 11:10   ` Vinod Koul
2025-01-08 11:14     ` Md Sadre Alam
2025-01-10  5:23     ` Md Sadre Alam
2025-01-08 11:14   ` Md Sadre Alam
2025-01-10  5:21   ` Md Sadre Alam
2025-01-10 10:29 ` Stephan Gerhold
2025-01-10 11:59   ` Md Sadre Alam
2025-01-10 12:07     ` Stephan Gerhold
2025-01-10 12:23       ` Md Sadre Alam [this message]

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=1964d238-d56a-b9ea-cda8-0b9ff32481cb@quicinc.com \
    --to=quic_mdalam@quicinc.com \
    --cc=av2082000@gmail.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=fenghua.yu@intel.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=quic_mmanikan@quicinc.com \
    --cc=quic_srichara@quicinc.com \
    --cc=quic_varada@quicinc.com \
    --cc=robin.murphy@arm.com \
    --cc=stephan.gerhold@linaro.org \
    --cc=u.kleine-koenig@baylibre.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