[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200306155707.RFT.7.I8e187cdfb7a31f5bb7724f1f937f2862ee464a35@changeid>
Date: Fri, 6 Mar 2020 15:59:49 -0800
From: Douglas Anderson <dianders@...omium.org>
To: Andy Gross <agross@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Maulik Shah <mkshah@...eaurora.org>
Cc: Rajendra Nayak <rnayak@...eaurora.org>, mka@...omium.org,
evgreen@...omium.org, swboyd@...omium.org,
Lina Iyer <ilina@...eaurora.org>,
Douglas Anderson <dianders@...omium.org>,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [RFT PATCH 7/9] drivers: qcom: rpmh-rsc: Warning if tcs_write() used for non-active
tcs_write() is documented to only be useful for writing
RPMH_ACTIVE_ONLY_STATE. Let's be loud if someone messes up.
Signed-off-by: Douglas Anderson <dianders@...omium.org>
---
drivers/soc/qcom/rpmh-rsc.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/soc/qcom/rpmh-rsc.c b/drivers/soc/qcom/rpmh-rsc.c
index c63441182358..693873fce895 100644
--- a/drivers/soc/qcom/rpmh-rsc.c
+++ b/drivers/soc/qcom/rpmh-rsc.c
@@ -550,6 +550,12 @@ static int tcs_write(struct rsc_drv *drv, const struct tcs_request *msg)
unsigned long flags;
int ret;
+ /*
+ * It only makes sense to grab a whole TCS for ourselves if we're
+ * triggering right away, which we only do for ACTIVE_ONLY.
+ */
+ WARN_ON(msg->state != RPMH_ACTIVE_ONLY_STATE);
+
tcs = get_tcs_for_msg(drv, msg);
if (IS_ERR(tcs))
return PTR_ERR(tcs);
--
2.25.1.481.gfbce0eb801-goog
Powered by blists - more mailing lists