From: bjorn.andersson@linaro.org (Bjorn Andersson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/8] firmware: qcom: scm: Use atomic SCM for cold boot
Date: Fri, 22 Apr 2016 16:50:05 -0700 [thread overview]
Message-ID: <20160422235005.GI3202@tuxbot> (raw)
In-Reply-To: <1461363432-5730-6-git-send-email-andy.gross@linaro.org>
On Fri 22 Apr 15:17 PDT 2016, Andy Gross wrote:
> This patch changes the cold_set_boot_addr function to use atomic SCM
> calls. This removes the need for memory allocation and instead places
> all arguments in registers.
>
> Signed-off-by: Andy Gross <andy.gross@linaro.org>
> ---
> drivers/firmware/qcom_scm-32.c | 40 ++++++++++++++++++++++++++--------------
> 1 file changed, 26 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/firmware/qcom_scm-32.c b/drivers/firmware/qcom_scm-32.c
[..]
> /*
> * Set the cold/warm boot address for one of the CPU cores.
> */
> -static int qcom_scm_set_boot_addr(u32 addr, int flags)
> +static int qcom_scm_set_boot_addr(u32 addr, int flags, bool do_atomic)
> {
> struct {
> __le32 flags;
> __le32 addr;
> } cmd;
>
> - cmd.addr = cpu_to_le32(addr);
> - cmd.flags = cpu_to_le32(flags);
> - return qcom_scm_call(QCOM_SCM_SVC_BOOT, QCOM_SCM_BOOT_ADDR,
> - &cmd, sizeof(cmd), NULL, 0);
> + if (do_atomic) {
> + return qcom_scm_call_atomic(QCOM_SCM_SVC_BOOT,
> + QCOM_SCM_BOOT_ADDR, 2, flags, addr);
> + } else {
> +
> + cmd.addr = cpu_to_le32(addr);
> + cmd.flags = cpu_to_le32(flags);
> +
> + return qcom_scm_call(QCOM_SCM_SVC_BOOT, QCOM_SCM_BOOT_ADDR,
> + &cmd, sizeof(cmd), NULL, 0);
> + }
I would prefer that you split this into two functions, rather than
hiding two functions bodies in one function.
Perhaps qcom_scm_set_boot_addr and qcom_scm_set_boot_addr_atomic?
> }
>
Regards,
Bjorn
next prev parent reply other threads:[~2016-04-22 23:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 22:17 [PATCH 0/8] Qualcomm SCM Rework Andy Gross
2016-04-22 22:17 ` [PATCH 1/8] dt/bindings: firmware: Add Qualcomm SCM binding Andy Gross
2016-04-22 23:12 ` Bjorn Andersson
2016-04-23 7:51 ` Stanimir Varbanov
2016-04-23 16:56 ` Rob Herring
2016-04-23 17:33 ` Andy Gross
2016-04-25 13:14 ` Rob Herring
2016-04-22 22:17 ` [PATCH 2/8] firmware: qcom: scm: Convert SCM to platform driver Andy Gross
2016-04-22 23:11 ` Bjorn Andersson
2016-04-23 4:43 ` Andy Gross
2016-04-22 22:17 ` [PATCH 3/8] firmware: qcom: scm: Generalize shared error map Andy Gross
2016-04-22 23:13 ` Bjorn Andersson
2016-04-22 22:17 ` [PATCH 4/8] firmware: qcom: scm: Add support for ARM64 SoCs Andy Gross
2016-04-22 23:41 ` Bjorn Andersson
2016-04-23 4:52 ` Andy Gross
2016-04-23 14:18 ` Bjorn Andersson
2016-04-22 22:17 ` [PATCH 5/8] firmware: qcom: scm: Use atomic SCM for cold boot Andy Gross
2016-04-22 23:50 ` Bjorn Andersson [this message]
2016-04-23 4:46 ` Andy Gross
2016-04-22 22:17 ` [PATCH 6/8] firmware: qcom: scm: Add memory allocation API Andy Gross
2016-04-22 23:23 ` Bjorn Andersson
2016-04-23 4:45 ` Andy Gross
2016-04-22 22:17 ` [PATCH 7/8] dts: qcom: apq8084: Add SCM firmware node Andy Gross
2016-04-22 23:50 ` Bjorn Andersson
2016-04-22 22:17 ` [PATCH 8/8] arm64: dts: msm8916: " Andy Gross
2016-04-23 0:03 ` Bjorn Andersson
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=20160422235005.GI3202@tuxbot \
--to=bjorn.andersson@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).