From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.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 1/3] dt-bindings: arm: qcoms-c: Include Eliza, Kaanapali and others in SoC names
Date: Wed, 20 May 2026 12:53:44 +0200 [thread overview]
Message-ID: <20260520-qualified-striped-husky-8bd1f9@quoll> (raw)
In-Reply-To: <de210bea-ba3c-4be9-aa97-5d04d4d3d9f3@oss.qualcomm.com>
On Wed, May 20, 2026 at 12:05:08PM +0200, Konrad Dybcio wrote:
> On 5/19/26 10:03 PM, Krzysztof Kozlowski wrote:
> > Grow the schema checking for proper SoC compatible naming style with
> > recently upstreamed new Qualcomm SoCs: Eliza, Kaanapali, Hawi, Mahua and
> > Shikra.
> >
> > Since switching from model numbers to codenames, this list with explicit
> > codenames will have to grow and list them all in order for the schema to
> > work. It feels like a churn, but the compatible naming is still mess,
> > for example, the schema pci/qcom,pcie-x1e80100.yaml with a legacy naming
> > vendor,IP-SoC (qcom,pcie-x1e80100) received a new compatible with new
> > style (qcom,glymur-pcie).
> >
> > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> > ---
> > Documentation/devicetree/bindings/arm/qcom-soc.yaml | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/arm/qcom-soc.yaml b/Documentation/devicetree/bindings/arm/qcom-soc.yaml
> > index 27261039d56f..b5f3a750cce8 100644
> > --- a/Documentation/devicetree/bindings/arm/qcom-soc.yaml
> > +++ b/Documentation/devicetree/bindings/arm/qcom-soc.yaml
> > @@ -25,7 +25,7 @@ select:
> > compatible:
> > oneOf:
> > - pattern: "^qcom,.*(apq|ipq|mdm|msm|qcm|qcs|q[dr]u|sa|sar|sc|sd[amx]|sm|x1[ep])[0-9]+.*$"
> > - - pattern: "^qcom,.*(glymur|milos).*$"
> > + - pattern: "^qcom,.*(eliza|kaanapali|glymur|hawi|mahua|milos|shikra).*$"
>
> +nord
True, ack.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-05-20 10:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 20:03 [PATCH 0/3] dt-bindings: arm: qcom-soc: Improve validation of expected SoC naming Krzysztof Kozlowski
2026-05-19 20:03 ` [PATCH 1/3] dt-bindings: arm: qcoms-c: Include Eliza, Kaanapali and others in SoC names Krzysztof Kozlowski
2026-05-20 10:05 ` Konrad Dybcio
2026-05-20 10:53 ` Krzysztof Kozlowski [this message]
2026-05-19 20:03 ` [PATCH 2/3] dt-bindings: arm: qcom-soc: Document more of existing legacy style compatibles Krzysztof Kozlowski
2026-05-20 10:04 ` Konrad Dybcio
2026-05-20 10:55 ` Krzysztof Kozlowski
2026-05-19 20:03 ` [PATCH 3/3] dt-bindings: arm: qcom-soc: Validate nodes with fallbacks Krzysztof Kozlowski
2026-05-19 23:56 ` Rob Herring (Arm)
2026-05-20 10:05 ` [PATCH 0/3] dt-bindings: arm: qcom-soc: Improve validation of expected SoC naming 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=20260520-qualified-striped-husky-8bd1f9@quoll \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--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®