[PATCH 0/2] Shikra: Fix qce configuration

From: Kuldeep Singh

Date: Tue Oct 06 2026 - 07:16:20 EST


This patch series fixes QCE on Shikra.
Shikra is derived from agatti target and QCE was using different
compatible configuration.
Also, one more reason to update QCE is, clk-smd-rpm was doing proxy
voting and crypto was consuming it. With proxy vote removal, qce need to
vote for it's own clocks explicitly which is already being done for
agatti target. Adapt same mechanism to Shikra QCE too.

The current qce configuration will still work but this one is more
appropriately describing the hardware.

Validations:
- Qce probe and kcapi_convenience.sh tests.
- Correct clk_summary output as prepare_count and enable_count are 0.

The previous patch-seriest[1] was sent to an older thread and with feedback
received, submitting a new series.

[1] https://lore.kernel.org/lkml/20260907-b4-shikra_crypto_changse-v6-0-0676f61894b3@xxxxxxxxxxxxxxxx/

Signed-off-by: Kuldeep Singh <kuldeep.singh@xxxxxxxxxxxxxxxx>
---
Kuldeep Singh (2):
dt-bindings: crypto: Adjust Shikra compatible hierarchy
arm64: dts: qcom: shikra: Correct QCE node configuration

Documentation/devicetree/bindings/crypto/qcom-qce.yaml | 3 ++-
arch/arm64/boot/dts/qcom/shikra.dtsi | 7 +++----
2 files changed, 5 insertions(+), 5 deletions(-)
---
base-commit: bf1ee2bd5c2da8992f33c8950ef194aaff74ed6c
change-id: 20261006-shikra_qce_fix-270b735479ad

Best regards,
--
Kuldeep Singh <kuldeep.singh@xxxxxxxxxxxxxxxx>