From: "Raju P.L.S.S.S.N" <rplsssn@xxxxxxxxxxxxxx> Changes in v1: - Remove unnecessary EXPORT_SYMBOL in rpmh-rsc This set of patches add additional functionality to RPMH drivers[1]. PM drivers can choose to disallow idle modes when RSC controller is busy sending or processing requests. The patches add necessary functions to query the controller status. The controllers may be in 'solver' state, where they could be in autonomous mode executing low power modes for their hardware and as such are not available for sending active votes. Functionality to get notified about such state and disallow requests for state change in that case is added in these patches. The Power Domain Controller can be programmed to wakeup the RSC and setup the resources back in the active state, before the processor is woken up by a timer interrupt. The wakeup value from the timer hardware can be copied to the PDC which has its own timer and is in an always-on power domain. Programming the wakeup value is done through a separate register on the RSC. Functions necessary to program wakeup is added in the patches. Please consider reviewing this patchset. v1:https://lkml.org/lkml/2018/7/19/213 [1] https://lkml.org/lkml/2018/6/20/519 Lina Iyer (5): drivers: qcom: rpmh-rsc: return if the controller is idle drivers: qcom: rpmh: export controller idle status drivers: qcom: rpmh: disallow active requests in solver mode drivers: qcom: rpmh-rsc: write PDC data drivers: qcom: rpmh: write PDC data Raju P.L.S.S.S.N (1): drivers: qcom: rpmh-rsc: clear active mode configuration for waketcs drivers/soc/qcom/rpmh-internal.h | 6 ++ drivers/soc/qcom/rpmh-rsc.c | 132 ++++++++++++++++++++++++++++++--------- drivers/soc/qcom/rpmh.c | 100 +++++++++++++++++++++++++++++ include/soc/qcom/rpmh.h | 16 +++++ 4 files changed, 225 insertions(+), 29 deletions(-) -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,\na Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe linux-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
