[PATCH] dt-bindings: leds: lacie,ns2-leds: Convert to DT schema

[PATCH] dt-bindings: leds: lacie,ns2-leds: Convert to DT schema

[Ninad Naik]

Convert lacie,ns2-leds to DT schema.

Signed-off-by: Ninad Naik <ninadnaik07@gmail.com>
---
 .../bindings/leds/lacie,ns2-leds.yaml         | 87 +++++++++++++++++++
 .../devicetree/bindings/leds/leds-ns2.txt     | 35 --------
 2 files changed, 87 insertions(+), 35 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/leds/lacie,ns2-leds.yaml
 delete mode 100644 Documentation/devicetree/bindings/leds/leds-ns2.txt

diff --git a/Documentation/devicetree/bindings/leds/lacie,ns2-leds.yaml b/Documentation/devicetree/bindings/leds/lacie,ns2-leds.yaml
new file mode 100644
index 000000000000..679a618906d8
--- /dev/null
+++ b/Documentation/devicetree/bindings/leds/lacie,ns2-leds.yaml
@@ -0,0 +1,87 @@
+# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/leds/lacie,ns2-leds.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Dual-GPIO LEDs found on Network Space v2 (and parents)
+
+maintainers:
+  - Lee Jones <lee@kernel.org>
+  - Pavel Machek <pavel@kernel.org>
+
+description: |
+  The Network Space v2 dual-GPIO LED is wired to a CPLD. Three different LED
+  modes are available: off, on and SATA activity blinking. The LED modes are
+  controlled through two GPIOs (command and slow): each combination of values
+  for the command/slow GPIOs corresponds to a LED mode.
+
+properties:
+  compatible:
+    const: lacie,ns2-leds
+
+patternProperties:
+  "^led(-[0-9a-z]+)?$":
+    type: object
+    $ref: common.yaml#
+    unevaluatedProperties: false
+
+    description:
+      Each child node represents a single LED
+
+    properties:
+      cmd-gpio:
+        maxItems: 1
+        description:
+          GPIO connected to the command LED output
+
+      slow-gpio:
+        maxItems: 1
+        description:
+          GPIO connected to the slow LED output
+
+      modes-map:
+        $ref: /schemas/types.yaml#/definitions/uint32-matrix
+        description:
+          A mapping between LED modes (off, on or SATA activity blinking) and
+          the corresponding cmd-gpio/slow-gpio values. All the GPIO values
+          combinations should be given in order to avoid having an unknown
+          mode at driver probe time.
+
+        items:
+          items:
+            - description: LED mode
+              enum: [0, 1, 2]
+            - description: Command GPIO level
+              enum: [0, 1]
+            - description: Slow GPIO level
+              enum: [0, 1]
+
+    required:
+      - cmd-gpio
+      - slow-gpio
+      - modes-map
+
+required:
+  - compatible
+
+additionalProperties: false
+
+examples:
+  - |
+    #include <dt-bindings/leds/leds-ns2.h>
+
+    led-controller {
+        compatible = "lacie,ns2-leds";
+
+        led-0 {
+            label = "ns2:blue:sata";
+            slow-gpio = <&gpio0 29 0>;
+            cmd-gpio = <&gpio0 30 0>;
+            modes-map = <NS_V2_LED_OFF  0 1
+                         NS_V2_LED_ON   1 0
+                         NS_V2_LED_ON   0 0
+                         NS_V2_LED_SATA 1 1>;
+        };
+    };
+...
diff --git a/Documentation/devicetree/bindings/leds/leds-ns2.txt b/Documentation/devicetree/bindings/leds/leds-ns2.txt
deleted file mode 100644
index 9f81258a5b6e..000000000000
--- a/Documentation/devicetree/bindings/leds/leds-ns2.txt
+++ /dev/null
@@ -1,35 +0,0 @@
-Binding for dual-GPIO LED found on Network Space v2 (and parents).
-
-Required properties:
-- compatible: "lacie,ns2-leds".
-
-Each LED is represented as a sub-node of the ns2-leds device.
-
-Required sub-node properties:
-- cmd-gpio: Command LED GPIO. See OF device-tree GPIO specification.
-- slow-gpio: Slow LED GPIO. See OF device-tree GPIO specification.
-- modes-map: A mapping between LED modes (off, on or SATA activity blinking) and
-  the corresponding cmd-gpio/slow-gpio values. All the GPIO values combinations
-  should be given in order to avoid having an unknown mode at driver probe time.
-
-Optional sub-node properties:
-- label: Name for this LED. If omitted, the label is taken from the node name.
-- linux,default-trigger: Trigger assigned to the LED.
-
-Example:
-
-#include <dt-bindings/leds/leds-ns2.h>
-
-ns2-leds {
-	compatible = "lacie,ns2-leds";
-
-	blue-sata {
-		label = "ns2:blue:sata";
-		slow-gpio = <&gpio0 29 0>;
-		cmd-gpio = <&gpio0 30 0>;
-		modes-map = <NS_V2_LED_OFF  0 1
-			     NS_V2_LED_ON   1 0
-			     NS_V2_LED_ON   0 0
-			     NS_V2_LED_SATA 1 1>;
-	};
-};
-- 
2.54.0

