[PATCH 0/2] soc: qcom: rpmh-rsc: Updates for RPMh read requests

Maulik Shah posted 2 patches 2 weeks, 1 day ago
There is a newer version of this series
drivers/soc/qcom/rpmh-internal.h |  2 ++
drivers/soc/qcom/rpmh-rsc.c      | 20 +++++++++++++++++---
drivers/soc/qcom/rpmh.c          |  6 ++++++
3 files changed, 25 insertions(+), 3 deletions(-)
[PATCH 0/2] soc: qcom: rpmh-rsc: Updates for RPMh read requests
Posted by Maulik Shah 2 weeks, 1 day ago
This series carries two RPMh read request updates.

RSC v4.5 and newer expect read commands to use a 4-byte message payload,
while write commands continue to use 8 bytes. Update the message length
used for read requests on those controllers.

Some platforms either do not support RPMh read requests or AOSS does not
respond to them. Issuing a read there can occupy an ACTIVE TCS indefinitely
and block subsequent write requests. Skip read commands on sm8150 and
sc8180x [1] returning a zero resource level so callers avoid error handling
for an unsupported read path.

Patch-1 do not have any dependency. Fixes tag is not required as existing
SoCs on upstream are all lower than v4.5 version. Patch-1 can be applied as
preparation for Hawi SoC support.

Patch-2 of the series carries fixes tag. I do not have sm8150 or sc8180x
to verify patch-2. If there are reports like [1] of read requests not
working on past SoC the list can be expanded within newly added
rpmh_rsc_no_rpmh_read() API.

[1] https://lore.kernel.org/linux-arm-msm/0a73bc50-71f4-43f8-9d95-14a763d63c61@oss.qualcomm.com/

Signed-off-by: Maulik Shah <maulik.shah@oss.qualcomm.com>
---
Maulik Shah (2):
      soc: qcom: rpmh-rsc: Update CMD_MSGID_LEN to 4 bytes for read request
      soc: qcom: rpmh-rsc: Skip read requests on unsupported platforms

 drivers/soc/qcom/rpmh-internal.h |  2 ++
 drivers/soc/qcom/rpmh-rsc.c      | 20 +++++++++++++++++---
 drivers/soc/qcom/rpmh.c          |  6 ++++++
 3 files changed, 25 insertions(+), 3 deletions(-)
---
base-commit: c68a982815dcce5464e3bf2a31ac94f5146c04ca
change-id: 20260910-rsc_read-27d689e37cb5

Best regards,
--  
Maulik Shah <maulik.shah@oss.qualcomm.com>