Skip to contentSkip to conversation

ARM: dts: intel: Drop pxa2xx

PATCH In review Rob Herring (Arm) 4 participants 8 messages Dec 12, 2025 – Jan 3

Subsystems (3)
lore
Share & tools
lore

Rob Herring (Arm)

author maintainer
#0 lore raw

PATCH 1/1 ARM: dts: intel: Drop pxa2xx

These .dtsi files are not included anywhere in the tree and can't be tested. They have not been touched since 2018 other than clean-ups.

---
 arch/arm/boot/dts/intel/pxa/pxa25x.dtsi       | 118 -----------
 arch/arm/boot/dts/intel/pxa/pxa27x.dtsi       | 188 ------------------
 arch/arm/boot/dts/marvell/armada-380.dtsi     | 148 --------------
 arch/arm64/boot/dts/marvell/armada-7020.dtsi  |  10 -
 arch/arm64/boot/dts/marvell/armada-8020.dtsi  |  20 --
 .../boot/dts/marvell/armada-ap806-dual.dtsi   |  60 ------
 .../dts/marvell/cn9130-db-comexpress.dtsi     |  96 ---------
 7 files changed, 640 deletions(-)
 delete mode 100644 arch/arm/boot/dts/intel/pxa/pxa25x.dtsi
 delete mode 100644 arch/arm/boot/dts/intel/pxa/pxa27x.dtsi
 delete mode 100644 arch/arm/boot/dts/marvell/armada-380.dtsi
 delete mode 100644 arch/arm64/boot/dts/marvell/armada-7020.dtsi
 delete mode 100644 arch/arm64/boot/dts/marvell/armada-8020.dtsi
 delete mode 100644 arch/arm64/boot/dts/marvell/armada-ap806-dual.dtsi
 delete mode 100644 arch/arm64/boot/dts/marvell/cn9130-db-comexpress.dtsi
arch/arm/boot/dts/intel/pxa/pxa25x.dtsi deleted +0 -118
deleted file mode 100644
index 5f8300e356ad..000000000000
@@ -1,118 +0,0 @@
-// SPDX-License-Identifier: GPL-2.0-or-later
-/*
- * Copyright (C) 2016 Robert Jarzmik <[email protected]>
- */
-#include "pxa2xx.dtsi"
-#include "dt-bindings/clock/pxa-clock.h"
-
-/ {
-	model = "Marvell PXA25x family SoC";
-	compatible = "marvell,pxa250";
-
-	clocks {
-	       /*
-		* The muxing of external clocks/internal dividers for osc* clock
-		* sources has been hidden under the carpet by now.
-		*/
-		#address-cells = <1>;
-		#size-cells = <1>;
-		ranges;
-
-		clks: pxa2xx_clks@41300004 {
-			compatible = "marvell,pxa250-core-clocks";
-			#clock-cells = <1>;
-			status = "okay";
-		};
-
-		/* timer oscillator */
-		clktimer: oscillator {
-			compatible = "fixed-clock";
-			#clock-cells = <0>;
-			clock-frequency  = <3686400>;
-			clock-output-names = "ostimer";
-		};
-	};
-
-	pxabus {
-		pdma: dma-controller@40000000 {
-			compatible = "marvell,pdma-1.0";
-			reg = <0x40000000 0x10000>;
-			interrupts = <25>;
-			#dma-cells = <2>;
-			/* For backwards compatibility: */
-			#dma-channels = <16>;
-			dma-channels = <16>;
-			#dma-requests = <40>;
-			dma-requests = <40>;
-			status = "okay";
-		};
-
-		pxairq: interrupt-controller@40d00000 {
-			marvell,intc-priority;
-			marvell,intc-nr-irqs = <32>;
-		};
-
-		pinctrl: pinctrl@40e00000 {
-			reg = <0x40e00054 0x20 0x40e0000c 0xc 0x40e0010c 4
-			       0x40f00020 0x10>;
-			compatible = "marvell,pxa25x-pinctrl";
-		};
-
-		gpio: gpio@40e00000 {
-			compatible = "intel,pxa25x-gpio";
-			gpio-ranges = <&pinctrl 0 0 84>;
-			clocks = <&clks CLK_NONE>;
-		};
-
-		pwm0: pwm@40b00000 {
-			compatible = "marvell,pxa250-pwm";
-			reg = <0x40b00000 0x10>;
-			#pwm-cells = <1>;
-			clocks = <&clks CLK_PWM0>;
-		};
-
-		pwm1: pwm@40b00010 {
-			compatible = "marvell,pxa250-pwm";
-			reg = <0x40b00010 0x10>;
-			#pwm-cells = <1>;
-			clocks = <&clks CLK_PWM1>;
-		};
-
-		rtc@40900000 {
-			clocks = <&clks CLK_OSC32k768>;
-		};
-	};
-
-	timer@40a00000 {
-		compatible = "marvell,pxa-timer";
-		reg = <0x40a00000 0x20>;
-		interrupts = <26>;
-		clocks = <&clktimer>;
-		status = "okay";
-	};
-
-	pxa250_opp_table: opp_table0 {
-		compatible = "operating-points-v2";
-
-		opp-99532800 {
-			opp-hz = /bits/ 64 <99532800>;
-			opp-microvolt = <1000000 950000 1650000>;
-			clock-latency-ns = <20>;
-		};
-		opp-199065600 {
-			opp-hz = /bits/ 64 <199065600>;
-			opp-microvolt = <1000000 950000 1650000>;
-			clock-latency-ns = <20>;
-		};
-		opp-298598400 {
-			opp-hz = /bits/ 64 <298598400>;
-			opp-microvolt = <1100000 1045000 1650000>;
-			clock-latency-ns = <20>;
-		};
-		opp-398131200 {
-			opp-hz = /bits/ 64 <398131200>;
-			opp-microvolt = <1300000 1235000 1650000>;
-			clock-latency-ns = <20>;
-		};
-	};
-};
arch/arm/boot/dts/intel/pxa/pxa27x.dtsi deleted +0 -188

