From: "Rob Herring (Arm)" <robh@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Konrad Dybcio <konradybcio@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 0/2] arm64: dts: qcom: add AP8096SG variant of DB820c
Date: Wed, 12 Nov 2025 07:56:44 -0600 [thread overview]
Message-ID: <176295563376.1637834.15728252609575729805.robh@kernel.org> (raw)
In-Reply-To: <20251111-db820c-pro-v1-0-6eece16c5c23@oss.qualcomm.com>
On Tue, 11 Nov 2025 18:02:50 +0200, Dmitry Baryshkov wrote:
> While debugging a crash in the DRM CI setup I noticed that the kernel
> warns about the unsupported hardware in CPU OPP tables. After a small
> research I found that board indeed uses APQ8096SG rather than APQ8096.
> Add DT file for these boards.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> ---
> Dmitry Baryshkov (2):
> dt-bindings: arm: qcom: add Dragonboard 820c using APQ8096SG SoC
> arm64: dts: qcom: add apq8096sg-db820c, AP8096SG variant of DB820c
>
> Documentation/devicetree/bindings/arm/qcom.yaml | 7 +
> arch/arm64/boot/dts/qcom/Makefile | 1 +
> arch/arm64/boot/dts/qcom/apq8096-db820c.dts | 1126 +-------------------
> .../{apq8096-db820c.dts => apq8096-db820c.dtsi} | 5 -
> arch/arm64/boot/dts/qcom/apq8096sg-db820c.dts | 15 +
> 5 files changed, 24 insertions(+), 1130 deletions(-)
> ---
> base-commit: ab40c92c74c6b0c611c89516794502b3a3173966
> change-id: 20251111-db820c-pro-8ecd2a28520e
>
> Best regards,
> --
> With best wishes
> Dmitry
>
>
>
My bot found new DTB warnings on the .dts files added or changed in this
series.
Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.
If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:
pip3 install dtschema --upgrade
This patch series was applied (using b4) to base:
Base: ab40c92c74c6b0c611c89516794502b3a3173966 (use --merge-base to override)
If this is not the correct base, please add 'base-commit' tag
(or use b4 which does this automatically)
New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/qcom/' for 20251111-db820c-pro-v1-0-6eece16c5c23@oss.qualcomm.com:
arch/arm64/boot/dts/qcom/apq8096sg-db820c.dtb: usb@6af8800 (qcom,msm8996-dwc3): 'extcon' does not match any of the regexes: '^pinctrl-[0-9]+$', '^usb@[0-9a-f]+$'
from schema $id: http://devicetree.org/schemas/usb/qcom,dwc3.yaml
arch/arm64/boot/dts/qcom/apq8096sg-db820c.dtb: usb@76f8800 (qcom,msm8996-dwc3): 'extcon' does not match any of the regexes: '^pinctrl-[0-9]+$', '^usb@[0-9a-f]+$'
from schema $id: http://devicetree.org/schemas/usb/qcom,dwc3.yaml
arch/arm64/boot/dts/qcom/apq8096sg-db820c.dtb: syscon@9a10000 (syscon): compatible: ['syscon'] is too short
from schema $id: http://devicetree.org/schemas/mfd/syscon-common.yaml
WARNING: multiple messages have this Message-ID (diff)
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Konrad Dybcio <konradybcio@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 0/2] arm64: dts: qcom: add AP8096SG variant of DB820c
Date: Wed, 12 Nov 2025 08:26:47 -0600 [thread overview]
Message-ID: <176295563376.1637834.15728252609575729805.robh@kernel.org> (raw)
Message-ID: <20251112142647.FsyA7lNMIvvGOPJaAvR0KnI4SJg6b0HBcLB6MIo9enE@z> (raw)
In-Reply-To: <20251111-db820c-pro-v1-0-6eece16c5c23@oss.qualcomm.com>
On Tue, 11 Nov 2025 18:02:50 +0200, Dmitry Baryshkov wrote:
> While debugging a crash in the DRM CI setup I noticed that the kernel
> warns about the unsupported hardware in CPU OPP tables. After a small
> research I found that board indeed uses APQ8096SG rather than APQ8096.
> Add DT file for these boards.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> ---
> Dmitry Baryshkov (2):
> dt-bindings: arm: qcom: add Dragonboard 820c using APQ8096SG SoC
> arm64: dts: qcom: add apq8096sg-db820c, AP8096SG variant of DB820c
>
> Documentation/devicetree/bindings/arm/qcom.yaml | 7 +
> arch/arm64/boot/dts/qcom/Makefile | 1 +
> arch/arm64/boot/dts/qcom/apq8096-db820c.dts | 1126 +-------------------
> .../{apq8096-db820c.dts => apq8096-db820c.dtsi} | 5 -
> arch/arm64/boot/dts/qcom/apq8096sg-db820c.dts | 15 +
> 5 files changed, 24 insertions(+), 1130 deletions(-)
> ---
> base-commit: ab40c92c74c6b0c611c89516794502b3a3173966
> change-id: 20251111-db820c-pro-8ecd2a28520e
>
> Best regards,
> --
> With best wishes
> Dmitry
>
>
>
My bot found new DTB warnings on the .dts files added or changed in this
series.
Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.
If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:
pip3 install dtschema --upgrade
This patch series was applied (using b4) to base:
Base: ab40c92c74c6b0c611c89516794502b3a3173966 (use --merge-base to override)
If this is not the correct base, please add 'base-commit' tag
(or use b4 which does this automatically)
New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/qcom/' for 20251111-db820c-pro-v1-0-6eece16c5c23@oss.qualcomm.com:
arch/arm64/boot/dts/qcom/apq8096sg-db820c.dtb: usb@6af8800 (qcom,msm8996-dwc3): 'extcon' does not match any of the regexes: '^pinctrl-[0-9]+$', '^usb@[0-9a-f]+$'
from schema $id: http://devicetree.org/schemas/usb/qcom,dwc3.yaml
arch/arm64/boot/dts/qcom/apq8096sg-db820c.dtb: usb@76f8800 (qcom,msm8996-dwc3): 'extcon' does not match any of the regexes: '^pinctrl-[0-9]+$', '^usb@[0-9a-f]+$'
from schema $id: http://devicetree.org/schemas/usb/qcom,dwc3.yaml
arch/arm64/boot/dts/qcom/apq8096sg-db820c.dtb: syscon@9a10000 (syscon): compatible: ['syscon'] is too short
from schema $id: http://devicetree.org/schemas/mfd/syscon-common.yaml
next prev parent reply other threads:[~2025-11-12 13:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 16:02 [PATCH 0/2] arm64: dts: qcom: add AP8096SG variant of DB820c Dmitry Baryshkov
2025-11-11 16:02 ` [PATCH 1/2] dt-bindings: arm: qcom: add Dragonboard 820c using APQ8096SG SoC Dmitry Baryshkov
2025-11-12 10:45 ` Konrad Dybcio
2025-11-17 17:49 ` Rob Herring (Arm)
2025-11-11 16:02 ` [PATCH 2/2] arm64: dts: qcom: add apq8096sg-db820c, AP8096SG variant of DB820c Dmitry Baryshkov
2025-11-12 9:44 ` Konrad Dybcio
2025-11-13 20:32 ` Dmitry Baryshkov
2025-11-14 21:31 ` Konrad Dybcio
2025-11-15 0:09 ` Dmitry Baryshkov
2025-11-17 11:54 ` Konrad Dybcio
2026-01-14 0:12 ` Dmitry Baryshkov
2026-01-14 9:28 ` Konrad Dybcio
2025-11-12 13:56 ` Rob Herring (Arm) [this message]
2025-11-12 14:26 ` [PATCH 0/2] arm64: dts: qcom: add " Rob Herring (Arm)
2026-02-27 3:46 ` 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=176295563376.1637834.15728252609575729805.robh@kernel.org \
--to=robh@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.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