On Thu, Mar 6, 2025 at 2:58 AM Krzysztof Kozlowski
<krzysztof.kozlowski@xxxxxxxxxx> wrote:
>
> Samsung Exynos SROM peripheral properties were moved from the device
> schema to separate "peripheral-props" schema for child node, but the
> device schema does not reference the new one.
>
> Reference the peripheral-props schema so the child nodes will be
> properly validated from the device schema.
>
> Fixes: 67bf606fcf18 ("dt-bindings: memory-controllers: samsung,exynos4210-srom: Split out child node properties")
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx>
>
> ---
>
> Fix for Rob's tree.
> ---
> .../devicetree/bindings/memory-controllers/exynos-srom.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/memory-controllers/exynos-srom.yaml b/Documentation/devicetree/bindings/memory-controllers/exynos-srom.yaml
> index 2267c5107d60..1578514ec58d 100644
> --- a/Documentation/devicetree/bindings/memory-controllers/exynos-srom.yaml
> +++ b/Documentation/devicetree/bindings/memory-controllers/exynos-srom.yaml
> @@ -38,6 +38,7 @@ properties:
> patternProperties:
> "^.*@[0-3],[a-f0-9]+$":
> type: object
> + $ref: mc-peripheral-props.yaml#
Why do we need this? Any child node should have a schema which needs
to include mc-peripheral-props.yaml if any properties from it can be
used.
Rob