188 lines not on this page · raw message

arch/arm/boot/dts/marvell/armada-380.dtsi deleted +0 -148

148 lines not on this page · raw message

arch/arm64/boot/dts/marvell/armada-7020.dtsi deleted +0 -10
deleted file mode 100644
index 570f901b4f4a..000000000000
@@ -1,10 +0,0 @@
-// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
-/*
- * Copyright (C) 2016 Marvell Technology Group Ltd.
- *
- * Device Tree file for the Armada 7020 SoC, made of an AP806 Dual and
- * one CP110.
- */
-
-#include "armada-ap806-dual.dtsi"
-#include "armada-70x0.dtsi"
arch/arm64/boot/dts/marvell/armada-8020.dtsi deleted +0 -20
deleted file mode 100644
index b6fc18876093..000000000000
@@ -1,20 +0,0 @@
-// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
-/*
- * Copyright (C) 2016 Marvell Technology Group Ltd.
- *
- * Device Tree file for the Armada 8020 SoC, made of an AP806 Dual and
- * two CP110.
- */
-
-#include "armada-ap806-dual.dtsi"
-#include "armada-80x0.dtsi"
-
-/* The RTC requires external oscillator. But on Aramda 80x0, the RTC clock
- * in CP master is not connected (by package) to the oscillator. So
- * disable it. However, the RTC clock in CP slave is connected to the
- * oscillator so this one is let enabled.
- */
-
-&cp0_rtc {
-	status = "disabled";
-};
arch/arm64/boot/dts/marvell/armada-ap806-dual.dtsi deleted +0 -60

60 lines not on this page · raw message

arch/arm64/boot/dts/marvell/cn9130-db-comexpress.dtsi deleted +0 -96

96 lines not on this page · raw message

Signature · 1 line
2.51.0
maintainer
#1 lore raw
Quoted 3 lines · Rob Herring (Arm)

These .dtsi files are not included anywhere in the tree and can't be tested. They have not been touched since 2018 other than clean-ups.

And yet, there are used by people using pxa2xx board with an DT support (like the mioa701 for which a board file was never merged).

If you remove pxa25x.dtsi and pxa27x.dtsi, you might as well remove all support for this architecture from the kernel, as these are the building blocks needed to make it work.

That might be what should be done, I'll let Arnd and Daniel comment on the future of PXA in the kernel.

Cheers.

--
Robert

Signature · 2 lines
Formal Signature
Emacs 25, org-mode 9, mu4e 1.0
#2 lore raw
Quoted 9 lines · Robert Jarzmik
Quoted 4 lines · Rob Herring (Arm)

These .dtsi files are not included anywhere in the tree and can't be tested. They have not been touched since 2018 other than clean-ups.

And yet, there are used by people using pxa2xx board with an DT support (like the mioa701 for which a board file was never merged).

Quoted 6 lines

If you remove pxa25x.dtsi and pxa27x.dtsi, you might as well remove all support for this architecture from the kernel, as these are the building blocks needed to make it work.

That might be what should be done, I'll let Arnd and Daniel comment on the future of PXA in the kernel.

I agree with Rob that at the very minimum, any dtsi files in the kernel should be build-tested along with the rest, so either we add some dts files using them soon, or we can remove pxa2xx (and maybe pxa3xx) completely.

