The recent conversion of the common MTD properties to YAML now mandates
a particular node name for SPI flash devices.
Reported-by: Rob Herring <[email protected]>
Signed-off-by: Michael Walle <[email protected]>
---
Documentation/devicetree/bindings/spi/spi-mux.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/spi/spi-mux.yaml b/Documentation/devicetree/bindings/spi/spi-mux.yaml
index d09c6355e22d..51c7622dc20b 100644
--- a/Documentation/devicetree/bindings/spi/spi-mux.yaml
+++ b/Documentation/devicetree/bindings/spi/spi-mux.yaml
@@ -72,7 +72,7 @@ examples:
mux-controls = <&mux>;
- spi-flash@0 {
+ flash@0 {
compatible = "jedec,spi-nor";
reg = <0>;
spi-max-frequency = <40000000>;
--
2.20.1
On Mon, May 17, 2021 at 10:39 AM Michael Walle <[email protected]> wrote:
>
> The recent conversion of the common MTD properties to YAML now mandates
> a particular node name for SPI flash devices.
>
> Reported-by: Rob Herring <[email protected]>
> Signed-off-by: Michael Walle <[email protected]>
> ---
> Documentation/devicetree/bindings/spi/spi-mux.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks for the quick fix.
Acked-by: Rob Herring <[email protected]>
On Mon, 17 May 2021 17:39:46 +0200, Michael Walle wrote:
> The recent conversion of the common MTD properties to YAML now mandates
> a particular node name for SPI flash devices.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] dt-bindings: spi: spi-mux: rename flash node
commit: 0b07154f066ab2c087c342b372be5771145bdc60
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