From: Conor Dooley <conor@kernel.org>
To: Robert Marko <robimarko@gmail.com>
Cc: 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 1/2] dt-bindings: arm: qcom,ids: Add IDs for IPQ8174 family
Date: Sat, 2 Sep 2023 11:41:34 +0100 [thread overview]
Message-ID: <20230902-e4a05a649a5f17b1e724cd21@fedora> (raw)
In-Reply-To: <20230901181041.1538999-1-robimarko@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 947 bytes --]
On Fri, Sep 01, 2023 at 08:10:04PM +0200, 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>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> include/dt-bindings/arm/qcom,ids.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/include/dt-bindings/arm/qcom,ids.h b/include/dt-bindings/arm/qcom,ids.h
> index be12e1dd1f38..d2b84a308fde 100644
> --- a/include/dt-bindings/arm/qcom,ids.h
> +++ b/include/dt-bindings/arm/qcom,ids.h
> @@ -203,6 +203,9 @@
> #define QCOM_ID_SM6125 394
> #define QCOM_ID_IPQ8070A 395
> #define QCOM_ID_IPQ8071A 396
> +#define QCOM_ID_IPQ8172 397
> +#define QCOM_ID_IPQ8173 398
> +#define QCOM_ID_IPQ8174 399
> #define QCOM_ID_IPQ6018 402
> #define QCOM_ID_IPQ6028 403
> #define QCOM_ID_SDM429W 416
> --
> 2.41.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-09-02 10:41 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: Add IDs for IPQ8174 family Robert Marko
2023-09-01 18:10 ` [PATCH 2/2] soc: qcom: socinfo: " Robert Marko
2023-09-02 14:43 ` Kathiravan T
2023-09-02 10:41 ` Conor Dooley [this message]
2023-09-02 14:42 ` [PATCH 1/2] dt-bindings: arm: qcom,ids: " 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=20230902-e4a05a649a5f17b1e724cd21@fedora \
--to=conor@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).