From: Johan Hovold <johan@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: neil.armstrong@linaro.org, Johan Hovold <johan+linaro@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Chris Lew <quic_clew@quicinc.com>,
Stephan Gerhold <stephan.gerhold@linaro.org>,
Abel Vesa <abel.vesa@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev, stable@vger.kernel.org
Subject: Re: [PATCH] soc: qcom: mark pd-mapper as broken
Date: Thu, 10 Oct 2024 16:07:07 +0200 [thread overview]
Message-ID: <Zwffi40TyaMZruHj@hovoldconsulting.com> (raw)
In-Reply-To: <jtxci47paynh3uuulwempryixgbdvcnx3fhtkru733s6rkip7l@jxoaaxdxvp3d>
On Thu, Oct 10, 2024 at 04:45:57PM +0300, Dmitry Baryshkov wrote:
> On Thu, Oct 10, 2024 at 03:24:19PM GMT, Johan Hovold wrote:
> > Again, you may just be lucky, we have x1e users that also don't hit
> > these issues due to how things are timed during boot in their setups.
> >
> > If there's some actual evidence that suggests that this is limited to
> > x1e, then that would of course be a different matter, but I'm not aware
> > of anything like that currently.
>
> Is there an evidence that it is broken on other platforms? I have been
> daily driving the pd-mapper in my testing kernels for a long period of
> time.
Yes, Chris's analysis of the ECANCELED issue suggests that this is not
SoC specific.
Johan
next prev parent reply other threads:[~2024-10-10 14:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 7:42 [PATCH] soc: qcom: mark pd-mapper as broken Johan Hovold
2024-10-10 9:55 ` Dmitry Baryshkov
2024-10-10 10:11 ` Johan Hovold
2024-10-10 10:55 ` Dmitry Baryshkov
2024-10-10 11:44 ` Johan Hovold
2024-10-10 11:46 ` neil.armstrong
2024-10-10 13:24 ` Johan Hovold
2024-10-10 13:45 ` Dmitry Baryshkov
2024-10-10 14:07 ` Johan Hovold [this message]
2024-10-10 14:13 ` Dmitry Baryshkov
2024-10-10 14:20 ` Johan Hovold
2024-10-10 14:42 ` Dmitry Baryshkov
2024-10-11 10:01 ` Stephan Gerhold
2025-01-06 19:10 ` Frank Oltmanns
2025-01-07 10:02 ` Johan Hovold
2025-01-08 14:06 ` Johan Hovold
2025-01-11 14:21 ` Frank Oltmanns
2025-01-13 9:07 ` Johan Hovold
2025-02-05 22:23 ` Frank Oltmanns
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=Zwffi40TyaMZruHj@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=johan+linaro@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_clew@quicinc.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=stephan.gerhold@linaro.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.