From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Douglas Anderson <dianders@chromium.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
swboyd@chromium.org, Andy Gross <agross@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: qcom: socinfo: add SC7180 entry to soc_id array
Date: Fri, 14 Aug 2020 10:37:13 +0530 [thread overview]
Message-ID: <87c217e5fc01c73fe008179274fa373f@codeaurora.org> (raw)
In-Reply-To: <20200813080345.1.I85bb28f9ea3fa3bf797ecaf0a5218ced4cfaa6e2@changeid>
On 2020-08-13 20:33, Douglas Anderson wrote:
> Add an entry for SC7180 SoC.
>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> ---
>
> drivers/soc/qcom/socinfo.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/soc/qcom/socinfo.c b/drivers/soc/qcom/socinfo.c
> index e19102f46302..e56eea29615c 100644
> --- a/drivers/soc/qcom/socinfo.c
> +++ b/drivers/soc/qcom/socinfo.c
> @@ -223,6 +223,7 @@ static const struct soc_id soc_id[] = {
> { 321, "SDM845" },
> { 341, "SDA845" },
> { 356, "SM8250" },
> + { 425, "SC7180" },
> };
>
> static const char *socinfo_machine(struct device *dev, unsigned int
> id)
From the chipinfo document that I have at hand, this is correct soc id
for SC7180, so
Reviewed-by: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
Thanks,
Sai
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
member
of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2020-08-14 5:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 15:03 [PATCH] soc: qcom: socinfo: add SC7180 entry to soc_id array Douglas Anderson
2020-08-13 17:30 ` Stephen Boyd
2020-08-14 5:07 ` Sai Prakash Ranjan [this message]
2020-09-14 20:17 ` Doug Anderson
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=87c217e5fc01c73fe008179274fa373f@codeaurora.org \
--to=saiprakash.ranjan@codeaurora.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=swboyd@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.