From: Georgi Djakov <djakov@kernel.org>
To: Md Sadre Alam <quic_mdalam@quicinc.com>,
vkoul@kernel.org, linux-arm-msm@vger.kernel.org,
dmaengine@vger.kernel.org
Cc: quic_mmanikan@quicinc.com, quic_srichara@quicinc.com,
quic_varada@quicinc.com, robin.murphy@arm.com,
u.kleine-koenig@baylibre.com, martin.petersen@oracle.com,
fenghua.yu@intel.com, av2082000@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] dmaengine: qcom: bam_dma: Avoid writing unavailable register
Date: Tue, 7 Jan 2025 23:30:18 +0200 [thread overview]
Message-ID: <9ef3daa8-cdb1-49f2-8d19-a72d6210ff3a@kernel.org> (raw)
In-Reply-To: <20241220094203.3510335-1-quic_mdalam@quicinc.com>
On 20.12.24 11:42, 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>
> ---
My Dragonboard db845c fails to boot on recent linux-next releases and
git bisect points to this patch. It boots again when it's reverted.
[..]
>
> bchan->reconfigure = 0;
> @@ -1192,10 +1199,11 @@ static int bam_init(struct bam_device *bdev)
> u32 val;
>
> /* read revision and configuration information */
> - if (!bdev->num_ees) {
> - val = readl_relaxed(bam_addr(bdev, 0, BAM_REVISION));
> + val = readl_relaxed(bam_addr(bdev, 0, BAM_REVISION));
> + if (!bdev->num_ees)
> bdev->num_ees = (val >> NUM_EES_SHIFT) & NUM_EES_MASK;
> - }
> +
> + bdev->bam_revision = val & REVISION_MASK;
The problem seems to occur when we try to read the revision for the
slimbus bam instance at 0x17184000 (which has "qcom,num-ees = <2>;").
Thanks,
Georgi
next prev parent reply other threads:[~2025-01-07 21:30 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 [this message]
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
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=9ef3daa8-cdb1-49f2-8d19-a72d6210ff3a@kernel.org \
--to=djakov@kernel.org \
--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_mdalam@quicinc.com \
--cc=quic_mmanikan@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@quicinc.com \
--cc=robin.murphy@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.