I already plan to remove the remaining board files for both sa1100 and pxa soon, as nobody has picked up the task to do any further DT conversion after we removed the majority of the files back in 2022 and left only the ones that someone said they'd be interested in keeping.

Robert, let me know if you or someone else is able to spend some time on sending (warning-free) dts files for pxa2xx machines soon. If not, I'd plan to remove whatever is there along with the board files and drivers.

I also checked the pxa3xx Raumfeld devicetree support that Daniel added in linux-3.7. The manufacturer's firmware download page contains kernel images based on this work, using a 4.19 kernel but built in 2022. If we remove pxa2xx DT support, it would be good to find out if anyone still plans to use something newer on that hardware, which may happen because of CRA requirements.

Arnd

maintainer
#3 lore raw

Hi,

Quoted 14 lines · Arnd Bergmann
Quoted 13 lines · Robert Jarzmik
Quoted 4 lines · Rob Herring (Arm)

These .dtsi files are not included anywhere in the tree and can't be tested. They have not been touched since 2018 other than clean-ups.

And yet, there are used by people using pxa2xx board with an DT support (like the mioa701 for which a board file was never merged).

If you remove pxa25x.dtsi and pxa27x.dtsi, you might as well remove all support for this architecture from the kernel, as these are the building blocks needed to make it work.

Quoted 7 lines
Quoted 2 lines

That might be what should be done, I'll let Arnd and Daniel comment on the future of PXA in the kernel.

I agree with Rob that at the very minimum, any dtsi files in the kernel should be build-tested along with the rest, so either we add some dts files using them soon, or we can remove pxa2xx (and maybe pxa3xx) completely.

PXA3xx is in use by the Raumfeld boards, and I would really like to keep them around.

For PXA2xx I'm torn. I don't have the capacity and hardware to work on those, but I don't know how many users are out there with out-of-tree dts files.

Quoted 11 lines

I already plan to remove the remaining board files for both sa1100 and pxa soon, as nobody has picked up the task to do any further DT conversion after we removed the majority of the files back in 2022 and left only the ones that someone said they'd be interested in keeping.

Robert, let me know if you or someone else is able to spend some time on sending (warning-free) dts files for pxa2xx machines soon. If not, I'd plan to remove whatever is there along with the board files and drivers.

Quoted 7 lines

I also checked the pxa3xx Raumfeld devicetree support that Daniel added in linux-3.7. The manufacturer's firmware download page contains kernel images based on this work, using a 4.19 kernel but built in 2022. If we remove pxa2xx DT support, it would be good to find out if anyone still plans to use something newer on that hardware, which may happen because of CRA requirements.

As I said, I would like to not close the door on this one if possible.

Thanks,
Daniel

#4 lore raw
Quoted 18 lines · Daniel
Quoted 17 lines · Arnd Bergmann
Quoted 15 lines · Robert Jarzmik
Quoted 4 lines · Rob Herring (Arm)

These .dtsi files are not included anywhere in the tree and can't be tested. They have not been touched since 2018 other than clean-ups.

And yet, there are used by people using pxa2xx board with an DT support (like the mioa701 for which a board file was never merged).

If you remove pxa25x.dtsi and pxa27x.dtsi, you might as well remove all support for this architecture from the kernel, as these are the building blocks needed to make it work.

That might be what should be done, I'll let Arnd and Daniel comment on the future of PXA in the kernel.

Quoted 7 lines
Quoted 4 lines

I agree with Rob that at the very minimum, any dtsi files in the kernel should be build-tested along with the rest, so either we add some dts files using them soon, or we can remove pxa2xx (and maybe pxa3xx) completely.

PXA3xx is in use by the Raumfeld boards, and I would really like to keep them around.

Ok, no problem. If there are upstream users, we can always keep that.

Quoted 3 lines

For PXA2xx I'm torn. I don't have the capacity and hardware to work on those, but I don't know how many users are out there with out-of-tree dts files.

It's clear that nobody has done anything upstream for a while on pxa2xx, you both initially put a lot of work into it but it has been incomplete for almost a decade at this point.

I wouldn't even expect you to do any runtime testing, but if we want to keep it in mainline, it seems the minimum state we should get to is to complete the upstreaming to the degree that one machine can plausibly boot with a mainline that gets built by default, and not introduce new warnings in the process.

At the moment, an empty dts file that includes pxa25x.dtsi doesn't even build because there is no pwri2c node:

arch/arm/boot/dts/intel/pxa/pxa2xx.dtsi:36.10-43.4: ERROR (path_references): /aliases: Reference to non-existent node or label "pwri2c"

The pxa27x.dtsi file does build but produces a couple of 'dtbs_check' W=1 and W=2 warnings:

