From: Bjorn Andersson <bjorn.andersson@sonymobile.com>
To: Andy Gross <agross@codeaurora.org>
Cc: <linux-arm-msm@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, Mark Brown <broonie@kernel.org>,
Stephen Boyd <sboyd@codeaurora.org>
Subject: Re: [Patch v2] firmware: qcom: scm: Add function stubs for ARM64
Date: Fri, 11 Sep 2015 16:26:16 -0700 [thread overview]
Message-ID: <20150911232616.GE13472@usrtlx11787.corpusers.net> (raw)
In-Reply-To: <1442005276-31971-1-git-send-email-agross@codeaurora.org>
On Fri 11 Sep 14:01 PDT 2015, Andy Gross wrote:
> This patch adds stubs for the SCM functions exposed in the QCOM SCM API.
>
> Signed-off-by: Andy Gross <agross@codeaurora.org>
> ---
> drivers/firmware/Kconfig | 8 +++++
> drivers/firmware/Makefile | 3 +-
> drivers/firmware/qcom_scm-64.c | 63 ++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 73 insertions(+), 1 deletion(-)
> create mode 100644 drivers/firmware/qcom_scm-64.c
>
> diff --git a/drivers/firmware/Kconfig b/drivers/firmware/Kconfig
> index 99c69a3..72720eb 100644
> --- a/drivers/firmware/Kconfig
> +++ b/drivers/firmware/Kconfig
> @@ -136,6 +136,14 @@ config QCOM_SCM
> bool
> depends on ARM || ARM64
>
> +config QCOM_SCM_32
> + def_bool y
> + depends on QCOM_SCM && ARM
> +
> +config QCOM_SCM_64
> + def_bool y
> + depends on QCOM_SCM && ARM64
> +
So if QCOM_SCM is selected by a consumer then the dependencies here will
be met and the correct implementation will be chosen, as these aren't
possible to deselect?
I guess that's an okay approach, so:
Acked-by: Bjorn Andersson <bjorn.andersson@sonymobile.com>
Regards,
Bjorn
prev parent reply other threads:[~2015-09-11 23:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 21:01 [Patch v2] firmware: qcom: scm: Add function stubs for ARM64 Andy Gross
2015-09-11 21:56 ` Russell King - ARM Linux
2015-09-11 23:26 ` Bjorn Andersson [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=20150911232616.GE13472@usrtlx11787.corpusers.net \
--to=bjorn.andersson@sonymobile.com \
--cc=agross@codeaurora.org \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@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