mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kathiravan T <kathirav@codeaurora.org>
To: Robert Marko <robert.marko@sartura.hr>
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: qcom: socinfo: Add remaining IPQ6018 family ID-s
Date: Mon, 17 May 2021 16:16:38 +0530	[thread overview]
Message-ID: <0870f5c7cadf86d102747ec4f3d1b77e@codeaurora.org> (raw)
In-Reply-To: <20210504114826.64376-1-robert.marko@sartura.hr>

On 2021-05-04 17:18, Robert Marko wrote:
> ID for IPQ6018 was previously added, but ID-s for rest of the
> family are missing.
> So, lets add those based on downstream driver.
> 
> Signed-off-by: Robert Marko <robert.marko@sartura.hr>

Reviewed-by: Kathiravan T <kathirav@codeaurora.org>

Nit: May be you can add the IPQ6005(453) variant as well? or you want to 
add it later on need basis?

> ---
>  drivers/soc/qcom/socinfo.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/soc/qcom/socinfo.c b/drivers/soc/qcom/socinfo.c
> index f6cfb79338f0..28bbc7a9227e 100644
> --- a/drivers/soc/qcom/socinfo.c
> +++ b/drivers/soc/qcom/socinfo.c
> @@ -255,6 +255,9 @@ static const struct soc_id soc_id[] = {
>  	{ 351, "SDA450" },
>  	{ 356, "SM8250" },
>  	{ 402, "IPQ6018" },
> +	{ 403, "IPQ6028" },
> +	{ 421, "IPQ6000" },
> +	{ 422, "IPQ6010" },
>  	{ 425, "SC7180" },
>  	{ 455, "QRB5165" },
>  };

-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a 
member of Code Aurora Forum, hosted by The Linux Foundation

  reply	other threads:[~2021-05-17 10:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04 11:48 Robert Marko
2021-05-17 10:46 ` Kathiravan T [this message]
2021-05-17 10:48   ` Robert Marko

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=0870f5c7cadf86d102747ec4f3d1b77e@codeaurora.org \
    --to=kathirav@codeaurora.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robert.marko@sartura.hr \
    /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

all inboxes | Powered by JetHome®