arch/arm/boot/dts/intel/pxa/pxa27x.dtsi:134.30-138.5: Warning (node_name_chars_strict): /clocks/pxa2xx_clks@41300004: Character '_' not recommended in node name arch/arm/boot/dts/intel/pxa/pxa27x.dtsi:149.31-187.4: Warning (node_name_chars_strict): /opp_table0: Character '_' not recommended in node name arch/arm/boot/dts/intel/pxa/pxa27x.dtsi:134.30-138.5: Warning (unit_address_vs_reg): /clocks/pxa2xx_clks@41300004: node has a unit name, but no reg or ranges property arch/arm/boot/dts/intel/pxa/pxa2xx.dtsi:154.33-160.5: Warning (simple_bus_reg): /pxabus/lcd-controller@40500000: simple-bus unit address format error, expected "44000000" arch/arm/boot/dts/intel/pxa/pxa27x.dtsi:29.29-33.5: Warning (simple_bus_reg): /pxabus/pinctrl@40e00000: simple-bus unit address format error, expected "40e00054" arch/arm/boot/dts/intel/pxa/pxa2xx.dtsi:67.23-94.5: Warning (unique_unit_address): /pxabus/gpio@40e00000: duplicate unit-address (also used in node /pxabus/pinctrl@40e00000) pxa270-minimal.dtb: /: failed to match any schema with compatible: ['marvell,pxa27x']
pxa270-minimal.dtb: cpus: '#address-cells' is a required property
from schema $id: http://devicetree.org/schemas/cpus.yaml#
pxa270-minimal.dtb: cpus: '#size-cells' is a required property
from schema $id: http://devicetree.org/schemas/cpus.yaml#
pxa270-minimal.dtb: /cpus/cpu: failed to match any schema with compatible: ['marvell,xscale']
pxa270-minimal.dtb: pxabus (simple-bus): $nodename:0: 'pxabus' does not match '^([a-z][a-z0-9\\-]+-bus|bus|localbus|soc|axi|ahb|apb)(@.+)?$'
from schema $id: http://devicetree.org/schemas/simple-bus.yaml#
pxa270-minimal.dtb: /pxabus/interrupt-controller@40d00000: failed to match any schema with compatible: ['marvell,pxa-intc']
pxa270-minimal.dtb: interrupt-controller@40d00000 (marvell,pxa-intc): interrupt-parent: True is not of type 'array'
from schema $id: http://devicetree.org/schemas/interrupts.yaml#
pxa270-minimal.dtb: /pxabus/mmc@41100000: failed to match any schema with compatible: ['marvell,pxa-mmc']
pxa270-minimal.dtb: rtc@40900000 (marvell,pxa-rtc): Unevaluated properties are not allowed ('clocks' was unexpected)
from schema $id: http://devicetree.org/schemas/rtc/marvell,pxa-rtc.yaml#
pxa270-minimal.dtb: /pxabus/lcd-controller@44000000: failed to match any schema with compatible: ['marvell,pxa2xx-lcdc']
pxa270-minimal.dtb: /pxabus/pinctrl@40e00000: failed to match any schema with compatible: ['marvell,pxa27x-pinctrl']
pxa270-minimal.dtb: /pxabus/usb@4c000000: failed to match any schema with compatible: ['marvell,pxa-ohci']
pxa270-minimal.dtb: pwm@40b00000 (marvell,pxa270-pwm): compatible: 'oneOf' conditional failed, one must be fixed:
['marvell,pxa270-pwm', 'marvell,pxa250-pwm'] is too long
'spacemit,k1-pwm' was expected
'marvell,pxa910-pwm' was expected
from schema $id: http://devicetree.org/schemas/pwm/marvell,pxa-pwm.yaml#
pxa270-minimal.dtb: pwm@40b00010 (marvell,pxa270-pwm): compatible: 'oneOf' conditional failed, one must be fixed:
['marvell,pxa270-pwm', 'marvell,pxa250-pwm'] is too long
'spacemit,k1-pwm' was expected
'marvell,pxa910-pwm' was expected
from schema $id: http://devicetree.org/schemas/pwm/marvell,pxa-pwm.yaml#
pxa270-minimal.dtb: pwm@40c00000 (marvell,pxa270-pwm): compatible: 'oneOf' conditional failed, one must be fixed:
['marvell,pxa270-pwm', 'marvell,pxa250-pwm'] is too long
'spacemit,k1-pwm' was expected
'marvell,pxa910-pwm' was expected
from schema $id: http://devicetree.org/schemas/pwm/marvell,pxa-pwm.yaml#
pxa270-minimal.dtb: pwm@40c00010 (marvell,pxa270-pwm): compatible: 'oneOf' conditional failed, one must be fixed:
['marvell,pxa270-pwm', 'marvell,pxa250-pwm'] is too long
'spacemit,k1-pwm' was expected
'marvell,pxa910-pwm' was expected
from schema $id: http://devicetree.org/schemas/pwm/marvell,pxa-pwm.yaml#
pxa270-minimal.dtb: /pxabus/udc@40600000: failed to match any schema with compatible: ['marvell,pxa270-udc']
pxa270-minimal.dtb: /pxabus/keypad@41500000: failed to match any schema with compatible: ['marvell,pxa27x-keypad']
pxa270-minimal.dtb: /pxabus/imaging@50000000: failed to match any schema with compatible: ['marvell,pxa270-qci']
pxa270-minimal.dtb: imaging@50000000 (marvell,pxa270-qci): '#clock-cells' is a dependency of 'clock-output-names'
from schema $id: http://devicetree.org/schemas/clock/clock.yaml#
pxa270-minimal.dtb: /clocks/pxa2xx_clks@41300004: failed to match any schema with compatible: ['marvell,pxa270-clocks']
pxa270-minimal.dtb: /timer@40a00000: failed to match any schema with compatible: ['marvell,pxa-timer']
pxa270-minimal.dtb: opp_table0 (operating-points-v2): $nodename:0: 'opp_table0' does not match '^opp-table(-[a-z0-9]+)?$'
from schema $id: http://devicetree.org/schemas/opp/opp-v2.yaml#
pxa270-minimal.dtb: opp_table0 (operating-points-v2): Unevaluated properties are not allowed ('opp-104000000', 'opp-156000000', 'opp-208000000', 'opp-312000000', 'opp-416000000', 'opp-520000000', 'opp-624000000' were unexpected)
from schema $id: http://devicetree.org/schemas/opp/opp-v2.yaml#

