From: Maulik Shah <mkshah@codeaurora.org>
To: Stephen Boyd <swboyd@chromium.org>,
agross@kernel.org, bjorn.andersson@linaro.org
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
dianders@chromium.org, rnayak@codeaurora.org,
ilina@codeaurora.org, lsrao@codeaurora.org
Subject: Re: [PATCH] soc: qcom: rpmh: Use __fill_rpmh_msg API during rpmh_write()
Date: Mon, 22 Jun 2020 15:03:24 +0530 [thread overview]
Message-ID: <31fe6700-b7ea-6d57-0e83-75bcfb118c08@codeaurora.org> (raw)
In-Reply-To: <159255500790.62212.11790974984337702896@swboyd.mtv.corp.google.com>
Hi,
On 6/19/2020 1:53 PM, Stephen Boyd wrote:
> Quoting Maulik Shah (2020-06-18 06:14:11)
>> Use __fill_rpmh_msg API during rpmh_write(). This allows to
>> remove duplication of code in error checking, copying commands
>> and setting message state.
>>
>> Signed-off-by: Maulik Shah<mkshah@codeaurora.org>
>> ---
>> drivers/soc/qcom/rpmh.c | 12 +++---------
>> 1 file changed, 3 insertions(+), 9 deletions(-)
>>
>> diff --git a/drivers/soc/qcom/rpmh.c b/drivers/soc/qcom/rpmh.c
>> index f2b5b46c..a0a0b97 100644
>> --- a/drivers/soc/qcom/rpmh.c
>> +++ b/drivers/soc/qcom/rpmh.c
>> @@ -181,8 +181,6 @@ static int __rpmh_write(const struct device *dev, enum rpmh_state state,
>> struct cache_req *req;
>> int i;
>>
>> - rpm_msg->msg.state = state;
>> -
>> /* Cache the request in our store and link the payload */
>> for (i = 0; i < rpm_msg->msg.num_cmds; i++) {
>> req = cache_rpm_request(ctrlr, state, &rpm_msg->msg.cmds[i]);
>> @@ -190,8 +188,6 @@ static int __rpmh_write(const struct device *dev, enum rpmh_state state,
>> return PTR_ERR(req);
>> }
>>
>> - rpm_msg->msg.state = state;
>> -
>> if (state == RPMH_ACTIVE_ONLY_STATE) {
>> WARN_ON(irqs_disabled());
>> ret = rpmh_rsc_send_data(ctrlr_to_drv(ctrlr), &rpm_msg->msg);
> Were these two hunks just nonsense assignments to rpm_msg->msg.state?
yes, using __fill_rpmh_msg() and DEFINE_RPMH_MSG_ONSTACK takes care of
setting this.
Thanks,
Maulik
>
>> @@ -268,11 +264,9 @@ int rpmh_write(const struct device *dev, enum rpmh_state state,
>> DEFINE_RPMH_MSG_ONSTACK(dev, state, &compl, rpm_msg);
>> int ret;
>>
>> - if (!cmd || !n || n > MAX_RPMH_PAYLOAD)
>> - return -EINVAL;
>> -
>> - memcpy(rpm_msg.cmd, cmd, n * sizeof(*cmd));
>> - rpm_msg.msg.num_cmds = n;
>> + ret = __fill_rpmh_msg(&rpm_msg, state, cmd, n);
>> + if (ret)
>> + return ret;
> This part makes sense and is discussed in the commit text.
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
prev parent reply other threads:[~2020-06-22 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 13:14 [PATCH] soc: qcom: rpmh: Use __fill_rpmh_msg API during rpmh_write() Maulik Shah
2020-06-19 8:23 ` Stephen Boyd
2020-06-22 9:33 ` Maulik Shah [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=31fe6700-b7ea-6d57-0e83-75bcfb118c08@codeaurora.org \
--to=mkshah@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=dianders@chromium.org \
--cc=ilina@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsrao@codeaurora.org \
--cc=rnayak@codeaurora.org \
--cc=swboyd@chromium.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox