All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Anderson <dianders@chromium.org>
To: Lina Iyer <ilina@codeaurora.org>
Cc: Raju P L S S S N <rplsssn@codeaurora.org>,
	Andy Gross <andy.gross@linaro.org>,
	David Brown <david.brown@linaro.org>,
	linux-arm-msm@vger.kernel.org,
	"open list:ARM/QUALCOMM SUPPORT" <linux-soc@vger.kernel.org>,
	Rajendra Nayak <rnayak@codeaurora.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Stephen Boyd <sboyd@kernel.org>,
	Evan Green <evgreen@chromium.org>,
	Matthias Kaehlcke <mka@chromium.org>
Subject: Re: [PATCH v11 04/10] drivers: qcom: rpmh: add RPMH helper functions
Date: Mon, 18 Jun 2018 12:54:07 -0700	[thread overview]
Message-ID: <CAD=FV=VVLGR-ynvURvQB2yU5HNb0-Z5e-1_McJ1Wu5PFpJ72Yg@mail.gmail.com> (raw)
In-Reply-To: <20180618190637.GG21724@codeaurora.org>

Hi,

On Mon, Jun 18, 2018 at 12:06 PM, Lina Iyer <ilina@codeaurora.org> wrote:
> On Mon, Jun 18 2018 at 12:33 -0600, Doug Anderson wrote:
>>
>> Lina,
>>
>> On Mon, Jun 18, 2018 at 9:39 AM, Lina Iyer <ilina@codeaurora.org> wrote:
>>>>
>>>> +/**
>>>>  * struct rsc_drv: the Direct Resource Voter (DRV) of the
>>>>  * Resource State Coordinator controller (RSC)
>>>>  *
>>>> @@ -52,6 +78,7 @@ struct tcs_group {
>>>>  * @tcs:        TCS groups
>>>>  * @tcs_in_use: s/w state of the TCS
>>>>  * @lock:       synchronize state of the controller
>>>> + * @ctrl:       controller to handle cases like batch requests
>>>
>>>
>>> This is not only for batch requests.
>>> This is handle to the DRV's client. @client might be a better name than
>>> @ctrlr.
>>
>>
>> The name "ctrlr" also matches the name of the structure.  Are you
>> suggesting also renaming "struct rpmh_ctrlr" to "struct rpmh_client",
>> or you think they should be different names?
>>
> Just the name of the variable. I was just a nice to have. I wouldn't
> block for this though.
>
> I also got a couple Bot reported issues on this and the previous
> revision that I have sent to Raju. He is planning to the post the v12
> tomorrow his time after fixing them. If you can wait until then, I would
> recommend picking up the v12 instead of this.

OK, if Raju can post the v12 tomorrow his time then that sounds like a
great plan to me.  While you're at it, I noticed that checkpatch
yelled about a few lines that were > 80 characters long for no good
reason.  Those would be nice to fix too.

-Doug

  reply	other threads:[~2018-06-18 19:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18 13:37 [PATCH v11 00/10] drivers/qcom: add RPMH communication support Raju P L S S S N
2018-06-18 13:37 ` [PATCH v11 01/10] drivers: qcom: rpmh-rsc: add RPMH controller for QCOM SoCs Raju P L S S S N
2018-06-18 13:37 ` [PATCH v11 02/10] dt-bindings: introduce RPMH RSC bindings for Qualcomm SoCs Raju P L S S S N
2018-06-18 13:37 ` [PATCH v11 03/10] drivers: qcom: rpmh-rsc: log RPMH requests in FTRACE Raju P L S S S N
2018-06-19  5:20   ` Bjorn Andersson
2018-06-19 13:12     ` Raju P L S S S N
2018-06-18 13:37 ` [PATCH v11 04/10] drivers: qcom: rpmh: add RPMH helper functions Raju P L S S S N
2018-06-18 16:39   ` Lina Iyer
2018-06-18 18:33     ` Doug Anderson
2018-06-18 19:06       ` Lina Iyer
2018-06-18 19:54         ` Doug Anderson [this message]
2018-06-18 20:11           ` Lina Iyer
2018-06-18 13:37 ` [PATCH v11 05/10] drivers: qcom: rpmh-rsc: write sleep/wake requests to TCS Raju P L S S S N
2018-06-18 13:37 ` [PATCH v11 06/10] drivers: qcom: rpmh-rsc: allow invalidation of sleep/wake TCS Raju P L S S S N
2018-06-18 13:37 ` [PATCH v11 07/10] drivers: qcom: rpmh: cache sleep/wake state requests Raju P L S S S N
2018-06-18 13:37 ` [PATCH v11 08/10] drivers: qcom: rpmh: allow requests to be sent asynchronously Raju P L S S S N
2018-06-18 13:37 ` [PATCH v11 09/10] drivers: qcom: rpmh: add support for batch RPMH request Raju P L S S S N
2018-06-18 13:37 ` [PATCH v11 10/10] drivers: qcom: rpmh-rsc: allow active requests from wake TCS Raju P L S S S N
2018-06-18 17:42 ` [PATCH v11 00/10] drivers/qcom: add RPMH communication support Doug Anderson

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='CAD=FV=VVLGR-ynvURvQB2yU5HNb0-Z5e-1_McJ1Wu5PFpJ72Yg@mail.gmail.com' \
    --to=dianders@chromium.org \
    --cc=andy.gross@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=david.brown@linaro.org \
    --cc=evgreen@chromium.org \
    --cc=ilina@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-soc@vger.kernel.org \
    --cc=mka@chromium.org \
    --cc=rnayak@codeaurora.org \
    --cc=rplsssn@codeaurora.org \
    --cc=sboyd@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.