arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dts | 100 +++++++++++++++++++ arch/arm64/boot/dts/qcom/qcs9100-ride.dts | 99 ++++++++++++++++++ 2 files changed, 199 insertions(+)
This patch series is based on Tengfei Fan's patches [1] which adds support
for QCS9100 Ride and QCS9100 Ride Rev3 boards.
Some new carveouts (viz. gunyah_md and a few pil dtb carveouts) have been
introduced and the size and base addresses have been updated for
a few of existing carveouts compared to SA8775P. Also, tz_ffi_mem carveout
and its corresponding scm reference has been removed as it is not required
for these boards. Incorporate these changes in the updated memory map
for QCS9100 Ride and QCS9100 Rev3 boards.
[1] https://lore.kernel.org/all/20240911-add_qcs9100_support-v2-4-e43a71ceb017@quicinc.com/
Signed-off-by: Pratyush Brahma <quic_pbrahma@quicinc.com>
---
arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dts | 100 +++++++++++++++++++
arch/arm64/boot/dts/qcom/qcs9100-ride.dts | 99 ++++++++++++++++++
2 files changed, 199 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dts b/arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dts
index 759d1ec694b2..0fa1afc0de17 100644
--- a/arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dts
+++ b/arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dts
@@ -5,7 +5,107 @@
/dts-v1/;
#include "sa8775p-ride-r3.dts"
+
+/delete-node/ &pil_adsp_mem;
+/delete-node/ &pil_gdsp0_mem;
+/delete-node/ &pil_gdsp1_mem;
+/delete-node/ &pil_cdsp0_mem;
+/delete-node/ &pil_gpu_mem;
+/delete-node/ &pil_cdsp1_mem;
+/delete-node/ &pil_cvp_mem;
+/delete-node/ &pil_video_mem;
+/delete-node/ &audio_mdf_mem;
+/delete-node/ &trusted_apps_mem;
+/delete-node/ &tz_ffi_mem;
+
/ {
model = "Qualcomm QCS9100 Ride Rev3";
compatible = "qcom,qcs9100-ride-r3", "qcom,qcs9100", "qcom,sa8775p";
+
+ reserved-memory {
+ #address-cells = <2>;
+ #size-cells = <2>;
+ ranges;
+
+ gunyah_md_mem: gunyah-md@91a80000 {
+ reg = <0x0 0x91a80000 0x0 0x80000>;
+ no-map;
+ };
+
+ pil_adsp_mem: pil-adsp@95900000 {
+ reg = <0x0 0x95900000 0x0 0x1e00000>;
+ no-map;
+ };
+
+ q6_adsp_dtb_mem: q6-adsp-dtb@97700000 {
+ reg = <0x0 0x97700000 0x0 0x80000>;
+ no-map;
+ };
+
+ q6_gdsp0_dtb_mem: q6-gdsp0-dtb@97780000 {
+ reg = <0x0 0x97780000 0x0 0x80000>;
+ no-map;
+ };
+
+ pil_gdsp0_mem: pil-gdsp0@97800000 {
+ reg = <0x0 0x97800000 0x0 0x1e00000>;
+ no-map;
+ };
+
+ pil_gdsp1_mem: pil-gdsp1@99600000 {
+ reg = <0x0 0x99600000 0x0 0x1e00000>;
+ no-map;
+ };
+
+ q6_gdsp1_dtb_mem: q6-gdsp1-dtb@9b400000 {
+ reg = <0x0 0x9b400000 0x0 0x80000>;
+ no-map;
+ };
+
+ q6_cdsp0_dtb_mem: q6-cdsp0-dtb@9b480000 {
+ reg = <0x0 0x9b480000 0x0 0x80000>;
+ no-map;
+ };
+
+ pil_cdsp0_mem: pil-cdsp0@9b500000 {
+ reg = <0x0 0x9b500000 0x0 0x1e00000>;
+ no-map;
+ };
+
+ pil_gpu_mem: pil-gpu@9d300000 {
+ reg = <0x0 0x9d300000 0x0 0x2000>;
+ no-map;
+ };
+
+ q6_cdsp1_dtb_mem: q6-cdsp1-dtb@9d380000 {
+ reg = <0x0 0x9d380000 0x0 0x80000>;
+ no-map;
+ };
+
+ pil_cdsp1_mem: pil-cdsp1@9d400000 {
+ reg = <0x0 0x9d400000 0x0 0x1e00000>;
+ no-map;
+ };
+
+ pil_cvp_mem: pil-cvp@9f200000 {
+ reg = <0x0 0x9f200000 0x0 0x700000>;
+ no-map;
+ };
+
+ pil_video_mem: pil-video@9f900000 {
+ reg = <0x0 0x9f900000 0x0 0x1000000>;
+ no-map;
+ };
+
+ trusted_apps_mem: trusted-apps@d1900000 {
+ reg = <0x0 0xd1900000 0x0 0x1c00000>;
+ no-map;
+ };
+ };
+
+ firmware {
+ scm {
+ /delete-property/ memory-region;
+ };
+ };
};
diff --git a/arch/arm64/boot/dts/qcom/qcs9100-ride.dts b/arch/arm64/boot/dts/qcom/qcs9100-ride.dts
index 979462dfec30..f79954ae0d38 100644
--- a/arch/arm64/boot/dts/qcom/qcs9100-ride.dts
+++ b/arch/arm64/boot/dts/qcom/qcs9100-ride.dts
@@ -5,7 +5,106 @@
/dts-v1/;
#include "sa8775p-ride.dts"
+
+/delete-node/ &pil_adsp_mem;
+/delete-node/ &pil_gdsp0_mem;
+/delete-node/ &pil_gdsp1_mem;
+/delete-node/ &pil_cdsp0_mem;
+/delete-node/ &pil_gpu_mem;
+/delete-node/ &pil_cdsp1_mem;
+/delete-node/ &pil_cvp_mem;
+/delete-node/ &pil_video_mem;
+/delete-node/ &audio_mdf_mem;
+/delete-node/ &trusted_apps_mem;
+/delete-node/ &tz_ffi_mem;
+
/ {
model = "Qualcomm QCS9100 Ride";
compatible = "qcom,qcs9100-ride", "qcom,qcs9100", "qcom,sa8775p";
+
+ reserved-memory {
+ #address-cells = <2>;
+ #size-cells = <2>;
+ ranges;
+ gunyah_md_mem: gunyah-md@91a80000 {
+ reg = <0x0 0x91a80000 0x0 0x80000>;
+ no-map;
+ };
+
+ pil_adsp_mem: pil-adsp@95900000 {
+ reg = <0x0 0x95900000 0x0 0x1e00000>;
+ no-map;
+ };
+
+ q6_adsp_dtb_mem: q6-adsp-dtb@97700000 {
+ reg = <0x0 0x97700000 0x0 0x80000>;
+ no-map;
+ };
+
+ q6_gdsp0_dtb_mem: q6-gdsp0-dtb@97780000 {
+ reg = <0x0 0x97780000 0x0 0x80000>;
+ no-map;
+ };
+
+ pil_gdsp0_mem: pil-gdsp0@97800000 {
+ reg = <0x0 0x97800000 0x0 0x1e00000>;
+ no-map;
+ };
+
+ pil_gdsp1_mem: pil-gdsp1@99600000 {
+ reg = <0x0 0x99600000 0x0 0x1e00000>;
+ no-map;
+ };
+
+ q6_gdsp1_dtb_mem: q6-gdsp1-dtb@9b400000 {
+ reg = <0x0 0x9b400000 0x0 0x80000>;
+ no-map;
+ };
+
+ q6_cdsp0_dtb_mem: q6-cdsp0-dtb@9b480000 {
+ reg = <0x0 0x9b480000 0x0 0x80000>;
+ no-map;
+ };
+
+ pil_cdsp0_mem: pil-cdsp0@9b500000 {
+ reg = <0x0 0x9b500000 0x0 0x1e00000>;
+ no-map;
+ };
+
+ pil_gpu_mem: pil-gpu@9d300000 {
+ reg = <0x0 0x9d300000 0x0 0x2000>;
+ no-map;
+ };
+
+ q6_cdsp1_dtb_mem: q6-cdsp1-dtb@9d380000 {
+ reg = <0x0 0x9d380000 0x0 0x80000>;
+ no-map;
+ };
+
+ pil_cdsp1_mem: pil-cdsp1@9d400000 {
+ reg = <0x0 0x9d400000 0x0 0x1e00000>;
+ no-map;
+ };
+
+ pil_cvp_mem: pil-cvp@9f200000 {
+ reg = <0x0 0x9f200000 0x0 0x700000>;
+ no-map;
+ };
+
+ pil_video_mem: pil-video@9f900000 {
+ reg = <0x0 0x9f900000 0x0 0x1000000>;
+ no-map;
+ };
+
+ trusted_apps_mem: trusted-apps@d1900000 {
+ reg = <0x0 0xd1900000 0x0 0x1c00000>;
+ no-map;
+ };
+ };
+
+ firmware {
+ scm {
+ /delete-property/ memory-region;
+ };
+ };
};
--
2.17.1On 11/19/2024 2:55 PM, Pratyush Brahma wrote: > This patch series is based on Tengfei Fan's patches [1] which adds support > for QCS9100 Ride and QCS9100 Ride Rev3 boards. > > Some new carveouts (viz. gunyah_md and a few pil dtb carveouts) have been > introduced and the size and base addresses have been updated for > a few of existing carveouts compared to SA8775P. Also, tz_ffi_mem carveout > and its corresponding scm reference has been removed as it is not required > for these boards. Incorporate these changes in the updated memory map > for QCS9100 Ride and QCS9100 Rev3 boards. > > [1] https://lore.kernel.org/all/20240911-add_qcs9100_support-v2-4-e43a71ceb017@quicinc.com/ > > Signed-off-by: Pratyush Brahma <quic_pbrahma@quicinc.com> The memory map for qcs9100-ride-r3 and qcs9100-ride is exactly same. A good churn you are first deleting(based on sa8775p) and then re-adding for qcs9100-ride*. I think it's better to move common qcs9100-ride* to a common file ex: qcs9100-ride.dtsi and keep specifics further to .dts files? This will ensure common entities are present at same place with no duplicates. -- Regards Kuldeep
On Wed, Nov 20, 2024 at 01:41:03AM +0530, Kuldeep Singh wrote: > > > On 11/19/2024 2:55 PM, Pratyush Brahma wrote: > > This patch series is based on Tengfei Fan's patches [1] which adds support > > for QCS9100 Ride and QCS9100 Ride Rev3 boards. > > > > Some new carveouts (viz. gunyah_md and a few pil dtb carveouts) have been > > introduced and the size and base addresses have been updated for > > a few of existing carveouts compared to SA8775P. Also, tz_ffi_mem carveout > > and its corresponding scm reference has been removed as it is not required > > for these boards. Incorporate these changes in the updated memory map > > for QCS9100 Ride and QCS9100 Rev3 boards. > > > > [1] https://lore.kernel.org/all/20240911-add_qcs9100_support-v2-4-e43a71ceb017@quicinc.com/ > > > > Signed-off-by: Pratyush Brahma <quic_pbrahma@quicinc.com> > > The memory map for qcs9100-ride-r3 and qcs9100-ride is exactly same. > A good churn you are first deleting(based on sa8775p) and then re-adding > for qcs9100-ride*. > > I think it's better to move common qcs9100-ride* to a common file ex: > qcs9100-ride.dtsi and keep specifics further to .dts files? > > This will ensure common entities are present at same place with no > duplicates. I'd second this proposal. -- With best wishes Dmitry
On 11/20/2024 5:24 PM, Dmitry Baryshkov wrote: > On Wed, Nov 20, 2024 at 01:41:03AM +0530, Kuldeep Singh wrote: >> >> On 11/19/2024 2:55 PM, Pratyush Brahma wrote: >>> This patch series is based on Tengfei Fan's patches [1] which adds support >>> for QCS9100 Ride and QCS9100 Ride Rev3 boards. >>> >>> Some new carveouts (viz. gunyah_md and a few pil dtb carveouts) have been >>> introduced and the size and base addresses have been updated for >>> a few of existing carveouts compared to SA8775P. Also, tz_ffi_mem carveout >>> and its corresponding scm reference has been removed as it is not required >>> for these boards. Incorporate these changes in the updated memory map >>> for QCS9100 Ride and QCS9100 Rev3 boards. >>> >>> [1] https://lore.kernel.org/all/20240911-add_qcs9100_support-v2-4-e43a71ceb017@quicinc.com/ >>> >>> Signed-off-by: Pratyush Brahma <quic_pbrahma@quicinc.com> >> The memory map for qcs9100-ride-r3 and qcs9100-ride is exactly same. >> A good churn you are first deleting(based on sa8775p) and then re-adding >> for qcs9100-ride*. >> >> I think it's better to move common qcs9100-ride* to a common file ex: >> qcs9100-ride.dtsi and keep specifics further to .dts files? >> >> This will ensure common entities are present at same place with no >> duplicates. > I'd second this proposal. Ok then, I see that there are some thermal and gpu enablement changes as well in the pipeline to be posted. Having a common dtsi file for these iot socs would help in reducing the duplication at board dts file level for all these changes. In that regard, does naming it "sa8775-iot.dtsi" sound good? The board files can include this dtsi. -- Thanks and Regards Pratyush Brahma
On Thu, Nov 21, 2024 at 05:08:22PM +0530, Pratyush Brahma wrote: > > On 11/20/2024 5:24 PM, Dmitry Baryshkov wrote: > > On Wed, Nov 20, 2024 at 01:41:03AM +0530, Kuldeep Singh wrote: > > > > > > On 11/19/2024 2:55 PM, Pratyush Brahma wrote: > > > > This patch series is based on Tengfei Fan's patches [1] which adds support > > > > for QCS9100 Ride and QCS9100 Ride Rev3 boards. > > > > > > > > Some new carveouts (viz. gunyah_md and a few pil dtb carveouts) have been > > > > introduced and the size and base addresses have been updated for > > > > a few of existing carveouts compared to SA8775P. Also, tz_ffi_mem carveout > > > > and its corresponding scm reference has been removed as it is not required > > > > for these boards. Incorporate these changes in the updated memory map > > > > for QCS9100 Ride and QCS9100 Rev3 boards. > > > > > > > > [1] https://lore.kernel.org/all/20240911-add_qcs9100_support-v2-4-e43a71ceb017@quicinc.com/ > > > > > > > > Signed-off-by: Pratyush Brahma <quic_pbrahma@quicinc.com> > > > The memory map for qcs9100-ride-r3 and qcs9100-ride is exactly same. > > > A good churn you are first deleting(based on sa8775p) and then re-adding > > > for qcs9100-ride*. > > > > > > I think it's better to move common qcs9100-ride* to a common file ex: > > > qcs9100-ride.dtsi and keep specifics further to .dts files? > > > > > > This will ensure common entities are present at same place with no > > > duplicates. > > I'd second this proposal. > Ok then, I see that there are some thermal and gpu enablement changes as > well in the pipeline to be posted. What kind of changes? It's really hard to make a judgement if you don't describe what is happening. > Having a common dtsi file for these iot socs would help in reducing the > duplication at board > dts file level for all these changes. In that regard, does naming it > "sa8775-iot.dtsi" sound good? The board files can include this dtsi. qcs9100.dtsi? -- With best wishes Dmitry
On 11/22/2024 12:20 AM, Dmitry Baryshkov wrote: > On Thu, Nov 21, 2024 at 05:08:22PM +0530, Pratyush Brahma wrote: >> >> On 11/20/2024 5:24 PM, Dmitry Baryshkov wrote: >>> On Wed, Nov 20, 2024 at 01:41:03AM +0530, Kuldeep Singh wrote: >>>> >>>> On 11/19/2024 2:55 PM, Pratyush Brahma wrote: >>>>> This patch series is based on Tengfei Fan's patches [1] which adds support >>>>> for QCS9100 Ride and QCS9100 Ride Rev3 boards. >>>>> >>>>> Some new carveouts (viz. gunyah_md and a few pil dtb carveouts) have been >>>>> introduced and the size and base addresses have been updated for >>>>> a few of existing carveouts compared to SA8775P. Also, tz_ffi_mem carveout >>>>> and its corresponding scm reference has been removed as it is not required >>>>> for these boards. Incorporate these changes in the updated memory map >>>>> for QCS9100 Ride and QCS9100 Rev3 boards. >>>>> >>>>> [1] https://lore.kernel.org/all/20240911-add_qcs9100_support-v2-4-e43a71ceb017@quicinc.com/ >>>>> >>>>> Signed-off-by: Pratyush Brahma <quic_pbrahma@quicinc.com> >>>> The memory map for qcs9100-ride-r3 and qcs9100-ride is exactly same. >>>> A good churn you are first deleting(based on sa8775p) and then re-adding >>>> for qcs9100-ride*. >>>> >>>> I think it's better to move common qcs9100-ride* to a common file ex: >>>> qcs9100-ride.dtsi and keep specifics further to .dts files? >>>> >>>> This will ensure common entities are present at same place with no >>>> duplicates. >>> I'd second this proposal. >> Ok then, I see that there are some thermal and gpu enablement changes as >> well in the pipeline to be posted. > > What kind of changes? It's really hard to make a judgement if you don't > describe what is happening> >> Having a common dtsi file for these iot socs would help in reducing the >> duplication at board >> dts file level for all these changes. In that regard, does naming it >> "sa8775-iot.dtsi" sound good? The board files can include this dtsi. > > qcs9100.dtsi? Looks good to me. If there are let's say below variants for qcs9100 in future as well. Ex: qcs9100-ride, qcs9100-ride-XX, qcs9100-ride-YY or qcs9100-XX, qcs9100-YY Then I think we can think of common filenames like qcs9100.dtsi, qcs9100-ride.dtsi etc. -- Regards Kuldeep
On 11/20/2024 1:41 AM, Kuldeep Singh wrote: > > On 11/19/2024 2:55 PM, Pratyush Brahma wrote: >> This patch series is based on Tengfei Fan's patches [1] which adds support >> for QCS9100 Ride and QCS9100 Ride Rev3 boards. >> >> Some new carveouts (viz. gunyah_md and a few pil dtb carveouts) have been >> introduced and the size and base addresses have been updated for >> a few of existing carveouts compared to SA8775P. Also, tz_ffi_mem carveout >> and its corresponding scm reference has been removed as it is not required >> for these boards. Incorporate these changes in the updated memory map >> for QCS9100 Ride and QCS9100 Rev3 boards. >> >> [1] https://lore.kernel.org/all/20240911-add_qcs9100_support-v2-4-e43a71ceb017@quicinc.com/ >> >> Signed-off-by: Pratyush Brahma <quic_pbrahma@quicinc.com> > The memory map for qcs9100-ride-r3 and qcs9100-ride is exactly same. > A good churn you are first deleting(based on sa8775p) and then re-adding > for qcs9100-ride*. > > I think it's better to move common qcs9100-ride* to a common file ex: > qcs9100-ride.dtsi and keep specifics further to .dts files? > > This will ensure common entities are present at same place with no > duplicates. > > -- > > Regards > Kuldeep It is true that the memory map for qcs9100-ride.dts and qcs9100-ride-r3.dts is exactly the same. However, I am not sure if having a new common dtsi file would be the right approach here since qcs9100* dts files inherit the sa8775p.dtsi file already. I'll wait for Bjorn's comment here. -- Thanks and Regards Pratyush Brahma
On Tue, 19 Nov 2024 14:55:01 +0530, Pratyush Brahma wrote:
> This patch series is based on Tengfei Fan's patches [1] which adds support
> for QCS9100 Ride and QCS9100 Ride Rev3 boards.
>
> Some new carveouts (viz. gunyah_md and a few pil dtb carveouts) have been
> introduced and the size and base addresses have been updated for
> a few of existing carveouts compared to SA8775P. Also, tz_ffi_mem carveout
> and its corresponding scm reference has been removed as it is not required
> for these boards. Incorporate these changes in the updated memory map
> for QCS9100 Ride and QCS9100 Rev3 boards.
>
> [1] https://lore.kernel.org/all/20240911-add_qcs9100_support-v2-4-e43a71ceb017@quicinc.com/
>
> Signed-off-by: Pratyush Brahma <quic_pbrahma@quicinc.com>
> ---
> arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dts | 100 +++++++++++++++++++
> arch/arm64/boot/dts/qcom/qcs9100-ride.dts | 99 ++++++++++++++++++
> 2 files changed, 199 insertions(+)
>
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
New warnings running 'make CHECK_DTBS=y qcom/qcs9100-ride-r3.dtb qcom/qcs9100-ride.dtb' for 20241119092501.31111-1-quic_pbrahma@quicinc.com:
arch/arm64/boot/dts/qcom/qcs9100-ride.dtb: qcom,gpi-dma@800000: $nodename:0: 'qcom,gpi-dma@800000' does not match '^dma-controller(@.*)?$'
from schema $id: http://devicetree.org/schemas/dma/qcom,gpi.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dtb: qcom,gpi-dma@800000: $nodename:0: 'qcom,gpi-dma@800000' does not match '^dma-controller(@.*)?$'
from schema $id: http://devicetree.org/schemas/dma/qcom,gpi.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride.dtb: bluetooth: 'vddwlcx-supply' is a required property
from schema $id: http://devicetree.org/schemas/net/bluetooth/qualcomm-bluetooth.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride.dtb: bluetooth: 'vddwlmx-supply' is a required property
from schema $id: http://devicetree.org/schemas/net/bluetooth/qualcomm-bluetooth.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride.dtb: bluetooth: 'vddrfa1p8-supply' is a required property
from schema $id: http://devicetree.org/schemas/net/bluetooth/qualcomm-bluetooth.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dtb: bluetooth: 'vddwlcx-supply' is a required property
from schema $id: http://devicetree.org/schemas/net/bluetooth/qualcomm-bluetooth.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dtb: bluetooth: 'vddwlmx-supply' is a required property
from schema $id: http://devicetree.org/schemas/net/bluetooth/qualcomm-bluetooth.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dtb: bluetooth: 'vddrfa1p8-supply' is a required property
from schema $id: http://devicetree.org/schemas/net/bluetooth/qualcomm-bluetooth.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride.dtb: qcom,gpi-dma@900000: $nodename:0: 'qcom,gpi-dma@900000' does not match '^dma-controller(@.*)?$'
from schema $id: http://devicetree.org/schemas/dma/qcom,gpi.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dtb: qcom,gpi-dma@900000: $nodename:0: 'qcom,gpi-dma@900000' does not match '^dma-controller(@.*)?$'
from schema $id: http://devicetree.org/schemas/dma/qcom,gpi.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride.dtb: qcom,gpi-dma@a00000: $nodename:0: 'qcom,gpi-dma@a00000' does not match '^dma-controller(@.*)?$'
from schema $id: http://devicetree.org/schemas/dma/qcom,gpi.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dtb: qcom,gpi-dma@a00000: $nodename:0: 'qcom,gpi-dma@a00000' does not match '^dma-controller(@.*)?$'
from schema $id: http://devicetree.org/schemas/dma/qcom,gpi.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride.dtb: qcom,gpi-dma@b00000: $nodename:0: 'qcom,gpi-dma@b00000' does not match '^dma-controller(@.*)?$'
from schema $id: http://devicetree.org/schemas/dma/qcom,gpi.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dtb: qcom,gpi-dma@b00000: $nodename:0: 'qcom,gpi-dma@b00000' does not match '^dma-controller(@.*)?$'
from schema $id: http://devicetree.org/schemas/dma/qcom,gpi.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride.dtb: crypto@1dfa000: compatible: 'oneOf' conditional failed, one must be fixed:
['qcom,sa8775p-qce', 'qcom,qce'] is too long
['qcom,sa8775p-qce', 'qcom,qce'] is too short
'qcom,crypto-v5.1' was expected
'qcom,crypto-v5.4' was expected
'qcom,sa8775p-qce' is not one of ['qcom,ipq4019-qce', 'qcom,sm8150-qce']
'qcom,sa8775p-qce' is not one of ['qcom,ipq6018-qce', 'qcom,ipq8074-qce', 'qcom,ipq9574-qce', 'qcom,msm8996-qce', 'qcom,qcm2290-qce', 'qcom,sdm845-qce', 'qcom,sm6115-qce']
'qcom,ipq4019-qce' was expected
'qcom,sm8150-qce' was expected
from schema $id: http://devicetree.org/schemas/crypto/qcom-qce.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dtb: crypto@1dfa000: compatible: 'oneOf' conditional failed, one must be fixed:
['qcom,sa8775p-qce', 'qcom,qce'] is too long
['qcom,sa8775p-qce', 'qcom,qce'] is too short
'qcom,crypto-v5.1' was expected
'qcom,crypto-v5.4' was expected
'qcom,sa8775p-qce' is not one of ['qcom,ipq4019-qce', 'qcom,sm8150-qce']
'qcom,sa8775p-qce' is not one of ['qcom,ipq6018-qce', 'qcom,ipq8074-qce', 'qcom,ipq9574-qce', 'qcom,msm8996-qce', 'qcom,qcm2290-qce', 'qcom,sdm845-qce', 'qcom,sm6115-qce']
'qcom,ipq4019-qce' was expected
'qcom,sm8150-qce' was expected
from schema $id: http://devicetree.org/schemas/crypto/qcom-qce.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride.dtb: rsc@18200000: 'power-domains' is a required property
from schema $id: http://devicetree.org/schemas/soc/qcom/qcom,rpmh-rsc.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dtb: rsc@18200000: 'power-domains' is a required property
from schema $id: http://devicetree.org/schemas/soc/qcom/qcom,rpmh-rsc.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride.dtb: ethernet@23000000: tx-queues-config: 'snps,tx-sched-sp' does not match any of the regexes: '^queue[0-9]$', 'pinctrl-[0-9]+'
from schema $id: http://devicetree.org/schemas/net/qcom,ethqos.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride.dtb: ethernet@23000000: Unevaluated properties are not allowed ('interconnect-names', 'interconnects', 'phy-handle', 'phy-mode', 'power-domains', 'rx-fifo-depth', 'rx-queues-config', 'snps,mtl-rx-config', 'snps,mtl-tx-config', 'snps,pbl', 'snps,ps-speed', 'snps,tso', 'tx-fifo-depth', 'tx-queues-config' were unexpected)
from schema $id: http://devicetree.org/schemas/net/qcom,ethqos.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dtb: ethernet@23000000: tx-queues-config: 'snps,tx-sched-sp' does not match any of the regexes: '^queue[0-9]$', 'pinctrl-[0-9]+'
from schema $id: http://devicetree.org/schemas/net/qcom,ethqos.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dtb: ethernet@23000000: Unevaluated properties are not allowed ('interconnect-names', 'interconnects', 'phy-handle', 'phy-mode', 'power-domains', 'rx-fifo-depth', 'rx-queues-config', 'snps,mtl-rx-config', 'snps,mtl-tx-config', 'snps,pbl', 'snps,ps-speed', 'snps,tso', 'tx-fifo-depth', 'tx-queues-config' were unexpected)
from schema $id: http://devicetree.org/schemas/net/qcom,ethqos.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride.dtb: ethernet@23040000: tx-queues-config: 'snps,tx-sched-sp' does not match any of the regexes: '^queue[0-9]$', 'pinctrl-[0-9]+'
from schema $id: http://devicetree.org/schemas/net/qcom,ethqos.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride.dtb: ethernet@23040000: Unevaluated properties are not allowed ('interconnect-names', 'interconnects', 'mdio', 'phy-handle', 'phy-mode', 'power-domains', 'rx-fifo-depth', 'rx-queues-config', 'snps,mtl-rx-config', 'snps,mtl-tx-config', 'snps,pbl', 'snps,ps-speed', 'snps,tso', 'tx-fifo-depth', 'tx-queues-config' were unexpected)
from schema $id: http://devicetree.org/schemas/net/qcom,ethqos.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dtb: ethernet@23040000: tx-queues-config: 'snps,tx-sched-sp' does not match any of the regexes: '^queue[0-9]$', 'pinctrl-[0-9]+'
from schema $id: http://devicetree.org/schemas/net/qcom,ethqos.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dtb: ethernet@23040000: Unevaluated properties are not allowed ('interconnect-names', 'interconnects', 'mdio', 'phy-handle', 'phy-mode', 'power-domains', 'rx-fifo-depth', 'rx-queues-config', 'snps,mtl-rx-config', 'snps,mtl-tx-config', 'snps,pbl', 'snps,ps-speed', 'snps,tso', 'tx-fifo-depth', 'tx-queues-config' were unexpected)
from schema $id: http://devicetree.org/schemas/net/qcom,ethqos.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride.dtb: wcn6855-pmu: 'vddpmumx-supply' is a required property
from schema $id: http://devicetree.org/schemas/regulator/qcom,qca6390-pmu.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride.dtb: wcn6855-pmu: 'vddpmucx-supply' is a required property
from schema $id: http://devicetree.org/schemas/regulator/qcom,qca6390-pmu.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dtb: wcn6855-pmu: 'vddpmumx-supply' is a required property
from schema $id: http://devicetree.org/schemas/regulator/qcom,qca6390-pmu.yaml#
arch/arm64/boot/dts/qcom/qcs9100-ride-r3.dtb: wcn6855-pmu: 'vddpmucx-supply' is a required property
from schema $id: http://devicetree.org/schemas/regulator/qcom,qca6390-pmu.yaml#
© 2016 - 2024 Red Hat, Inc.