From: Vinod Koul <vkoul@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>
Cc: "Caleb Connolly" <caleb.connolly@linaro.org>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Amit Vadhavana" <av2082000@gmail.com>,
"Dave Jiang" <dave.jiang@intel.com>,
"Fenghua Yu" <fenghua.yu@intel.com>,
"Kees Cook" <kees@kernel.org>,
"Md Sadre Alam" <quic_mdalam@quicinc.com>,
"Robin Murphy" <robin.murphy@arm.com>,
"David Heidelberg" <david@ixit.cz>,
"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
dmaengine@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] Revert "dmaengine: qcom: bam_dma: Avoid writing unavailable register"
Date: Mon, 10 Feb 2025 15:49:52 +0530 [thread overview]
Message-ID: <Z6nSyNz91IIzrVuv@vaman> (raw)
In-Reply-To: <mjyavvk5jymhfdn4czffihi55nvlxea5ldgchsmkyd6lomrlbr@7224az7nsnsa>
On 08-02-25, 20:03, Bjorn Andersson wrote:
> On Sat, Feb 08, 2025 at 10:30:54PM +0000, Caleb Connolly wrote:
> > This commit causes a hard crash on sdm845 and likely other platforms.
> > Revert it until a proper fix is found.
> >
> > This reverts commit 57a7138d0627309d469719f1845d2778c251f358.
> >
>
> I posted below patch yesterday, which reverts the change for
> bdev->num_ees != 0 (i.e. SDM845), while still retaining the introduced
> NDP vs Lite logic.
Bjorn,
Given the issues reported by Stephan, do you this we should revert
and then patch it up..?
--
~Vinod
next prev parent reply other threads:[~2025-02-10 10:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 22:30 [PATCH] Revert "dmaengine: qcom: bam_dma: Avoid writing unavailable register" Caleb Connolly
2025-02-08 22:33 ` Caleb Connolly
2025-02-09 0:23 ` David Heidelberg
2025-02-09 2:03 ` Bjorn Andersson
2025-02-10 10:19 ` Vinod Koul [this message]
2025-02-10 11:40 ` neil.armstrong
2025-02-24 13:16 ` Manivannan Sadhasivam
2025-02-10 11:39 ` neil.armstrong
2025-02-27 12:07 ` Vinod Koul
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=Z6nSyNz91IIzrVuv@vaman \
--to=vkoul@kernel.org \
--cc=andersson@kernel.org \
--cc=av2082000@gmail.com \
--cc=caleb.connolly@linaro.org \
--cc=dave.jiang@intel.com \
--cc=david@ixit.cz \
--cc=dmaengine@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=fenghua.yu@intel.com \
--cc=kees@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=quic_mdalam@quicinc.com \
--cc=robin.murphy@arm.com \
--cc=u.kleine-koenig@baylibre.com \
/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