[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bc4c395d-4e21-1d15-96be-00a5cad1d6f7@linaro.org>
Date: Wed, 11 May 2022 18:00:09 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Nicolas Frattaroli <frattaroli.nicolas@...il.com>,
Ezequiel Garcia <ezequiel@...guardiasur.com.ar>,
Philipp Zabel <p.zabel@...gutronix.de>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Heiko Stuebner <heiko@...ech.de>
Cc: Ezequiel Garcia <ezequiel@...labora.com>,
linux-media@...r.kernel.org, linux-rockchip@...ts.infradead.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: media: rockchip-vpu: Add RK3568 VEPU
compatible
On 11/05/2022 17:53, Nicolas Frattaroli wrote:
> The RK3568 and RK3566 have a Hantro VPU node solely dedicated to
> encoding. This patch adds a compatible for it, and also allows
> the bindings to only come with a vepu interrupt.
>
> Signed-off-by: Nicolas Frattaroli <frattaroli.nicolas@...il.com>
> ---
> .../devicetree/bindings/media/rockchip-vpu.yaml | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/media/rockchip-vpu.yaml b/Documentation/devicetree/bindings/media/rockchip-vpu.yaml
> index bacb60a34989..965ca80b5cea 100644
> --- a/Documentation/devicetree/bindings/media/rockchip-vpu.yaml
> +++ b/Documentation/devicetree/bindings/media/rockchip-vpu.yaml
> @@ -22,6 +22,7 @@ properties:
> - rockchip,rk3288-vpu
> - rockchip,rk3328-vpu
> - rockchip,rk3399-vpu
> + - rockchip,rk3568-vepu
> - rockchip,px30-vpu
> - items:
> - const: rockchip,rk3188-vpu
> @@ -39,7 +40,9 @@ properties:
>
> interrupt-names:
> oneOf:
> - - const: vdpu
> + - enum:
> + - vdpu
> + - vepu
> - items:
> - const: vepu
> - const: vdpu
> @@ -76,6 +79,18 @@ required:
>
> additionalProperties: false
>
> +allOf:
> + # compatibles that end in -vepu should only have the vepu interrupt
> + - if:
> + properties:
> + compatible:
> + contains:
> + pattern: "^[a-zA-Z0-9\\-,_.]+\\-vepu$"
Why not listing the compatible how I asked? This is the common way of
handling allOf:if:then per variant.
https://lore.kernel.org/all/ea94f18d-3172-98bb-0892-a98236a08018@linaro.org/
Your patches do not apply on next, so the set might not have been tested
by Rob's bot.
Best regards,
Krzysztof
Powered by blists - more mailing lists