Skip to contentSkip to conversation

spi: dt-bindings: nuvoton,ma35d1-qspi: Drop redundant SPI example

PATCH In review Chi-Wen Weng 2 participants 2 messages Oct 6 – Oct 7

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 spi: dt-bindings: nuvoton,ma35d1-qspi: Drop redundant SPI example

From: Chi-Wen Weng <[email protected]>

The SPI and QSPI controllers use the same Devicetree node structure. The additional SPI example only differs in property values and does not demonstrate any binding-specific behavior.

Drop the redundant SPI example and keep the existing QSPI example.

---
 .../bindings/spi/nuvoton,ma35d1-qspi.yaml     | 20 -------------------
 1 file changed, 20 deletions(-)
Documentation/devicetree/bindings/spi/nuvoton,ma35d1-qspi.yaml +0 -20
index 72f2e1e1219a..9ee61f8ac4d6 100644
@@ -75,24 +75,4 @@ examples:
         };
     };
 
-  - |
-    #include <dt-bindings/interrupt-controller/arm-gic.h>
-    #include <dt-bindings/clock/nuvoton,ma35d1-clk.h>
-    #include <dt-bindings/reset/nuvoton,ma35d1-reset.h>
-
-    soc {
-        #address-cells = <2>;
-        #size-cells = <2>;
-
-        spi@40600000 {
-            compatible = "nuvoton,ma35d1-spi";
-            reg = <0 0x40600000 0 0x10000>;
-            interrupts = <GIC_SPI 89 IRQ_TYPE_LEVEL_HIGH>;
-            clocks = <&clk SPI0_GATE>;
-            resets = <&sys MA35D1_RESET_SPI0>;
-
-            #address-cells = <1>;
-            #size-cells = <0>;
-        };
-    };
 ...

base-commit: 4825287f6d2346e9273f35a928d1ef40e68bc58b

Signature · 1 line
2.25.1
maintainer
#1 lore raw
Quoted 1 line · Chi-Wen Weng

spi: dt-bindings: nuvoton,ma35d1-qspi: Drop redundant SPI example

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-7.4

Thanks!

[1/1] spi: dt-bindings: nuvoton,ma35d1-qspi: Drop redundant SPI example

      https://git.kernel.org/broonie/spi/c/921ecc459d4f

All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying to this mail.

Thanks,
Mark