From: "Barnabás Czémán" <barnabas.czeman@mainlining.org>
To: "Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Abel Vesa" <abelvesa@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Stephan Gerhold" <stephan.gerhold@linaro.org>,
"Otto Pflüger" <otto.pflueger@abscue.de>,
"Dang Huynh" <danct12@riseup.net>,
"Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>,
"Luca Weiss" <luca@lucaweiss.eu>,
"Vladimir Lypak" <vladimir.lypak@gmail.com>
Cc: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] MSM8917/MSM8937/MSM8953 fix prng
Date: Sun, 15 Nov 2026 14:28:59 +0100 [thread overview]
Message-ID: <fbd93a808dbd9c4ab859494d7b33c7d3@mainlining.org> (raw)
In-Reply-To: <20261001-prng-fix-v1-0-72f924527465@mainlining.org>
On 2026-10-01 07:51, Barnabás Czémán wrote:
> On MSM8917/MSM8937/MSM8953 HW QRNG is configured by TZ.
> qcom-rng driver will not have access to the configuration registers.
> Change the compatible to qcom,prng-ee for skip the initialization
> sequence.
>
> Compatbile changes are fixing this issue:
> Call trace:
> qcom_rng_init+0x6c/0xe8 [qcom_rng] (P)
> crypto_create_tfm_node+0x154/0x198
> crypto_alloc_tfm_node+0xa4/0x1b4
> crypto_alloc_rng+0x34/0x48
> rng_bind+0x60/0xa8 [algif_rng]
> alg_bind+0x15c/0x1f4 [af_alg]
> __arm64_sys_bind+0xb8/0x120
> invoke_syscall+0x6c/0x11c
> el0_svc_common+0x98/0xe8
> do_el0_svc+0x2c/0x3c
> el0_svc+0x40/0x9c
> el0t_64_sync_handler+0x88/0x134
> el0t_64_sync+0x1a0/0x1a4
>
> Signed-off-by: Barnabás Czémán <barnabas.czeman@mainlining.org>
> ---
> Barnabás Czémán (3):
> arm64: dts: qcom: msm8917: change prng compatible
> arm64: dts: qcom: msm8937: change prng compatible
> arm64: dts: qcom: msm8953: change prng compatible
>
> arch/arm64/boot/dts/qcom/msm8917.dtsi | 2 +-
> arch/arm64/boot/dts/qcom/msm8937.dtsi | 2 +-
> arch/arm64/boot/dts/qcom/msm8953.dtsi | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
> ---
> base-commit: 6c2cb8b8b843d216ab549b678a0d8831c43153e0
> change-id: 20261001-prng-fix-5366a05da970
>
> Best regards,
> --
> Barnabás Czémán <barnabas.czeman@mainlining.org>
I hope it is not forgotten, should I resend it?
prev parent reply other threads:[~2026-11-15 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 5:51 [PATCH 0/3] MSM8917/MSM8937/MSM8953 fix prng Barnabás Czémán
2026-10-01 5:51 ` [PATCH 1/3] arm64: dts: qcom: msm8917: change prng compatible Barnabás Czémán
2026-10-01 5:51 ` [PATCH 2/3] arm64: dts: qcom: msm8937: " Barnabás Czémán
2026-10-01 5:51 ` [PATCH 3/3] arm64: dts: qcom: msm8953: " Barnabás Czémán
2026-10-01 9:21 ` [PATCH 0/3] MSM8917/MSM8937/MSM8953 fix prng Konrad Dybcio
2026-11-15 13:28 ` Barnabás Czémán [this message]
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=fbd93a808dbd9c4ab859494d7b33c7d3@mainlining.org \
--to=barnabas.czeman@mainlining.org \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=danct12@riseup.net \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@lucaweiss.eu \
--cc=otto.pflueger@abscue.de \
--cc=robh@kernel.org \
--cc=stephan.gerhold@linaro.org \
--cc=vladimir.lypak@gmail.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 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.