[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <13819b2d-26f0-14f4-9cb9-affb6b18f13d@quicinc.com>
Date: Wed, 4 May 2022 07:44:47 +0530
From: Sai Prakash Ranjan <quic_saipraka@...cinc.com>
To: Douglas Anderson <dianders@...omium.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>
CC: <matvore@...omium.org>,
"Reviewed-by : Stephen Boyd" <swboyd@...omium.org>,
Andy Gross <agross@...nel.org>,
<linux-arm-msm@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] soc: qcom: socinfo: Add another ID for sc7180
Hi,
On 5/3/2022 6:03 AM, Douglas Anderson wrote:
> It appears the some sc7180 devices, like the one in my
> sc7180-trogdor-homestar, report an ID of 407 instead of 425. Add
> another ID into the list.
>
> Signed-off-by: Douglas Anderson <dianders@...omium.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 cee579a267a6..2ef1dc2a1dd3 100644
> --- a/drivers/soc/qcom/socinfo.c
> +++ b/drivers/soc/qcom/socinfo.c
> @@ -318,6 +318,7 @@ static const struct soc_id soc_id[] = {
> { 396, "IPQ8071A" },
> { 402, "IPQ6018" },
> { 403, "IPQ6028" },
> + { 407, "SC7180" },
> { 421, "IPQ6000" },
> { 422, "IPQ6010" },
> { 425, "SC7180" },
Hmm, this ID maps to SM6250 which is a mobile variant. Not sure we should
use it for SC7180 which already has 425 ID assigned, perks of marketing :)
Thanks,
Sai
Powered by blists - more mailing lists