devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Andy Gross <andy.gross@linaro.org>
Cc: linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	jilai wang <jilaiw@codeaurora.org>
Subject: Re: [Patch v2 6/8] firmware: qcom: scm: Use atomic SCM for cold boot
Date: Mon, 25 Apr 2016 18:44:57 -0700	[thread overview]
Message-ID: <20160426014457.GG29990@codeaurora.org> (raw)
In-Reply-To: <1461625725-32425-7-git-send-email-andy.gross@linaro.org>

On 04/25, 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 | 47 ++++++++++++++++++++----------------------
>  1 file changed, 22 insertions(+), 25 deletions(-)
> 
> diff --git a/drivers/firmware/qcom_scm-32.c b/drivers/firmware/qcom_scm-32.c
> index 0d2a3f8..419df4d 100644
> --- a/drivers/firmware/qcom_scm-32.c
> +++ b/drivers/firmware/qcom_scm-32.c
> @@ -294,34 +294,39 @@ out:
>  				(n & 0xf))
>  
>  /**
> - * qcom_scm_call_atomic1() - Send an atomic SCM command with one argument
> + * qcom_scm_call_atomic() - Send an atomic SCM command with one argument

Update doc to say 1 or 2 arguments now? I guess we get slightly
worse code because we force a load into the second argument
register even if it isn't used.

Also, is there a patch to change scm-32 to use dma allocations
for the buffer, or did I miss it?

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2016-04-26  1:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25 23:08 [Patch v2 0/8] Qualcomm SCM Rework Andy Gross
2016-04-25 23:08 ` [Patch v2 1/8] dt/bindings: firmware: Add Qualcomm SCM binding Andy Gross
2016-04-26  1:49   ` Stephen Boyd
2016-04-26  2:14     ` Andy Gross
2016-04-28 20:47       ` Rob Herring
2016-04-25 23:08 ` [Patch v2 2/8] firmware: qcom: scm: Convert SCM to platform driver Andy Gross
2016-04-26  1:29   ` Stephen Boyd
2016-04-29 19:25     ` Andy Gross
2016-04-25 23:08 ` [Patch v2 3/8] firmware: qcom: scm: Generalize shared error map Andy Gross
2016-04-26  1:29   ` Stephen Boyd
2016-04-25 23:08 ` [Patch v2 4/8] firmware: qcom: scm: Add memory allocation API Andy Gross
2016-04-26  1:50   ` Stephen Boyd
2016-04-25 23:08 ` [Patch v2 5/8] firmware: qcom: scm: Add support for ARM64 SoCs Andy Gross
     [not found] ` <1461625725-32425-1-git-send-email-andy.gross-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-04-25 23:08   ` [Patch v2 6/8] firmware: qcom: scm: Use atomic SCM for cold boot Andy Gross
2016-04-26  1:44     ` Stephen Boyd [this message]
2016-04-25 23:08   ` [Patch v2 7/8] dts: qcom: apq8084: Add SCM firmware node Andy Gross
2016-04-25 23:08 ` [Patch v2 8/8] arm64: dts: msm8916: " Andy Gross

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=20160426014457.GG29990@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=andy.gross@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jilaiw@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.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 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).