Am 09.08.22 um 17:55 schrieb Krzysztof Kozlowski: > On 09/08/2022 18:25, Frieder Schrempf wrote: >> From: Frieder Schrempf <frieder.schrempf@xxxxxxxxxx> >> >> This updates the bindings in order to simplify the devicetree >> structure and to add names for the boards that follow the latest >> convention used by Kontron marketing. >> >> Signed-off-by: Frieder Schrempf <frieder.schrempf@xxxxxxxxxx> >> --- >> .../devicetree/bindings/arm/fsl.yaml | 31 +++++++------------ >> 1 file changed, 12 insertions(+), 19 deletions(-) >> >> diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml b/Documentation/devicetree/bindings/arm/fsl.yaml >> index ef524378d449..7c4c27d553ec 100644 >> --- a/Documentation/devicetree/bindings/arm/fsl.yaml >> +++ b/Documentation/devicetree/bindings/arm/fsl.yaml >> @@ -553,8 +553,7 @@ properties: >> - engicam,imx6ul-isiot # Engicam Is.IoT MX6UL eMMC/NAND Starter kit >> - fsl,imx6ul-14x14-evk # i.MX6 UltraLite 14x14 EVK Board >> - karo,imx6ul-tx6ul # Ka-Ro electronics TXUL-0010 Module >> - - kontron,imx6ul-n6310-som # Kontron N6310 SOM >> - - kontron,imx6ul-n6311-som # Kontron N6311 SOM >> + - kontron,imx6ul-n631x-som # Kontron SL i.MX6UL (N631X SOM) > > Although board-level compatibles are not that important, yet still they > follow the same rules as other DT bindings: no wildcards for compatibles. > > Therefore the change is not correct, in my opinion. Ok, I see your point. I will look for a way to get rid of the wildcard in the compatible. Either by keeping the old names and having some duplication in the devicetree files or by renaming the compatibles altogether, as the N6xxx notation is not used nowadays anyway.
