From: Kathiravan T <quic_kathirav@quicinc.com>
To: Robert Marko <robimarko@gmail.com>, <agross@kernel.org>,
<andersson@kernel.org>, <konrad.dybcio@linaro.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH 2/2] soc: qcom: socinfo: Add IDs for IPQ8174 family
Date: Sat, 2 Sep 2023 20:13:14 +0530 [thread overview]
Message-ID: <6f7e2b0a-5113-2526-bdfe-c9053c285d55@quicinc.com> (raw)
In-Reply-To: <20230901181041.1538999-2-robimarko@gmail.com>
On 9/1/2023 11:40 PM, Robert Marko wrote:
> IPQ8174 (Oak) family is part of the IPQ8074 family, but the ID-s for it
> are missing so lets add them.
>
> Signed-off-by: Robert Marko <robimarko@gmail.com>
> ---
> drivers/soc/qcom/socinfo.c | 3 +++
> 1 file changed, 3 insertions(+)
Reviewed-by: Kathiravan T <quic_kathirav@quicinc.com>
>
> diff --git a/drivers/soc/qcom/socinfo.c b/drivers/soc/qcom/socinfo.c
> index 497cfb720fcb..345f0b002eb5 100644
> --- a/drivers/soc/qcom/socinfo.c
> +++ b/drivers/soc/qcom/socinfo.c
> @@ -359,6 +359,9 @@ static const struct soc_id soc_id[] = {
> { qcom_board_id(SM6125) },
> { qcom_board_id(IPQ8070A) },
> { qcom_board_id(IPQ8071A) },
> + { qcom_board_id(IPQ8172) },
> + { qcom_board_id(IPQ8173) },
> + { qcom_board_id(IPQ8174) },
> { qcom_board_id(IPQ6018) },
> { qcom_board_id(IPQ6028) },
> { qcom_board_id(SDM429W) },
next prev parent reply other threads:[~2023-09-02 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 18:10 [PATCH 1/2] dt-bindings: arm: qcom,ids: " Robert Marko
2023-09-01 18:10 ` [PATCH 2/2] soc: qcom: socinfo: " Robert Marko
2023-09-02 14:43 ` Kathiravan T [this message]
2023-09-02 10:41 ` [PATCH 1/2] dt-bindings: arm: qcom,ids: " Conor Dooley
2023-09-02 14:42 ` Kathiravan T
2023-09-02 15:35 ` Dmitry Baryshkov
2023-09-04 3:42 ` Kathiravan T
2023-09-14 16:04 ` (subset) " Bjorn Andersson
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=6f7e2b0a-5113-2526-bdfe-c9053c285d55@quicinc.com \
--to=quic_kathirav@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robimarko@gmail.com \
/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®