mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Christian Marangi <ansuelsmth@gmail.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: arm: qcom: add ipq8064 board variants
Date: Thu, 20 Nov 2025 16:25:37 +0100	[thread overview]
Message-ID: <8e75be2b-643e-4380-a018-3cb718745101@oss.qualcomm.com> (raw)
In-Reply-To: <20251120135435.12824-1-ansuelsmth@gmail.com>

On 11/20/25 2:54 PM, Christian Marangi wrote:
> Document QCOM ipq8064 board variants ipq8062, ipq8065, ipq8066,
> ipq8068, ipq8069 now matched by the QCOM cpufreq nvmem driver if
> socinfo can't derive the variant from SMEM.
> 
> Suggested-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> ---
>  .../devicetree/bindings/arm/qcom.yaml         | 20 +++++++++++++++++++
>  1 file changed, 20 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> index 18b5ed044f9f..0eb1619fede8 100644
> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> @@ -299,12 +299,32 @@ properties:
>                - qcom,ipq5424-rdp466
>            - const: qcom,ipq5424
>  
> +      - items:
> +          - const: qcom,ipq8062
> +          - const: qcom,ipq8064

Since 'items' requires that all items are present (and in this order),
we would normally have a board name go first.. but I suppose this is
some sort of a fix to the issue that sparked this (posting the link
for others to have more context)

But since these SoCs do exist, I wouldn't say this is necessarily
wrong..

https://lore.kernel.org/linux-arm-msm/20251105112136.371376-2-ansuelsmth@gmail.com/

Konrad

  reply	other threads:[~2025-11-20 15:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20 13:54 Christian Marangi
2025-11-20 15:25 ` Konrad Dybcio [this message]
2025-11-20 15:31   ` Christian Marangi
2025-11-20 17:41     ` Rob Herring
2025-11-20 22:49       ` Christian Marangi
2025-11-21  9:19         ` Konrad Dybcio

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=8e75be2b-643e-4380-a018-3cb718745101@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=ansuelsmth@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.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 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®