[PATCH 0/3] mips: lantiq: add British Telecom Home Hub 5A dts

[PATCH 0/3] mips: lantiq: add British Telecom Home Hub 5A dts

[Aleksander Jan Bajkowski]

This series adds a device tree and bindings for the BT Home Hub 5A router.
It is based on the Lantiq VRX268 SoC. It has 128 MB of RAM and 128 MB of
NAND memory. At the moment, only the peripherals necessary to run the
initramfs image have been added. The remaining peripherals will be added
later. Some of them do not have upstream drivers. This is one of the most
popular Lantiq-based routers within the OpenWRT community.

Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>

Aleksander Jan Bajkowski (3):
  dt-bindings: vendor-prefixes: add British Telecom
  mips: lantiq: add British Telecom Home Hub 5A dts
  dt-bindings: mips: lantiq: Add Lantiq platform binding

 .../devicetree/bindings/mips/lantiq/soc.yaml  |  60 ++++++++++
 .../devicetree/bindings/vendor-prefixes.yaml  |   2 +
 arch/mips/boot/dts/lantiq/Makefile            |   1 +
 arch/mips/boot/dts/lantiq/xrx200.dtsi         | 104 ++++++++++++++++++
 .../boot/dts/lantiq/xrx200_bt_homehub-v5a.dts |  17 +++
 arch/mips/lantiq/Kconfig                      |  10 ++
 6 files changed, 194 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/mips/lantiq/soc.yaml
 create mode 100644 arch/mips/boot/dts/lantiq/xrx200.dtsi
 create mode 100644 arch/mips/boot/dts/lantiq/xrx200_bt_homehub-v5a.dts

-- 
2.47.2

[PATCH 1/3] dt-bindings: vendor-prefixes: add British Telecom

[Aleksander Jan Bajkowski]

British Telecom is a telecommunications operator. It provides various
home routers popular among OpenWRT enthusiasts.
Link: https://www.bt.com/

Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
---
 Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
index 77160cd47f54..e91879137e43 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
+++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
@@ -243,6 +243,8 @@ patternProperties:
     description: Shanghai Broadmobi Communication Technology Co.,Ltd.
   "^bsh,.*":
     description: BSH Hausgeraete GmbH
+  "^bt,.*":
+    description: British Telecom
   "^bticino,.*":
     description: Bticino International
   "^buffalo,.*":
-- 
2.47.2

[PATCH 2/3] mips: lantiq: add British Telecom Home Hub 5A dts

[Aleksander Jan Bajkowski]

This patch adds minimal dts for BT Home Hub 5A. The provided dts
allows to boot the initramfs image. Nodes for other peripherals
inside the SoC will be added in the future.

Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
---
 arch/mips/boot/dts/lantiq/Makefile            |   1 +
 arch/mips/boot/dts/lantiq/xrx200.dtsi         | 104 ++++++++++++++++++
 .../boot/dts/lantiq/xrx200_bt_homehub-v5a.dts |  17 +++
 arch/mips/lantiq/Kconfig                      |  10 ++
 4 files changed, 132 insertions(+)
 create mode 100644 arch/mips/boot/dts/lantiq/xrx200.dtsi
 create mode 100644 arch/mips/boot/dts/lantiq/xrx200_bt_homehub-v5a.dts

diff --git a/arch/mips/boot/dts/lantiq/Makefile b/arch/mips/boot/dts/lantiq/Makefile
index d8531b4653c0..9b43a7518bdc 100644
--- a/arch/mips/boot/dts/lantiq/Makefile
+++ b/arch/mips/boot/dts/lantiq/Makefile
@@ -1,2 +1,3 @@
 # SPDX-License-Identifier: GPL-2.0
 dtb-$(CONFIG_DT_EASY50712)	+= danube_easy50712.dtb