Re: [PATCH] dt-bindings: leds: lacie,ns2-leds: Convert to DT schema

[sashiko-bot]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The schema conversion incorrectly restricts LED child node names to `^led(-[0-9a-z]+)?$`, which breaks `dtbs_check` validation for all existing upstream device trees using this binding.
--

commit 6c59295f22b17d02a2b26847db54458f820fa4f3
Author: Ninad Naik <ninadnaik07@gmail.com>

dt-bindings: leds: lacie,ns2-leds: Convert to DT schema

Convert lacie,ns2-leds to DT schema.

> diff --git a/Documentation/devicetree/bindings/leds/lacie,ns2-leds.yaml b/Documentation/devicetree/bindings/leds/lacie,ns2-leds.yaml
> new file mode 100644
> index 0000000000000..679a618906d80
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/leds/lacie,ns2-leds.yaml
> @@ -0,0 +1,87 @@
[ ... ]
> +properties:
> +  compatible:
> +    const: lacie,ns2-leds
> +
> +patternProperties:
> +  "^led(-[0-9a-z]+)?$":

[Severity: Low]
Will this restrictive regex cause existing device trees to fail dtbs_check?

The old text binding example used a child node named blue-sata, which does
not match this pattern. Since additionalProperties is set to false below,
nodes in existing device trees that don't start with led will be rejected
during validation.

Should this regex be relaxed to allow existing node names, or should those
device tree files be updated alongside this conversion?

> +    type: object
> +    $ref: common.yaml#
> +    unevaluatedProperties: false

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260701175330.1645927-1-ninadnaik07@gmail.com?part=1

Re: [PATCH] dt-bindings: leds: lacie,ns2-leds: Convert to DT schema

[Rob Herring]

On Wed, Jul 01, 2026 at 11:23:30PM +0530, Ninad Naik wrote:
> Convert lacie,ns2-leds to DT schema.
> 
> Signed-off-by: Ninad Naik <ninadnaik07@gmail.com>
> ---
>  .../bindings/leds/lacie,ns2-leds.yaml         | 87 +++++++++++++++++++
>  .../devicetree/bindings/leds/leds-ns2.txt     | 35 --------
>  2 files changed, 87 insertions(+), 35 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/leds/lacie,ns2-leds.yaml
>  delete mode 100644 Documentation/devicetree/bindings/leds/leds-ns2.txt
> 
> diff --git a/Documentation/devicetree/bindings/leds/lacie,ns2-leds.yaml b/Documentation/devicetree/bindings/leds/lacie,ns2-leds.yaml
> new file mode 100644
> index 000000000000..679a618906d8
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/leds/lacie,ns2-leds.yaml
> @@ -0,0 +1,87 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/leds/lacie,ns2-leds.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Dual-GPIO LEDs found on Network Space v2 (and parents)
> +
> +maintainers:
> +  - Lee Jones <lee@kernel.org>
> +  - Pavel Machek <pavel@kernel.org>

This should be someone with the h/w, not subsystem maintainers.

> +
> +description: |

Dont need '|'.