Most of these have an obvious fix and just need someone to care a little bit. The Raumfeld files have a similar set of warnings:

arch/arm/boot/dts/intel/pxa/pxa300-raumfeld-common.dtsi:17.9-20.4: Warning (unit_address_vs_reg): /memory: node has a reg or ranges property, but no unit name arch/arm/boot/dts/intel/pxa/pxa300-raumfeld-controller.dts:242.29-248.4: Warning (node_name_chars_strict): /pxabus/pinctrl@40e10000/charger_pins: Character '_' not recommended in node name arch/arm/boot/dts/intel/pxa/pxa300-raumfeld-controller.dts:250.37-256.4: Warning (node_name_chars_strict): /pxabus/pinctrl@40e10000/dock_detect_pins: Character '_' not recommended in node name arch/arm/boot/dts/intel/pxa/pxa300-raumfeld-speaker-one.dts:122.3-25: Warning (property_name_chars_strict): /pxabus/i2c@40301680/codec@1a:st,needs_esd_watchdog: Character '_' not recommended in property name pxa300-raumfeld-speaker-l.dtb: /: failed to match any schema with compatible: ['raumfeld,raumfeld-speaker-l-pxa303', 'marvell,pxa300']
pxa300-raumfeld-speaker-l.dtb: /: failed to match any schema with compatible: ['raumfeld,raumfeld-speaker-l-pxa303', 'marvell,pxa300']
pxa300-raumfeld-speaker-l.dtb: / (raumfeld,raumfeld-speaker-l-pxa303): memory: False schema does not allow {'device_type': ['memory'], 'reg': [[2684354560, 134217728]]}
from schema $id: http://devicetree.org/schemas/root-node.yaml#
pxa300-raumfeld-speaker-l.dtb: cpus: '#address-cells' is a required property
from schema $id: http://devicetree.org/schemas/cpus.yaml#
pxa300-raumfeld-speaker-l.dtb: cpus: '#size-cells' is a required property
from schema $id: http://devicetree.org/schemas/cpus.yaml#
pxa300-raumfeld-speaker-l.dtb: /cpus/cpu: failed to match any schema with compatible: ['marvell,xscale']
pxa300-raumfeld-speaker-l.dtb: pxabus (simple-bus): $nodename:0: 'pxabus' does not match '^([a-z][a-z0-9\\-]+-bus|bus|localbus|soc|axi|ahb|apb)(@.+)?$'
from schema $id: http://devicetree.org/schemas/simple-bus.yaml#
pxa300-raumfeld-speaker-l.dtb: /pxabus/interrupt-controller@40d00000: failed to match any schema with compatible: ['marvell,pxa-intc']
pxa300-raumfeld-speaker-l.dtb: interrupt-controller@40d00000 (marvell,pxa-intc): interrupt-parent: True is not of type 'array'
from schema $id: http://devicetree.org/schemas/interrupts.yaml#
pxa300-raumfeld-speaker-l.dtb: /pxabus/mmc@41100000: failed to match any schema with compatible: ['marvell,pxa-mmc']
pxa300-raumfeld-speaker-l.dtb: /pxabus/lcd-controller@44000000: failed to match any schema with compatible: ['marvell,pxa2xx-lcdc']
pxa300-raumfeld-speaker-l.dtb: /pxabus/i2c@40f500c0: failed to match any schema with compatible: ['mrvl,pwri2c']
pxa300-raumfeld-speaker-l.dtb: regulator@34 (maxim,max8660): $nodename:0: 'regulator@34' does not match 'pmic@[0-9a-f]{1,2}'
from schema $id: http://devicetree.org/schemas/regulator/max8660.yaml#
pxa300-raumfeld-speaker-l.dtb: regulator@34 (maxim,max8660): regulators:regulator-v3: Unevaluated properties are not allowed ('regulator-compatible' was unexpected)
from schema $id: http://devicetree.org/schemas/regulator/max8660.yaml#
pxa300-raumfeld-speaker-l.dtb: regulator@34 (maxim,max8660): regulators:regulator-v4: Unevaluated properties are not allowed ('regulator-compatible' was unexpected)
from schema $id: http://devicetree.org/schemas/regulator/max8660.yaml#
pxa300-raumfeld-speaker-l.dtb: regulator@34 (maxim,max8660): regulators:regulator-v5: Unevaluated properties are not allowed ('regulator-compatible' was unexpected)
from schema $id: http://devicetree.org/schemas/regulator/max8660.yaml#
pxa300-raumfeld-speaker-l.dtb: regulator@34 (maxim,max8660): regulators:regulator-v6: Unevaluated properties are not allowed ('regulator-compatible' was unexpected)
from schema $id: http://devicetree.org/schemas/regulator/max8660.yaml#
pxa300-raumfeld-speaker-l.dtb: regulator@34 (maxim,max8660): regulators:regulator-v7: Unevaluated properties are not allowed ('regulator-compatible' was unexpected)
from schema $id: http://devicetree.org/schemas/regulator/max8660.yaml#
pxa300-raumfeld-speaker-l.dtb: pinctrl@40e10000 (pinconf-single): 'led-pins-a', 'led-pins-b' do not match any of the regexes: '-pins(-[0-9]+)?$|-pin$', '^pinctrl-[0-9]+$'
from schema $id: http://devicetree.org/schemas/pinctrl/pinctrl-single.yaml#
pxa300-raumfeld-speaker-l.dtb: /pxabus/mmc@42000000: failed to match any schema with compatible: ['marvell,pxa-mmc']
pxa300-raumfeld-speaker-l.dtb: /pxabus/mmc@42500000: failed to match any schema with compatible: ['marvell,pxa-mmc']
pxa300-raumfeld-speaker-l.dtb: /pxabus/usb@4c000000: failed to match any schema with compatible: ['marvell,pxa-ohci']
pxa300-raumfeld-speaker-l.dtb: ssp@41000000 (mrvl,pxa3xx-ssp): $nodename:0: 'ssp@41000000' does not match '^spi(@.*|-([0-9]|[1-9][0-9]+))?$'
from schema $id: http://devicetree.org/schemas/spi/marvell,mmp2-ssp.yaml#
pxa300-raumfeld-speaker-l.dtb: ssp@41700000 (mrvl,pxa3xx-ssp): $nodename:0: 'ssp@41700000' does not match '^spi(@.*|-([0-9]|[1-9][0-9]+))?$'
from schema $id: http://devicetree.org/schemas/spi/marvell,mmp2-ssp.yaml#
pxa300-raumfeld-speaker-l.dtb: ssp@41900000 (mrvl,pxa3xx-ssp): $nodename:0: 'ssp@41900000' does not match '^spi(@.*|-([0-9]|[1-9][0-9]+))?$'
from schema $id: http://devicetree.org/schemas/spi/marvell,mmp2-ssp.yaml#
pxa300-raumfeld-speaker-l.dtb: ssp@41a00000 (mrvl,pxa3xx-ssp): $nodename:0: 'ssp@41a00000' does not match '^spi(@.*|-([0-9]|[1-9][0-9]+))?$'
from schema $id: http://devicetree.org/schemas/spi/marvell,mmp2-ssp.yaml#
pxa300-raumfeld-speaker-l.dtb: /pxabus/timer@40a00000: failed to match any schema with compatible: ['marvell,pxa-timer']
pxa300-raumfeld-speaker-l.dtb: /pxabus/display-controller@54000000: failed to match any schema with compatible: ['marvell,pxa300-gcu']
pxa300-raumfeld-speaker-l.dtb: /clocks/clocks: failed to match any schema with compatible: ['marvell,pxa300-clocks']
pxa300-raumfeld-speaker-l.dtb: /ssp-dai0: failed to match any schema with compatible: ['mrvl,pxa-ssp-dai']
pxa300-raumfeld-speaker-l.dtb: /ssp-dai1: failed to match any schema with compatible: ['mrvl,pxa-ssp-dai']
pxa300-raumfeld-speaker-l.dtb: spi (spi-gpio): gpio-miso: False schema does not allow [8, 98, 0]
from schema $id: http://devicetree.org/schemas/spi/spi-gpio.yaml#
pxa300-raumfeld-speaker-l.dtb: spi (spi-gpio): gpio-mosi: False schema does not allow [8, 97, 0]
from schema $id: http://devicetree.org/schemas/spi/spi-gpio.yaml#
pxa300-raumfeld-speaker-l.dtb: spi (spi-gpio): gpio-sck: False schema does not allow [8, 95, 0]
from schema $id: http://devicetree.org/schemas/spi/spi-gpio.yaml#
pxa300-raumfeld-speaker-l.dtb: spi (spi-gpio): 'sck-gpios' is a required property
from schema $id: http://devicetree.org/schemas/spi/spi-gpio.yaml#
pxa300-raumfeld-speaker-l.dtb: spi (spi-gpio): Unevaluated properties are not allowed ('gpio-miso', 'gpio-mosi', 'gpio-sck' were unexpected)
from schema $id: http://devicetree.org/schemas/spi/spi-gpio.yaml#
pxa300-raumfeld-speaker-l.dtb: dac@2 (ti,dac7512): 'vcc-supply' does not match any of the regexes: '^pinctrl-[0-9]+$'
from schema $id: http://devicetree.org/schemas/iio/dac/ti,dac7512.yaml#
pxa300-raumfeld-speaker-l.dtb: gpio-keys (gpio-keys): 'on-off', 'rescue-boot', 'setup' do not match any of the regexes: '^(button|event|key|switch|(button|event|key|switch)-[a-z0-9-]+|[a-z0-9-]+-(button|event|key|switch))$', '^pinctrl-[0-9]+$'
from schema $id: http://devicetree.org/schemas/input/gpio-keys.yaml#
pxa300-raumfeld-speaker-l.dtb: leds (gpio-leds): 'left', 'right' do not match any of the regexes: '(^led-[0-9a-f]$|led)', '^pinctrl-[0-9]+$'
from schema $id: http://devicetree.org/schemas/leds/leds-gpio.yaml#:%!