+dtb-$(CONFIG_DT_HH5A)		+= xrx200_bt_homehub-v5a.dtb
diff --git a/arch/mips/boot/dts/lantiq/xrx200.dtsi b/arch/mips/boot/dts/lantiq/xrx200.dtsi
new file mode 100644
index 000000000000..7e7cb6264e6f
--- /dev/null
+++ b/arch/mips/boot/dts/lantiq/xrx200.dtsi
@@ -0,0 +1,104 @@
+// SPDX-License-Identifier: GPL-2.0-or-later OR BSD-2-Clause
+
+/dts-v1/;
+
+/ {
+	#address-cells = <1>;
+	#size-cells = <1>;
+	compatible = "lantiq,vr9";
+
+	aliases {
+		serial0 = &asc1;
+	};
+
+	chosen {
+		stdout-path = "serial0:115200n8";
+	};
+
+	cpus {
+		#address-cells = <1>;
+		#size-cells = <0>;
+
+		cpu@0 {
+			compatible = "mips,mips34Kc";
+			reg = <0>;
+		};
+	};
+
+	cpuintc: cpuintc {
+		compatible = "mti,cpu-interrupt-controller";
+
+		#address-cells = <0>;
+		#interrupt-cells = <1>;
+
+		interrupt-controller;
+	};
+
+	localbus@1f800000 {
+		#address-cells = <1>;
+		#size-cells = <1>;
+		compatible = "simple-bus";
+		reg = <0x1f800000 0x800000>;
+		ranges = <0x0 0x1f800000 0x7fffff>;
+
+		icu0: icu@80200 {
+			#interrupt-cells = <1>;
+			interrupt-controller;
+			interrupt-parent = <&cpuintc>;
+			interrupts = <2>, <3>, <4>, <5>, <6>;
+			compatible = "lantiq,icu";
+			reg = <0x80200 0xc8	/* icu0 */
+			       0x80300 0xc8>;	/* icu1 */
+		};
+	};
+
+	localbus@1f000000 {
+		#address-cells = <1>;
+		#size-cells = <1>;
+		compatible = "simple-bus";
+		reg = <0x1f000000 0x800000>;
+		ranges = <0x0 0x1f000000 0x7fffff>;
+
+		pmu@102000 {
+			compatible = "lantiq,pmu-xway";
+			reg = <0x102000 0x1000>;
+		};
+
+		cgu@103000 {
+			compatible = "lantiq,cgu-xway";
+			reg = <0x103000 0x1000>;
+		};
+
+		rcu0: rcu@203000 {
+			#address-cells = <1>;
+			#size-cells = <1>;
+			compatible = "lantiq,xrx200-rcu", "simple-mfd", "syscon";
+			reg = <0x203000 0x100>;
+			ranges = <0x0 0x203000 0x100>;
+			big-endian;
+		};
+	};
+
+	localbus@10000000 {
+		compatible = "lantiq,xrx200-fpi", "simple-bus";
+		ranges = <0x0 0x10000000 0xf000000>;
+		reg =	<0x1f400000 0x1000>,
+			<0x10000000 0xf000000>;
+		regmap = <&rcu0>;
+		offset-endianness = <0x4c>;
+		#address-cells = <1>;
+		#size-cells = <1>;
+
+		asc1: serial@e100c00 {
+			compatible = "lantiq,asc";
+			reg = <0xe100c00 0x400>;
+			interrupt-parent = <&icu0>;
+			interrupts = <112 113 114>;
+		};
+
+		ebu@e105300 {
+			compatible = "lantiq,ebu-xway";
+			reg = <0xe105300 0x100>;
+		};
+	};
+};
diff --git a/arch/mips/boot/dts/lantiq/xrx200_bt_homehub-v5a.dts b/arch/mips/boot/dts/lantiq/xrx200_bt_homehub-v5a.dts
new file mode 100644
index 000000000000..ce1aae34adc9
--- /dev/null
+++ b/arch/mips/boot/dts/lantiq/xrx200_bt_homehub-v5a.dts
@@ -0,0 +1,17 @@
+// SPDX-License-Identifier: GPL-2.0-or-later OR BSD-2-Clause
+
+#include "xrx200.dtsi"
+
+/ {
+	compatible = "bt,homehub-v5a", "lantiq,vr9";
+	model = "BT Home Hub 5A";
+
+	chosen {
+		bootargs = "console=ttyLTQ0,115200";
+	};
+
+	memory@0 {
+		device_type = "memory";
+		reg = <0x0 0x8000000>;
+	};
+};
diff --git a/arch/mips/lantiq/Kconfig b/arch/mips/lantiq/Kconfig
index 6c6802e482c9..3376ac595b8c 100644
--- a/arch/mips/lantiq/Kconfig
+++ b/arch/mips/lantiq/Kconfig
@@ -46,6 +46,16 @@ config DT_EASY50712
 	bool "Easy50712"
 	depends on SOC_XWAY
 	select BUILTIN_DTB