> +  The Network Space v2 dual-GPIO LED is wired to a CPLD. Three different LED
> +  modes are available: off, on and SATA activity blinking. The LED modes are
> +  controlled through two GPIOs (command and slow): each combination of values
> +  for the command/slow GPIOs corresponds to a LED mode.

Rest looks fine.

Rob

Re: [PATCH] dt-bindings: leds: lacie,ns2-leds: Convert to DT schema

[Rob Herring]

On Wed, Jul 01, 2026 at 06:05:52PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] The schema conversion incorrectly restricts LED child node names to `^led(-[0-9a-z]+)?$`, which breaks `dtbs_check` validation for all existing upstream device trees using this binding.
> --
> 
> commit 6c59295f22b17d02a2b26847db54458f820fa4f3
> Author: Ninad Naik <ninadnaik07@gmail.com>
> 
> dt-bindings: leds: lacie,ns2-leds: Convert to DT schema
> 
> Convert lacie,ns2-leds to DT schema.
> 
> > diff --git a/Documentation/devicetree/bindings/leds/lacie,ns2-leds.yaml b/Documentation/devicetree/bindings/leds/lacie,ns2-leds.yaml
> > new file mode 100644
> > index 0000000000000..679a618906d80
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/leds/lacie,ns2-leds.yaml
> > @@ -0,0 +1,87 @@
> [ ... ]
> > +properties:
> > +  compatible:
> > +    const: lacie,ns2-leds
> > +
> > +patternProperties:
> > +  "^led(-[0-9a-z]+)?$":
> 
> [Severity: Low]
> Will this restrictive regex cause existing device trees to fail dtbs_check?
> 
> The old text binding example used a child node named blue-sata, which does
> not match this pattern. Since additionalProperties is set to false below,
> nodes in existing device trees that don't start with led will be rejected
> during validation.
> 
> Should this regex be relaxed to allow existing node names, or should those
> device tree files be updated alongside this conversion?

While yes we prefer what you did, it's perhaps not worth changing these 
old .dts files to match the preference.

Rob

Re: [PATCH] dt-bindings: leds: lacie,ns2-leds: Convert to DT schema

[Ninad Naik]

On 16/07/26 11:09 pm, Rob Herring wrote:
> On Wed, Jul 01, 2026 at 06:05:52PM +0000,sashiko-bot@kernel.org wrote:
>> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
>> - [Low] The schema conversion incorrectly restricts LED child node names to `^led(-[0-9a-z]+)?$`, which breaks `dtbs_check` validation for all existing upstream device trees using this binding.
>> --
>>
>> commit 6c59295f22b17d02a2b26847db54458f820fa4f3
>> Author: Ninad Naik<ninadnaik07@gmail.com>
>>
>> dt-bindings: leds: lacie,ns2-leds: Convert to DT schema
>>
>> Convert lacie,ns2-leds to DT schema.
>>
>>> diff --git a/Documentation/devicetree/bindings/leds/lacie,ns2-leds.yaml b/Documentation/devicetree/bindings/leds/lacie,ns2-leds.yaml
>>> new file mode 100644
>>> index 0000000000000..679a618906d80
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/leds/lacie,ns2-leds.yaml
>>> @@ -0,0 +1,87 @@
>> [ ... ]
>>> +properties:
>>> +  compatible:
>>> +    const: lacie,ns2-leds
>>> +
>>> +patternProperties:
>>> +  "^led(-[0-9a-z]+)?$":
>> [Severity: Low]
>> Will this restrictive regex cause existing device trees to fail dtbs_check?
>>
>> The old text binding example used a child node named blue-sata, which does
>> not match this pattern. Since additionalProperties is set to false below,
>> nodes in existing device trees that don't start with led will be rejected
>> during validation.
>>
>> Should this regex be relaxed to allow existing node names, or should those
>> device tree files be updated alongside this conversion?
> While yes we prefer what you did, it's perhaps not worth changing these
> old .dts files to match the preference.
>
> Rob

I understand this. Should I relax the regex to allow any pattern so that 
the existing as well

as new DTS files could be properly validated?

Thanks,

Ninad Naik

Re: [PATCH] dt-bindings: leds: lacie,ns2-leds: Convert to DT schema

[Rob Herring]