It would be good to at least address the warnings for nodes that have an existing yaml binding. Converting the remaining others or writing new ones takes more time and I wouldn't stress out about those (yet).

Arnd

maintainer
#5 lore raw
In reply to Arnd Bergmann
Quoted 4 lines · Arnd Bergmann

Robert, let me know if you or someone else is able to spend some time on sending (warning-free) dts files for pxa2xx machines soon. If not, I'd plan to remove whatever is there along with the board files and drivers.

Here is one attached, the previously mentioned mioa701 board dts file I've been using for years (the date of the patch should be funny enough). It was first submitted here :
https://lkml.org/lkml/2018/9/15/321

I'm not very sure pxa25x and pxa27x should survive though. Lately, the platform which I have left have 64MB of RAM, and cannot cope with recent binaries sizes. And to my best knowledge, pxa2xx architecture are not built anymore nor supported ...
The drivers might still be useful (the DMA, the SPI for intel CPU, ...).

Cheers.

--
Robert

-- >8 --
From a3cbbe846c4651d71edcf36d114f5e48f4455347 Mon Sep 17 00:00:00 2001
From: Robert Jarzmik <[email protected]>
Date: Mon, 1 Sep 2014 13:26:56 +0200
Subject: [PATCH] arm: dts: add mioa701 board description