+
+config DT_HH5A
+	bool "BT Home Hub 5A"
+	depends on SOC_XWAY
+	select BUILTIN_DTB
+	help
+	  The BT Home Hub 5A is a device based on the VRX268 SoC. It has 128MB
+	  of memory and 128MB of NAND flash. This kernel needs only an appended
+	  initramfs to boot. It can be loaded through tftp and booted from
+	  memory in the bootloader.
 endchoice
 
 config PCI_LANTIQ
-- 
2.47.2

[PATCH 3/3] dt-bindings: mips: lantiq: Add Lantiq platform binding

[Aleksander Jan Bajkowski]

Document the top-level device tree binding for Lantiq MIPS-based SoCs

Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
---
 .../devicetree/bindings/mips/lantiq/soc.yaml  | 60 +++++++++++++++++++
 1 file changed, 60 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/mips/lantiq/soc.yaml

diff --git a/Documentation/devicetree/bindings/mips/lantiq/soc.yaml b/Documentation/devicetree/bindings/mips/lantiq/soc.yaml
new file mode 100644
index 000000000000..e1708cd9b07e
--- /dev/null
+++ b/Documentation/devicetree/bindings/mips/lantiq/soc.yaml
@@ -0,0 +1,60 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/mips/lantiq/soc.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Lantiq SoC based Platform
+
+maintainers:
+  - Aleksander Jan Bajkowski <olek2@wp.pl>
+
+description:
+  Devices with a Lantiq CPU shall have the following properties.
+
+properties:
+  $nodename:
+    const: "/"
+  compatible:
+    oneOf:
+      - description: Boards with Lantiq Amazon-SE SoC
+        items:
+          - const: lantiq,ase
+
+      - description: Boards with Lantiq Danube SoC
+        items:
+          - const: lantiq,danube
+
+      - description: Boards with Lantiq Falcon SoC
+        items:
+          - const: lantiq,falcon
+
+      - description: Boards with Lantiq Twinpass SoC
+        items:
+          - const: lantiq,twinpass
+
+      - description: Boards with Lantiq ARX100 SoC
+        items:
+          - const: lantiq,ar9
+
+      - description: Boards with Lantiq GRX100 SoC
+        items:
+          - const: lantiq,gr9
+
+      - description: Boards with Lantiq xRX200 SoC
+        items:
+          - enum:
+              - bt,homehub-v5a
+          - const: lantiq,vr9
+
+      - description: Boards with Lantiq xRX300 SoC
+        items:
+          - const: lantiq,ar10
+
+      - description: Boards with Lantiq xRX330 SoC
+        items:
+          - const: lantiq,grx390
+
+additionalProperties: true
+
+...
-- 
2.47.2

Re: [PATCH 3/3] dt-bindings: mips: lantiq: Add Lantiq platform binding

[Conor Dooley]

[-- Attachment #1: Type: text/plain, Size: 2538 bytes --]

On Wed, Aug 13, 2025 at 04:21:34PM +0200, Aleksander Jan Bajkowski wrote:
> Document the top-level device tree binding for Lantiq MIPS-based SoCs
> 
> Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
> ---
>  .../devicetree/bindings/mips/lantiq/soc.yaml  | 60 +++++++++++++++++++
>  1 file changed, 60 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/mips/lantiq/soc.yaml
> 
> diff --git a/Documentation/devicetree/bindings/mips/lantiq/soc.yaml b/Documentation/devicetree/bindings/mips/lantiq/soc.yaml
> new file mode 100644
> index 000000000000..e1708cd9b07e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mips/lantiq/soc.yaml
> @@ -0,0 +1,60 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mips/lantiq/soc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Lantiq SoC based Platform
> +
> +maintainers:
> +  - Aleksander Jan Bajkowski <olek2@wp.pl>
> +
> +description:
> +  Devices with a Lantiq CPU shall have the following properties.
> +
> +properties:
> +  $nodename:
> +    const: "/"
> +  compatible:
> +    oneOf:
> +      - description: Boards with Lantiq Amazon-SE SoC
> +        items:
> +          - const: lantiq,ase

Half these entries you have added say "boards" but there are no boards
in them at all. Where are the boards? Only the homehub entry appears to
be complete.


Cheers,
Conor.

> +
> +      - description: Boards with Lantiq Danube SoC
> +        items:
> +          - const: lantiq,danube
> +
> +      - description: Boards with Lantiq Falcon SoC
> +        items:
> +          - const: lantiq,falcon
> +
> +      - description: Boards with Lantiq Twinpass SoC
> +        items:
> +          - const: lantiq,twinpass
> +
> +      - description: Boards with Lantiq ARX100 SoC
> +        items:
> +          - const: lantiq,ar9
> +
> +      - description: Boards with Lantiq GRX100 SoC
> +        items:
> +          - const: lantiq,gr9
> +
> +      - description: Boards with Lantiq xRX200 SoC
> +        items:
> +          - enum:
> +              - bt,homehub-v5a
> +          - const: lantiq,vr9
> +
> +      - description: Boards with Lantiq xRX300 SoC
> +        items:
> +          - const: lantiq,ar10
> +
> +      - description: Boards with Lantiq xRX330 SoC
> +        items:
> +          - const: lantiq,grx390
> +
> +additionalProperties: true
> +
> +...
> -- 
> 2.47.2
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [PATCH 0/3] mips: lantiq: add British Telecom Home Hub 5A dts

[Conor Dooley]

[-- Attachment #1: Type: text/plain, Size: 850 bytes --]

On Wed, Aug 13, 2025 at 04:21:31PM +0200, Aleksander Jan Bajkowski wrote:
> This series adds a device tree and bindings for the BT Home Hub 5A router.
> It is based on the Lantiq VRX268 SoC. It has 128 MB of RAM and 128 MB of
> NAND memory. At the moment, only the peripherals necessary to run the
> initramfs image have been added. The remaining peripherals will be added
> later. Some of them do not have upstream drivers. This is one of the most
> popular Lantiq-based routers within the OpenWRT community.
> 
> Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
> 
> Aleksander Jan Bajkowski (3):
>   dt-bindings: vendor-prefixes: add British Telecom
>   mips: lantiq: add British Telecom Home Hub 5A dts
>   dt-bindings: mips: lantiq: Add Lantiq platform binding

This order is wrong, the bindings must come before the users.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [PATCH 1/3] dt-bindings: vendor-prefixes: add British Telecom

[Conor Dooley]

[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]

On Wed, Aug 13, 2025 at 04:21:32PM +0200, Aleksander Jan Bajkowski wrote:
> British Telecom is a telecommunications operator. It provides various
> home routers popular among OpenWRT enthusiasts.
> Link: https://www.bt.com/
> 
> Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>

The blank line should be before the Link, not between Link and signoff
FWIW.
Otherwise,
Acked-by: Conor Dooley <conor.dooley@microchip.com>

> ---
>  Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> index 77160cd47f54..e91879137e43 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -243,6 +243,8 @@ patternProperties:
>      description: Shanghai Broadmobi Communication Technology Co.,Ltd.
>    "^bsh,.*":
>      description: BSH Hausgeraete GmbH
> +  "^bt,.*":
> +    description: British Telecom
>    "^bticino,.*":
>      description: Bticino International
>    "^buffalo,.*":
> -- 
> 2.47.2
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [PATCH 3/3] dt-bindings: mips: lantiq: Add Lantiq platform binding

[Aleksander Jan Bajkowski]

Hi Conor,

On 8/13/25 18:56, Conor Dooley wrote:
> On Wed, Aug 13, 2025 at 04:21:34PM +0200, Aleksander Jan Bajkowski wrote:
>> Document the top-level device tree binding for Lantiq MIPS-based SoCs
>>
>> Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
>> ---
>>   .../devicetree/bindings/mips/lantiq/soc.yaml  | 60 +++++++++++++++++++
>>   1 file changed, 60 insertions(+)
>>   create mode 100644 Documentation/devicetree/bindings/mips/lantiq/soc.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/mips/lantiq/soc.yaml b/Documentation/devicetree/bindings/mips/lantiq/soc.yaml
>> new file mode 100644
>> index 000000000000..e1708cd9b07e
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/mips/lantiq/soc.yaml
>> @@ -0,0 +1,60 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/mips/lantiq/soc.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Lantiq SoC based Platform
>> +
>> +maintainers:
>> +  - Aleksander Jan Bajkowski <olek2@wp.pl>
>> +
>> +description:
>> +  Devices with a Lantiq CPU shall have the following properties.
>> +
>> +properties:
>> +  $nodename:
>> +    const: "/"
>> +  compatible:
>> +    oneOf:
>> +      - description: Boards with Lantiq Amazon-SE SoC
>> +        items:
>> +          - const: lantiq,ase
> Half these entries you have added say "boards" but there are no boards
> in them at all. Where are the boards? Only the homehub entry appears to
> be complete.
>
>
> Cheers,
> Conor.


Right now, I'm just adding one router with the Lantiq xRX200 SoC. The 
binding
is prepared for adding more devices in the future. I'd like to add devices
based on the xRX100 and xRX330 SoCs too. Should I remove the other SoCs from
the list now?


Best regards,
Aleksander

Re: [PATCH 3/3] dt-bindings: mips: lantiq: Add Lantiq platform binding

[Conor Dooley]

[-- Attachment #1: Type: text/plain, Size: 2050 bytes --]

On Thu, Aug 14, 2025 at 06:31:42PM +0200, Aleksander Jan Bajkowski wrote:
> On 8/13/25 18:56, Conor Dooley wrote:
> > On Wed, Aug 13, 2025 at 04:21:34PM +0200, Aleksander Jan Bajkowski wrote:
> > > Document the top-level device tree binding for Lantiq MIPS-based SoCs
> > > 
> > > Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
> > > ---
> > >   .../devicetree/bindings/mips/lantiq/soc.yaml  | 60 +++++++++++++++++++
> > >   1 file changed, 60 insertions(+)
> > >   create mode 100644 Documentation/devicetree/bindings/mips/lantiq/soc.yaml
> > > 
> > > diff --git a/Documentation/devicetree/bindings/mips/lantiq/soc.yaml b/Documentation/devicetree/bindings/mips/lantiq/soc.yaml
> > > new file mode 100644
> > > index 000000000000..e1708cd9b07e
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/mips/lantiq/soc.yaml
> > > @@ -0,0 +1,60 @@
> > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > > +%YAML 1.2
> > > +---
> > > +$id: http://devicetree.org/schemas/mips/lantiq/soc.yaml#
> > > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > > +
> > > +title: Lantiq SoC based Platform
> > > +
> > > +maintainers:
> > > +  - Aleksander Jan Bajkowski <olek2@wp.pl>
> > > +
> > > +description:
> > > +  Devices with a Lantiq CPU shall have the following properties.
> > > +
> > > +properties:
> > > +  $nodename:
> > > +    const: "/"
> > > +  compatible:
> > > +    oneOf:
> > > +      - description: Boards with Lantiq Amazon-SE SoC
> > > +        items:
> > > +          - const: lantiq,ase
> > Half these entries you have added say "boards" but there are no boards
> > in them at all. Where are the boards? Only the homehub entry appears to
> > be complete.
> 
> Right now, I'm just adding one router with the Lantiq xRX200 SoC. The
> binding
> is prepared for adding more devices in the future. I'd like to add devices
> based on the xRX100 and xRX330 SoCs too. Should I remove the other SoCs from
> the list now?

Ye, I'd remove all of the unused SoCs. 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]