On Sat, Jul 18, 2026 at 3:15 AM Ninad Naik <ninadnaik07@gmail.com> wrote:
>
>
> On 16/07/26 11:09 pm, Rob Herring wrote:
> > On Wed, Jul 01, 2026 at 06:05:52PM +0000,sashiko-bot@kernel.org wrote:
> >> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> >> - [Low] The schema conversion incorrectly restricts LED child node names to `^led(-[0-9a-z]+)?$`, which breaks `dtbs_check` validation for all existing upstream device trees using this binding.
> >> --
> >>
> >> commit 6c59295f22b17d02a2b26847db54458f820fa4f3
> >> Author: Ninad Naik<ninadnaik07@gmail.com>
> >>
> >> dt-bindings: leds: lacie,ns2-leds: Convert to DT schema
> >>
> >> Convert lacie,ns2-leds to DT schema.
> >>
> >>> diff --git a/Documentation/devicetree/bindings/leds/lacie,ns2-leds.yaml b/Documentation/devicetree/bindings/leds/lacie,ns2-leds.yaml
> >>> new file mode 100644
> >>> index 0000000000000..679a618906d80
> >>> --- /dev/null
> >>> +++ b/Documentation/devicetree/bindings/leds/lacie,ns2-leds.yaml
> >>> @@ -0,0 +1,87 @@
> >> [ ... ]
> >>> +properties:
> >>> +  compatible:
> >>> +    const: lacie,ns2-leds
> >>> +
> >>> +patternProperties:
> >>> +  "^led(-[0-9a-z]+)?$":
> >> [Severity: Low]
> >> Will this restrictive regex cause existing device trees to fail dtbs_check?
> >>
> >> The old text binding example used a child node named blue-sata, which does
> >> not match this pattern. Since additionalProperties is set to false below,
> >> nodes in existing device trees that don't start with led will be rejected
> >> during validation.
> >>
> >> Should this regex be relaxed to allow existing node names, or should those
> >> device tree files be updated alongside this conversion?
> > While yes we prefer what you did, it's perhaps not worth changing these
> > old .dts files to match the preference.
> >
> > Rob
>
> I understand this. Should I relax the regex to allow any pattern so that
> the existing as well
>
> as new DTS files could be properly validated?

I doubt there will be new DTS files here, so you could just list the
node names in use. Or to just allow anything, you can do:

additionalProperties:
  type: object
  ...

Re: [PATCH] dt-bindings: leds: lacie,ns2-leds: Convert to DT schema

[kernel test robot]

:::::: 
:::::: Manual check reason: "dtcheck: binding changes may go via different trees"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260701175330.1645927-1-ninadnaik07@gmail.com>
References: <20260701175330.1645927-1-ninadnaik07@gmail.com>
TO: Ninad Naik <ninadnaik07@gmail.com>
TO: lee@kernel.org
TO: pavel@kernel.org
TO: robh@kernel.org
TO: krzk+dt@kernel.org
TO: conor+dt@kernel.org
CC: linux-leds@vger.kernel.org
CC: devicetree@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: me@brighamcampbell.com
CC: linux-kernel-mentees@lists.linux.dev
CC: skhan@linuxfoundation.org
CC: Ninad Naik <ninadnaik07@gmail.com>

Hi Ninad,

kernel test robot noticed the following build warnings:

