doc: remove u-boot,boot-led and u-boot,error-led from "binding"

We're aiming to reduce the amount of U-Boot-specific and out-of-spec
Device Tree additions.

Those two properties haven't been doing anything for a long time
already, except when read by board files manually. This is still the
case for STM32 boards but those will be migrated in the near future
according to their maintainer. In any case, let's not encourage people
to add either of these properties to new or existing Device Trees and
remove it from the bindings.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>

diff --git a/doc/device-tree-bindings/config.txt b/doc/device-tree-bindings/config.txt
index fffb69e75de0b0555a09d665e312cb148598fb0c..3756f57bf443329d906af07104b1b17b5af65d5a 100644 (file)
--- a/doc/device-tree-bindings/config.txt
+++ b/doc/device-tree-bindings/config.txt
@@ -26,11 +26,6 @@ bootdelay (int)
        images is being packed for testing or a user holds down a button, it may
        allow a delay, but disable it for production.
 
-u-boot,boot-led (string)
-u-boot,error-led (string)
-       This is used to specify the label for an LED to indicate an error and
-       a successful boot, on supported hardware.
-
 bootsecure (int)
        Indicates that U-Boot should use secure_boot_cmd() to run commands,
        rather than the normal CLI. This can be used in production images, to