Add device-tree description of the Mitac MIO A701 board.

---
arch/arm/boot/dts/intel/pxa/Makefile | 1 +
arch/arm/boot/dts/intel/pxa/mioa701.dts | 309 ++++++++++++++++++++++++

2 files changed, 310 insertions(+)

create mode 100644 arch/arm/boot/dts/intel/pxa/mioa701.dts

arch/arm/boot/dts/intel/pxa/Makefile +0 -0
index 24d5240f08e7..29670ec5861b 100644
@@ -6,3 +6,4 @@ dtb-$(CONFIG_ARCH_PXA) += \
	pxa300-raumfeld-speaker-m.dtb \
	pxa300-raumfeld-speaker-one.dtb \
	pxa300-raumfeld-speaker-s.dtb

+dtb-$(CONFIG_ARCH_PXA) += mioa701.dtb

arch/arm/boot/dts/intel/pxa/mioa701.dts new file +309 -0

309 lines not on this page · raw message

Signature · 1 line
2.50.1 (Apple Git-155)
#6 lore raw
Quoted 12 lines · Robert Jarzmik
Quoted 5 lines

Robert, let me know if you or someone else is able to spend some time on sending (warning-free) dts files for pxa2xx machines soon. If not, I'd plan to remove whatever is there along with the board files and drivers.

Here is one attached, the previously mentioned mioa701 board dts file
I've been using for years (the date of the patch should be funny enough). It was first submitted here :
https://lkml.org/lkml/2018/9/15/321

Quoted 4 lines

I'm not very sure pxa25x and pxa27x should survive though. Lately, the platform which I have left have 64MB of RAM, and cannot cope with recent binaries sizes. And to my best knowledge, pxa2xx architecture are not built anymore nor supported ...

Thanks for posting this one, that is helpful both for reference and in case anyone wants to keep using or bringing back pxa27x after we remove it.

My feeling is that if neither you nor Daniel are planning on actually using PXA2xx on future kernels, we're better off removing both PXA25x and PXA27x along with the board files and only keep PXA3xx around for Raumfeld.

Looking at when PXA2xx was used, I see a lot of handhelds from 2002 to 2007 but not much later, as smartphones then started moved to newer Marvell chips, or TI and Qualcomm alternatives. The last embedded PXA2xx boards were in 2010 (Colibri/Income, Voipac vpac270, Arcom Zeus), and were all discontinued by their manufacturers years ago, usually 10 years after the hardware introduction, and nobody complained when I removed the board files in 2022.

I had left the gumstix boards in the source tree at the time because it had more memory than the others and was supported by qemu. The upstream qemu releases now removed that as well.

If you or anyone else is still using PXA27x, we can always bring it back later, but I'd then put the burden on them to submit the dts file for inclusion without introducing DT warnings.

Quoted 2 lines

The drivers might still be useful (the DMA, the SPI for intel CPU, ...).

Right, most drivers have to stay as they are still used on newer chips. The ones that I think would become obsolete without pxa2xx are pinctrl, cpufreq, camera, mtd, udc and pcmcia. Especially the latter two have come up a few times during cleanups where they cause extra work from complexity that probably nobody is using any more.

arch/arm/boot/dts/intel/pxa/mioa701.dts line 244

Quoted 4 lines
arch/arm/boot/dts/intel/pxa/mioa701.dts new file +4 -0
+	docg3: flash@0 {
+		compatible = "m-systems,diskonchip-g3";
+		reg = <0x0 0x2000>;
+	};

This currently has no upstream users I can see, so removing pxa27x would probably mean we should remove that as well.

arch/arm/boot/dts/intel/pxa/mioa701.dts line 248

Quoted 3 lines
arch/arm/boot/dts/intel/pxa/mioa701.dts new file +3 -0
+	panel {
+		compatible = "toshiba,ltm0305a776";
+		lcd-type = "color-tft";

I don't see a driver that matches the compatible string, does this one actually work?

Arnd

maintainer
#7 lore raw
Quoted 4 lines · Arnd Bergmann

If you or anyone else is still using PXA27x, we can always bring it back later, but I'd then put the burden on them to submit the dts file for inclusion without introducing DT warnings.

Well not anymore, for RAM constraints as I said.
I can still fallback to an older kernel though if I feel like hacking.

Quoted 8 lines

arch/arm/boot/dts/intel/pxa/mioa701.dts line 244

Quoted 4 lines
arch/arm/boot/dts/intel/pxa/mioa701.dts new file +4 -0
+	docg3: flash@0 {
+		compatible = "m-systems,diskonchip-g3";
+		reg = <0x0 0x2000>;
+	};

This currently has no upstream users I can see, so removing pxa27x would probably mean we should remove that as well.

Yep, this driver was only used on the Mitac MIO A701 (my main board, pxa27x based).

Quoted 6 lines

arch/arm/boot/dts/intel/pxa/mioa701.dts line 248

Quoted 3 lines
arch/arm/boot/dts/intel/pxa/mioa701.dts new file +3 -0
+	panel {
+		compatible = "toshiba,ltm0305a776";
+		lcd-type = "color-tft";

I don't see a driver that matches the compatible string, does this one actually work?

Yes it does. The compatible string doesn't really matter. What is relevant in that part is the "timings" node, which is used by pxafb driver to setup its registers to control the LCD panel.

More generally, each and every part of this DT was working 3 years ago.

Cheers.

--
Robert