[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAPZXbJmpAZfxFK9LKaS=wZXX+pez9j5k3gjF+CRPgP6Ru4DuRA@mail.gmail.com>
Date: Tue, 10 Feb 2026 00:05:49 +0100
From: Yoann Lecuyer <yoann.lecuyer@...il.com>
To: val@...kett.cool
Cc: andersson@...nel.org, barnabas.czeman@...nlining.org,
devicetree@...r.kernel.org, dmitry.baryshkov@....qualcomm.com,
justinstitt@...gle.com, konrad.dybcio@....qualcomm.com,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-remoteproc@...r.kernel.org, linux@...nlining.org, llvm@...ts.linux.dev,
Luca Weiss <luca@...aweiss.eu>, mathieu.poirier@...aro.org, matti.lehtimaki@...il.com,
morbo@...gle.com, Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <nick.desaulniers+lkml@...il.com>, phone-devel@...r.kernel.org,
vladimir.lypak@...il.com, ~postmarketos/upstreaming@...ts.sr.ht
Subject: Re: [PATCH v2] remoteproc: qcom_wcnss: Fix handling the lack of PD
regulators in v3
> 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.
>
> Signed-off-by: Val Packett <val@...kett.cool>
Tested-by: Yoann Lecuyer <yoann.lecuyer@...il.com>
Yoann
Powered by blists - more mailing lists