Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Maulik Shah <mkshah@codeaurora.org>
To: agross@kernel.org, bjorn.andersson@linaro.org
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	ulf.hansson@linaro.org, swboyd@chromium.org,
	dianders@chromium.org, rnayak@codeaurora.org,
	ilina@codeaurora.org, lsrao@codeaurora.org
Subject: Re: [RESEND v2 0/2] Modularize RPMH driver
Date: Mon, 19 Oct 2020 12:56:25 +0530	[thread overview]
Message-ID: <0def494d-a729-0728-c633-4a74fbe95a87@codeaurora.org> (raw)
In-Reply-To: <1601877596-32676-1-git-send-email-mkshah@codeaurora.org>

Hi Bjorn,

Can you please pick these changes.

Thanks,
Maulik

On 10/5/2020 11:29 AM, Maulik Shah wrote:
> Resending the patches rebasing on top of latest linux-next (next-20201002)
>
> Changes in v2:
> - Update commit message in patch 1
> - send [4] again instead of revert's revert in patch 2.
>
> This series is to modularize RPMH driver
>
> The tracepoint in RPMH driver was changed to _rcuidle variant based on the
> test results of unmerged series [1] where .power_off callback from genpd
> reported RCU warnings.
>
> The series which finally got merged [2] uses CPU PM notifications
> and genpd .power_off callback is not implemented in RPMH driver to invoke
> rpmh_flush(). The CPU PM notifications are done with RCU non idle in kernel
> (see cpu_pm_notify() uses rcu_irq_enter_irqson() before notifications)
>
> However using _rcuidle variant prevented RPMH driver to compile as module
> since these _rcuidle are not exported symbols for tracepoints.
>
> This seris reverts the change [3] to remove _rcuidle variant for tracepoint
> as its no more valid test case (genpd .power_off is not implemented)
> and bring backs the change [4] that was reverted due to _rcuidle preventing
> to become modular.
>
> [1] https://patchwork.kernel.org/project/linux-arm-msm/list/?series=243931
> [2] https://patchwork.kernel.org/project/linux-arm-msm/list/?series=269733
> [3] https://lore.kernel.org/r/20200115013751.249588-1-swboyd@chromium.org
> [4] https://lore.kernel.org/r/20200326224459.105170-3-john.stultz@linaro.org
>
> John Stultz (1):
>    soc: qcom: rpmh: Allow RPMH driver to be loaded as a module
>
> Maulik Shah (1):
>    Revert "drivers: qcom: rpmh-rsc: Use rcuidle tracepoints for rpmh"
>
>   drivers/soc/qcom/Kconfig    | 2 +-
>   drivers/soc/qcom/rpmh-rsc.c | 7 ++++++-
>   2 files changed, 7 insertions(+), 2 deletions(-)
>
-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation


      parent reply	other threads:[~2020-10-19  7:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05  5:59 [RESEND v2 0/2] Modularize RPMH driver Maulik Shah
2020-10-05  5:59 ` [RESEND v2 1/2] Revert "drivers: qcom: rpmh-rsc: Use rcuidle tracepoints for rpmh" Maulik Shah
2020-10-05  5:59 ` [RESEND v2 2/2] soc: qcom: rpmh: Allow RPMH driver to be loaded as a module Maulik Shah
2020-10-19  7:26 ` 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=0def494d-a729-0728-c633-4a74fbe95a87@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 \
    --cc=ulf.hansson@linaro.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