From: Johan Hovold <johan@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Chris Lew <quic_clew@quicinc.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Stephan Gerhold <stephan.gerhold@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] soc: qcom: pd_mapper: fix ADSP PD maps
Date: Fri, 20 Sep 2024 11:02:22 +0200 [thread overview]
Message-ID: <Zu06HiEpA--LbaoU@hovoldconsulting.com> (raw)
In-Reply-To: <sziblrb4ggjzehl7fqwrh3bnedvwizh2vgymxu56zmls2whkup@yziunmooga7b>
On Fri, Sep 20, 2024 at 11:49:46AM +0300, Dmitry Baryshkov wrote:
> On Fri, Sep 20, 2024 at 10:21:03AM GMT, Johan Hovold wrote:
> > On Wed, Sep 18, 2024 at 04:02:39PM +0300, Dmitry Baryshkov wrote:
> > > On X1E8 devices root ADSP domain should have tms/pdr_enabled registered.
> > > Change the PDM domain data that is used for X1E80100 ADSP.
> >
> > Please expand the commit message so that it explains why this is
> > needed and not just describes what the patch does.
>
> Unfortunately in this case I have no idea. It marks the domain as
> restartable (?), this is what json files for CRD and T14s do. Maybe
> Chris can comment more.
Chris, could you help sort out if and why this change is needed?
https://lore.kernel.org/all/20240918-x1e-fix-pdm-pdr-v1-1-cefc79bb33d1@linaro.org/
> > What is the expected impact of this and is there any chance that this is
> > related to some of the in-kernel pd-mapper regression I've reported
> > (e.g. audio not being registered and failing with a PDR error)?
> >
> > https://lore.kernel.org/all/ZthVTC8dt1kSdjMb@hovoldconsulting.com/
>
> Still debugging this, sidetracked by OSS / LPC.
Johan
next prev parent reply other threads:[~2024-09-20 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 13:02 Dmitry Baryshkov
2024-09-20 8:21 ` Johan Hovold
2024-09-20 8:49 ` Dmitry Baryshkov
2024-09-20 9:02 ` Johan Hovold [this message]
2024-09-20 14:00 ` Chris Lew
2024-09-20 14:07 ` Dmitry Baryshkov
2024-09-24 16:40 ` Bjorn Andersson
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=Zu06HiEpA--LbaoU@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_clew@quicinc.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome