From: Stephen Boyd <swboyd@chromium.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Maulik Shah <mkshah@codeaurora.org>,
Douglas Anderson <dianders@chromium.org>
Subject: [PATCH v3/RESEND 0/3] Even moar rpmh cleanups
Date: Wed, 20 May 2020 23:04:22 -0700 [thread overview]
Message-ID: <20200521060425.24285-1-swboyd@chromium.org> (raw)
(Resent with more Ccs and To lines)
We remove the tcs_is_free() API and then do super micro optimizations on
the irq handler. I haven't tested anything here so most likely there's a
bug (again again)!
Changes from v2:
* Went back in time and used the v1 patch for the first patch with
the fixes to make it not so complicated
Changes from v1:
* First patch became even moar complicated because it combines
find_free_tcs() with the check for a request in flight
* Fixed subject in patch 2
* Put back unsigned long for bitmap operation to silence compiler
warning
* Picked up review tags
Stephen Boyd (3):
soc: qcom: rpmh-rsc: Remove tcs_is_free() API
soc: qcom: rpmh-rsc: Loop over fewer bits in irq handler
soc: qcom: rpmh-rsc: Fold WARN_ON() into if condition
drivers/soc/qcom/rpmh-rsc.c | 65 +++++++++++++------------------------
1 file changed, 22 insertions(+), 43 deletions(-)
Cc: Maulik Shah <mkshah@codeaurora.org>
Cc: Douglas Anderson <dianders@chromium.org>
base-commit: 1f7a3eb785e4a4e196729cd3d5ec97bd5f9f2940
--
Sent by a computer, using git, on the internet
next reply other threads:[~2020-05-21 6:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 6:04 Stephen Boyd [this message]
2020-05-21 6:04 ` [PATCHv3/RESEND 1/3] soc: qcom: rpmh-rsc: Remove tcs_is_free() API Stephen Boyd
2020-05-26 7:07 ` Maulik Shah
2020-05-28 18:04 ` Doug Anderson
2020-05-21 6:04 ` [PATCHv3/RESEND 2/3] soc: qcom: rpmh-rsc: Loop over fewer bits in irq handler Stephen Boyd
2020-05-21 6:04 ` [PATCHv3/RESEND 3/3] soc: qcom: rpmh-rsc: Fold WARN_ON() into if condition Stephen Boyd
2020-05-21 6:11 ` [PATCH v3/RESEND 0/3] Even moar rpmh cleanups Randy Dunlap
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=20200521060425.24285-1-swboyd@chromium.org \
--to=swboyd@chromium.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkshah@codeaurora.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