Skip to content

Commit f1595d5

Browse files
krzkConchuOD
authored andcommitted
arm64: dts: microchip: sparx5_pcb134: drop duplicated NOR flash
Since beginning the DTS extended the SPI0 in two places adding two SPI muxes, each with same SPI NOR flash. Both used exactly the same chip-selects, so this was clearly buggy code. Then in commit d0f482b ("arm64: dts: sparx5: Add the Sparx5 switch node") one SPI mux was removed, while keeping the SPI NOR flash node. This still leaves duplicated SPI nodes under same chip select 0, reported by dtc W=1 warnings: sparx5_pcb134_board.dtsi:277.10-281.4: Warning (unique_unit_address_if_enabled): /axi@600000000/spi@600104000/flash@0: duplicate unit-address (also used in node /axi@600000000/spi@600104000/spi@0) Steen Hegelund confirmed that in fact there is a SPI mux, thus remove the duplicated node without the mux. Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org> Tested-by: Steen Hegelund <Steen.Hegelund@microchip.com> Reviewed-by: Steen Hegelund <Steen.Hegelund@microchip.com> Reviewed-by: Steen Hegelund <Steen.Hegelund@microchip.com> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
1 parent 5945df4 commit f1595d5

1 file changed

Lines changed: 0 additions & 9 deletions

File tree

arch/arm64/boot/dts/microchip/sparx5_pcb134_board.dtsi

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -272,15 +272,6 @@
272272
};
273273
};
274274

275-
&spi0 {
276-
status = "okay";
277-
flash@0 {
278-
compatible = "jedec,spi-nor";
279-
spi-max-frequency = <8000000>;
280-
reg = <0>;
281-
};
282-
};
283-
284275
&spi0 {
285276
status = "okay";
286277
spi@0 {

0 commit comments

Comments
 (0)