Devicetree
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>,
	Val Packett <val@packett.cool>
Cc: "Matti Lehtimäki" <matti.lehtimaki@gmail.com>,
	"Luca Weiss" <luca@lucaweiss.eu>,
	"Vladimir Lypak" <vladimir.lypak@gmail.com>,
	"Barnabás Czémán" <barnabas.czeman@mainlining.org>,
	"Konrad Dybcio" <konrad.dybcio@oss.qualcomm.com>,
	"Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>,
	~postmarketos/upstreaming@lists.sr.ht, linux@mainlining.org,
	phone-devel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-remoteproc@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v2] remoteproc: qcom_wcnss: Fix handling the lack of PD regulators in v3
Date: Fri, 10 Jul 2026 13:07:07 -0500	[thread overview]
Message-ID: <178370682982.2572738.1804514769753985254.b4-ty@kernel.org> (raw)
In-Reply-To: <20260201210230.911220-1-val@packett.cool>


On Sun, 01 Feb 2026 17:55:03 -0300, Val Packett wrote:
> The changes introduced to handle single power domain platforms have
> swapped the info pointer increment from num_pd_vregs to num_pds, which
> would shift the info pointer past the end of the array for pronto-v3,
> which does not list power domain regulators in vregs.
> 
> This showed up as a difference between GCC- and LLVM-compiled kernels
> on SDM632 devices, where only with LLVM one would get the
> "regulator request with no identifier" error, because the out-of-bounds
> memory ended up being zeroed. Fix by skipping the increment when there
> are more power domains than regulators.
> 
> [...]

Applied, thanks!

[1/1] remoteproc: qcom_wcnss: Fix handling the lack of PD regulators in v3
      commit: 3dbc90b9c22ea96e37bf55f6011e63b5123ec668

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

  parent reply	other threads:[~2026-07-10 18:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-01 20:55 [PATCH v2] remoteproc: qcom_wcnss: Fix handling the lack of PD regulators in v3 Val Packett
2026-02-02 10:57 ` Konrad Dybcio
2026-02-23 20:03 ` Bjorn Andersson
2026-02-24 18:45   ` Val Packett
2026-02-27  3:52     ` Bjorn Andersson
2026-02-27  4:20       ` Val Packett
2026-07-10 18:07 ` Bjorn Andersson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-02-09 23:05 Yoann Lecuyer

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=178370682982.2572738.1804514769753985254.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=barnabas.czeman@mainlining.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=justinstitt@google.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=linux@mainlining.org \
    --cc=llvm@lists.linux.dev \
    --cc=luca@lucaweiss.eu \
    --cc=mathieu.poirier@linaro.org \
    --cc=matti.lehtimaki@gmail.com \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=nick.desaulniers+lkml@gmail.com \
    --cc=phone-devel@vger.kernel.org \
    --cc=val@packett.cool \
    --cc=vladimir.lypak@gmail.com \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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