On 03/06/2022 09:45, Conor Dooley wrote: > spi-max-frequency property is supposed to be a per SPI peripheral device > property, not a SPI controller property, so remove it. > > Reported-by: Rob Herring <robh@xxxxxxxxxx> > Link: https://lore.kernel.org/lkml/20220526014141.2872567-1-robh@xxxxxxxxxx/ > Signed-off-by: Conor Dooley <conor.dooley@xxxxxxxxxxxxx> Feels weird saying this, but: Applied to dt-for-next of conor/linux.git > --- > Since v1: > - Rebase on changed filename JIC > --- > arch/riscv/boot/dts/microchip/mpfs.dtsi | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/arch/riscv/boot/dts/microchip/mpfs.dtsi b/arch/riscv/boot/dts/microchip/mpfs.dtsi > index 3095d08453a1..65a20c0b8af1 100644 > --- a/arch/riscv/boot/dts/microchip/mpfs.dtsi > +++ b/arch/riscv/boot/dts/microchip/mpfs.dtsi > @@ -299,7 +299,6 @@ spi1: spi@20109000 { > interrupt-parent = <&plic>; > interrupts = <55>; > clocks = <&clkcfg CLK_SPI1>; > - spi-max-frequency = <25000000>; > status = "disabled"; > }; > > @@ -311,7 +310,6 @@ qspi: spi@21000000 { > interrupt-parent = <&plic>; > interrupts = <85>; > clocks = <&clkcfg CLK_QSPI>; > - spi-max-frequency = <25000000>; > status = "disabled"; > }; >