[auto build test WARNING on v7.2-rc6]
[also build test WARNING on linus/master]
[cannot apply to lee-leds/for-leds-next next-20260811]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Ninad-Naik/dt-bindings-leds-lacie-ns2-leds-Convert-to-DT-schema/20260810-032423
base:   v7.2-rc6
patch link:    https://lore.kernel.org/r/20260701175330.1645927-1-ninadnaik07%40gmail.com
patch subject: [PATCH] dt-bindings: leds: lacie,ns2-leds: Convert to DT schema
:::::: branch date: 3 days ago
:::::: commit date: 3 days ago
config: arm-randconfig-2051-20260811 (https://download.01.org/0day-ci/archive/20260812/202608121549.88E5f7bu-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 85c730242e741f79bf7ca543bdf496dfb89a7f22)
dtschema: 2026.7.dev1+g2203c1720
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260812/202608121549.88E5f7bu-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202608121549.88E5f7bu-lkp@intel.com/

dtcheck warnings: (new ones prefixed by >>)
   arch/arm/boot/dts/marvell/armada-370-seagate-nas-4bay.dtb: mvsdio@d4000 (marvell,orion-sdio): $nodename:0: 'mvsdio@d4000' does not match '^mmc(@.*)?$'
   	from schema $id: http://devicetree.org/schemas/mmc/marvell,orion-sdio.yaml
   arch/arm/boot/dts/marvell/armada-370-seagate-nas-4bay.dtb: /soc/internal-regs/system-controller@18200: failed to match any schema with compatible: ['marvell,armada-370-xp-system-controller']
   arch/arm/boot/dts/marvell/armada-370-seagate-nas-4bay.dtb: /soc/internal-regs/cpu-config@21000: failed to match any schema with compatible: ['marvell,armada-370-cpu-config']
   arch/arm/boot/dts/marvell/armada-370-seagate-nas-4bay.dtb: /soc/internal-regs/audio-controller@30000: failed to match any schema with compatible: ['marvell,armada370-audio']
   arch/arm/boot/dts/marvell/armada-370-seagate-nas-4bay.dtb: /soc/bootrom: failed to match any schema with compatible: ['marvell,bootrom']
   arch/arm/boot/dts/marvell/armada-370-seagate-nas-4bay.dtb: sa-sram (mmio-sram): 'reg-names' does not match any of the regexes: '^([a-z0-9]+-)*sram(-section)?@[a-f0-9]+$', '^pinctrl-[0-9]+$'
   	from schema $id: http://devicetree.org/schemas/sram/sram.yaml
   arch/arm/boot/dts/marvell/armada-370-seagate-nas-4bay.dtb: sa-sram (mmio-sram): $nodename:0: 'sa-sram' does not match '^sram(@.*)?'
   	from schema $id: http://devicetree.org/schemas/sram/sram.yaml
>> arch/arm/boot/dts/marvell/armada-370-seagate-nas-4bay.dtb: leds-ns2 (lacie,ns2-leds): 'white-sata2', 'white-sata3' do not match any of the regexes: '^led(-[0-9a-z]+)?$', '^pinctrl-[0-9]+$'
   	from schema $id: http://devicetree.org/schemas/leds/lacie,ns2-leds.yaml
--
   	from schema $id: http://devicetree.org/schemas/simple-bus.yaml
   arch/arm/boot/dts/marvell/kirkwood-d2net.dtb: regulators (simple-bus): $nodename:0: 'regulators' does not match '^([a-z][a-z0-9\\-]+-bus|bus|localbus|soc|axi|ahb|apb)(@.+)?$'
   	from schema $id: http://devicetree.org/schemas/simple-bus.yaml
   arch/arm/boot/dts/marvell/kirkwood-d2net.dtb: regulators (simple-bus): 'ranges' is a required property
   	from schema $id: http://devicetree.org/schemas/simple-bus.yaml
   arch/arm/boot/dts/marvell/kirkwood-d2net.dtb: regulators (simple-bus): 'pinctrl-0' is a dependency of 'pinctrl-names'
   	from schema $id: http://devicetree.org/schemas/pinctrl/pinctrl-consumer.yaml
   arch/arm/boot/dts/marvell/kirkwood-d2net.dtb: regulator@1 (regulator-fixed): Unevaluated properties are not allowed ('reg' was unexpected)
   	from schema $id: http://devicetree.org/schemas/regulator/fixed-regulator.yaml
   arch/arm/boot/dts/marvell/kirkwood-d2net.dtb: /netxbig-leds: failed to match any schema with compatible: ['lacie,netxbig-leds']
>> arch/arm/boot/dts/marvell/kirkwood-d2net.dtb: ns2-leds (lacie,ns2-leds): 'blue-sata' does not match any of the regexes: '^led(-[0-9a-z]+)?$', '^pinctrl-[0-9]+$'
   	from schema $id: http://devicetree.org/schemas/leds/lacie,ns2-leds.yaml
--
   arch/arm/boot/dts/marvell/kirkwood-is2.dtb: /ocp@f1000000/audio-controller@a0000: failed to match any schema with compatible: ['marvell,kirkwood-audio']
   arch/arm/boot/dts/marvell/kirkwood-is2.dtb: rtc@10300 (marvell,kirkwood-rtc): 'clocks' does not match any of the regexes: '^pinctrl-[0-9]+$'
   	from schema $id: http://devicetree.org/schemas/rtc/trivial-rtc.yaml
   arch/arm/boot/dts/marvell/kirkwood-is2.dtb: rtc@10300 (marvell,kirkwood-rtc): compatible:0: 'marvell,kirkwood-rtc' is not one of ['abracon,abb5zes3', 'abracon,abeoz9', 'aspeed,ast2400-rtc', 'aspeed,ast2500-rtc', 'aspeed,ast2600-rtc', 'aspeed,ast2700-rtc', 'cnxt,cx92755-rtc', 'dallas,ds1374', 'dallas,ds1672', 'dallas,ds3232', 'dallas,m41t00', 'dfrobot,sd2405al', 'emmicro,em3027', 'epson,rx8010', 'epson,rx8035', 'epson,rx8111', 'epson,rx8571', 'epson,rx8581', 'google,goldfish-rtc', 'marvell,orion-rtc', 'maxim,ds1742', 'maxim,mcp795', 'microcrystal,rv3029', 'microcrystal,rv8523', 'olpc,xo1-rtc', 'ricoh,r2025sd', 'ricoh,r2221tl', 'ricoh,rs5c372a', 'ricoh,rs5c372b', 'ricoh,rv5c386', 'ricoh,rv5c387a', 'sii,s35390a', 'st,spear600-rtc', 'via,vt8500-rtc', 'whwave,sd3078', 'xicor,x1205']
   	from schema $id: http://devicetree.org/schemas/rtc/trivial-rtc.yaml
   arch/arm/boot/dts/marvell/kirkwood-is2.dtb: rtc@10300 (marvell,kirkwood-rtc): compatible: ['marvell,kirkwood-rtc', 'marvell,orion-rtc'] is too long
   	from schema $id: http://devicetree.org/schemas/rtc/trivial-rtc.yaml
   arch/arm/boot/dts/marvell/kirkwood-is2.dtb: /ocp@f1000000/rtc@10300: failed to match any schema with compatible: ['marvell,kirkwood-rtc', 'marvell,orion-rtc']
   arch/arm/boot/dts/marvell/kirkwood-is2.dtb: mvsdio@90000 (marvell,orion-sdio): $nodename:0: 'mvsdio@90000' does not match '^mmc(@.*)?$'
   	from schema $id: http://devicetree.org/schemas/mmc/marvell,orion-sdio.yaml
>> arch/arm/boot/dts/marvell/kirkwood-is2.dtb: ns2-leds (lacie,ns2-leds): 'blue-sata' does not match any of the regexes: '^led(-[0-9a-z]+)?$', '^pinctrl-[0-9]+$'
   	from schema $id: http://devicetree.org/schemas/leds/lacie,ns2-leds.yaml
--
   arch/arm/boot/dts/marvell/kirkwood-ns2.dtb: /ocp@f1000000/audio-controller@a0000: failed to match any schema with compatible: ['marvell,kirkwood-audio']
   arch/arm/boot/dts/marvell/kirkwood-ns2.dtb: rtc@10300 (marvell,kirkwood-rtc): 'clocks' does not match any of the regexes: '^pinctrl-[0-9]+$'
   	from schema $id: http://devicetree.org/schemas/rtc/trivial-rtc.yaml
   arch/arm/boot/dts/marvell/kirkwood-ns2.dtb: rtc@10300 (marvell,kirkwood-rtc): compatible:0: 'marvell,kirkwood-rtc' is not one of ['abracon,abb5zes3', 'abracon,abeoz9', 'aspeed,ast2400-rtc', 'aspeed,ast2500-rtc', 'aspeed,ast2600-rtc', 'aspeed,ast2700-rtc', 'cnxt,cx92755-rtc', 'dallas,ds1374', 'dallas,ds1672', 'dallas,ds3232', 'dallas,m41t00', 'dfrobot,sd2405al', 'emmicro,em3027', 'epson,rx8010', 'epson,rx8035', 'epson,rx8111', 'epson,rx8571', 'epson,rx8581', 'google,goldfish-rtc', 'marvell,orion-rtc', 'maxim,ds1742', 'maxim,mcp795', 'microcrystal,rv3029', 'microcrystal,rv8523', 'olpc,xo1-rtc', 'ricoh,r2025sd', 'ricoh,r2221tl', 'ricoh,rs5c372a', 'ricoh,rs5c372b', 'ricoh,rv5c386', 'ricoh,rv5c387a', 'sii,s35390a', 'st,spear600-rtc', 'via,vt8500-rtc', 'whwave,sd3078', 'xicor,x1205']
   	from schema $id: http://devicetree.org/schemas/rtc/trivial-rtc.yaml
   arch/arm/boot/dts/marvell/kirkwood-ns2.dtb: rtc@10300 (marvell,kirkwood-rtc): compatible: ['marvell,kirkwood-rtc', 'marvell,orion-rtc'] is too long
   	from schema $id: http://devicetree.org/schemas/rtc/trivial-rtc.yaml
   arch/arm/boot/dts/marvell/kirkwood-ns2.dtb: /ocp@f1000000/rtc@10300: failed to match any schema with compatible: ['marvell,kirkwood-rtc', 'marvell,orion-rtc']
   arch/arm/boot/dts/marvell/kirkwood-ns2.dtb: mvsdio@90000 (marvell,orion-sdio): $nodename:0: 'mvsdio@90000' does not match '^mmc(@.*)?$'
   	from schema $id: http://devicetree.org/schemas/mmc/marvell,orion-sdio.yaml
>> arch/arm/boot/dts/marvell/kirkwood-ns2.dtb: ns2-leds (lacie,ns2-leds): 'blue-sata' does not match any of the regexes: '^led(-[0-9a-z]+)?$', '^pinctrl-[0-9]+$'
   	from schema $id: http://devicetree.org/schemas/leds/lacie,ns2-leds.yaml
--
   arch/arm/boot/dts/marvell/kirkwood-ns2max.dtb: /ocp@f1000000/audio-controller@a0000: failed to match any schema with compatible: ['marvell,kirkwood-audio']
   arch/arm/boot/dts/marvell/kirkwood-ns2max.dtb: rtc@10300 (marvell,kirkwood-rtc): 'clocks' does not match any of the regexes: '^pinctrl-[0-9]+$'
   	from schema $id: http://devicetree.org/schemas/rtc/trivial-rtc.yaml
   arch/arm/boot/dts/marvell/kirkwood-ns2max.dtb: rtc@10300 (marvell,kirkwood-rtc): compatible:0: 'marvell,kirkwood-rtc' is not one of ['abracon,abb5zes3', 'abracon,abeoz9', 'aspeed,ast2400-rtc', 'aspeed,ast2500-rtc', 'aspeed,ast2600-rtc', 'aspeed,ast2700-rtc', 'cnxt,cx92755-rtc', 'dallas,ds1374', 'dallas,ds1672', 'dallas,ds3232', 'dallas,m41t00', 'dfrobot,sd2405al', 'emmicro,em3027', 'epson,rx8010', 'epson,rx8035', 'epson,rx8111', 'epson,rx8571', 'epson,rx8581', 'google,goldfish-rtc', 'marvell,orion-rtc', 'maxim,ds1742', 'maxim,mcp795', 'microcrystal,rv3029', 'microcrystal,rv8523', 'olpc,xo1-rtc', 'ricoh,r2025sd', 'ricoh,r2221tl', 'ricoh,rs5c372a', 'ricoh,rs5c372b', 'ricoh,rv5c386', 'ricoh,rv5c387a', 'sii,s35390a', 'st,spear600-rtc', 'via,vt8500-rtc', 'whwave,sd3078', 'xicor,x1205']
   	from schema $id: http://devicetree.org/schemas/rtc/trivial-rtc.yaml
   arch/arm/boot/dts/marvell/kirkwood-ns2max.dtb: rtc@10300 (marvell,kirkwood-rtc): compatible: ['marvell,kirkwood-rtc', 'marvell,orion-rtc'] is too long
   	from schema $id: http://devicetree.org/schemas/rtc/trivial-rtc.yaml
   arch/arm/boot/dts/marvell/kirkwood-ns2max.dtb: /ocp@f1000000/rtc@10300: failed to match any schema with compatible: ['marvell,kirkwood-rtc', 'marvell,orion-rtc']
   arch/arm/boot/dts/marvell/kirkwood-ns2max.dtb: mvsdio@90000 (marvell,orion-sdio): $nodename:0: 'mvsdio@90000' does not match '^mmc(@.*)?$'
   	from schema $id: http://devicetree.org/schemas/mmc/marvell,orion-sdio.yaml
>> arch/arm/boot/dts/marvell/kirkwood-ns2max.dtb: ns2-leds (lacie,ns2-leds): 'blue-sata' does not match any of the regexes: '^led(-[0-9a-z]+)?$', '^pinctrl-[0-9]+$'
   	from schema $id: http://devicetree.org/schemas/leds/lacie,ns2-leds.yaml
--
   arch/arm/boot/dts/marvell/kirkwood-ns2mini.dtb: /ocp@f1000000/audio-controller@a0000: failed to match any schema with compatible: ['marvell,kirkwood-audio']
   arch/arm/boot/dts/marvell/kirkwood-ns2mini.dtb: rtc@10300 (marvell,kirkwood-rtc): 'clocks' does not match any of the regexes: '^pinctrl-[0-9]+$'
   	from schema $id: http://devicetree.org/schemas/rtc/trivial-rtc.yaml
   arch/arm/boot/dts/marvell/kirkwood-ns2mini.dtb: rtc@10300 (marvell,kirkwood-rtc): compatible:0: 'marvell,kirkwood-rtc' is not one of ['abracon,abb5zes3', 'abracon,abeoz9', 'aspeed,ast2400-rtc', 'aspeed,ast2500-rtc', 'aspeed,ast2600-rtc', 'aspeed,ast2700-rtc', 'cnxt,cx92755-rtc', 'dallas,ds1374', 'dallas,ds1672', 'dallas,ds3232', 'dallas,m41t00', 'dfrobot,sd2405al', 'emmicro,em3027', 'epson,rx8010', 'epson,rx8035', 'epson,rx8111', 'epson,rx8571', 'epson,rx8581', 'google,goldfish-rtc', 'marvell,orion-rtc', 'maxim,ds1742', 'maxim,mcp795', 'microcrystal,rv3029', 'microcrystal,rv8523', 'olpc,xo1-rtc', 'ricoh,r2025sd', 'ricoh,r2221tl', 'ricoh,rs5c372a', 'ricoh,rs5c372b', 'ricoh,rv5c386', 'ricoh,rv5c387a', 'sii,s35390a', 'st,spear600-rtc', 'via,vt8500-rtc', 'whwave,sd3078', 'xicor,x1205']
   	from schema $id: http://devicetree.org/schemas/rtc/trivial-rtc.yaml
   arch/arm/boot/dts/marvell/kirkwood-ns2mini.dtb: rtc@10300 (marvell,kirkwood-rtc): compatible: ['marvell,kirkwood-rtc', 'marvell,orion-rtc'] is too long
   	from schema $id: http://devicetree.org/schemas/rtc/trivial-rtc.yaml
   arch/arm/boot/dts/marvell/kirkwood-ns2mini.dtb: /ocp@f1000000/rtc@10300: failed to match any schema with compatible: ['marvell,kirkwood-rtc', 'marvell,orion-rtc']
   arch/arm/boot/dts/marvell/kirkwood-ns2mini.dtb: mvsdio@90000 (marvell,orion-sdio): $nodename:0: 'mvsdio@90000' does not match '^mmc(@.*)?$'
   	from schema $id: http://devicetree.org/schemas/mmc/marvell,orion-sdio.yaml
>> arch/arm/boot/dts/marvell/kirkwood-ns2mini.dtb: ns2-leds (lacie,ns2-leds): 'blue-sata' does not match any of the regexes: '^led(-[0-9a-z]+)?$', '^pinctrl-[0-9]+$'
   	from schema $id: http://devicetree.org/schemas/leds/lacie,ns2-leds.yaml

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki