From: Maulik Shah <mkshah@codeaurora.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Stephen Boyd <swboyd@chromium.org>,
Evan Green <evgreen@chromium.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Andy Gross <agross@kernel.org>,
Matthias Kaehlcke <mka@chromium.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
Lina Iyer <ilina@codeaurora.org>,
lsrao@codeaurora.org
Subject: Re: [PATCH v15 4/7] soc: qcom: rpmh-rsc: Save base address of drv
Date: Mon, 6 Apr 2020 10:19:23 +0530 [thread overview]
Message-ID: <7fd2b098-0ad2-accc-a149-77680aeb4411@codeaurora.org> (raw)
In-Reply-To: <CAD=FV=X1t5bxgDqg5uPz4NrxfFMSCrGVwMgtnE5snDu330s78Q@mail.gmail.com>
Hi,
On 4/2/2020 10:30 PM, Doug Anderson wrote:
> Hi,
>
> On Tue, Mar 31, 2020 at 6:20 AM Maulik Shah <mkshah@codeaurora.org> wrote:
>> Add changes to save drv's base address for rsc. This is
>> used to read drv's configuration such as solver mode is
>> supported or to write into drv's registers.
>>
>> Signed-off-by: Maulik Shah <mkshah@codeaurora.org>
>> ---
>> drivers/soc/qcom/rpmh-internal.h | 2 ++
>> drivers/soc/qcom/rpmh-rsc.c | 11 +++++------
>> 2 files changed, 7 insertions(+), 6 deletions(-)
> I still see no usage of "drv->base" outside of the probe function even
> after applying your whole patch series. That implies that it can just
> stay as a local variable.
>
> If you have a later patch series that needs "drv->base" in some other
> RPMH function then this patch should be moved to the front of that
> series. Until then it feels like it should be dropped.
>
>
> -Doug
Okay, i will drop this and keep base local to probe only for now.
Thanks,
Maulik
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2020-04-06 4:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 13:19 [PATCH v15 0/7] Invoke rpmh_flush for non OSI targets Maulik Shah
2020-03-31 13:19 ` [PATCH v15 1/7] arm64: dts: qcom: sc7180: Add cpuidle low power states Maulik Shah
2020-03-31 13:19 ` [PATCH v15 2/7] soc: qcom: rpmh: Update dirty flag only when data changes Maulik Shah
2020-03-31 13:19 ` [PATCH v15 3/7] soc: qcom: rpmh: Invalidate SLEEP and WAKE TCSes before flushing new data Maulik Shah
2020-03-31 13:19 ` [PATCH v15 4/7] soc: qcom: rpmh-rsc: Save base address of drv Maulik Shah
2020-04-02 17:00 ` Doug Anderson
2020-04-06 4:49 ` Maulik Shah [this message]
2020-03-31 13:19 ` [PATCH v15 5/7] soc: qcom: rpmh: Invoke rpmh_flush() for dirty caches Maulik Shah
2020-04-02 20:13 ` Doug Anderson
2020-04-06 4:51 ` Maulik Shah
2020-03-31 13:19 ` [PATCH v15 6/7] soc: qcom: rpmh-rsc: Clear active mode configuration for wake TCS Maulik Shah
2020-04-02 20:14 ` Doug Anderson
2020-04-06 5:08 ` Maulik Shah
2020-04-06 15:33 ` Doug Anderson
2020-03-31 13:19 ` [PATCH v15 7/7] soc: qcom: rpmh-rsc: Allow using free WAKE TCS for active request Maulik Shah
2020-04-02 20:13 ` Doug Anderson
2020-04-06 5:12 ` Maulik Shah
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=7fd2b098-0ad2-accc-a149-77680aeb4411@codeaurora.org \
--to=mkshah@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=dianders@chromium.org \
--cc=evgreen@chromium.org \
--cc=ilina@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsrao@codeaurora.org \
--cc=mka@chromium.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