Received: by 2002:a25:c205:0:0:0:0:0 with SMTP id s5csp797098ybf; Sat, 29 Feb 2020 16:30:10 -0800 (PST) X-Google-Smtp-Source: APXvYqzYgXEw7u5kYoYvMJpA88WnuSyhXYNQMIryci/bBZAqRfmURV8dR8nNtQd23VbaHM59V2F7 X-Received: by 2002:a9d:4c96:: with SMTP id m22mr2108743otf.21.1583022610364; Sat, 29 Feb 2020 16:30:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1583022610; cv=none; d=google.com; s=arc-20160816; b=UKL7wjWHDbm7vpJwIf+mMJMfhODRGcMPI22uTRX2HKqAjGI0PAriHA5coFEqzHGLaN y/ZfulcGBfkXPzE7gkCfNXTXi6lZ+5H/76Soe0yEpS6+O72/2ru0g3IDLaO4by+tVGHr ErN36TGtJqISxTZ5mzndRtNFhde/EVeAjEKbagBsl7GVZR/rUjTgezflZozRc9xrJHO6 NezcWBmW3VavWegbHtnycYjepGirJB9huqSJpmxtjH5TxEXmTnrqiDPZUbsXgYdMcbG/ E5s/1LwZhgnRBAylmRZb80EHZE2Bytrh1qvafb/zMAxqsxGQOPnUvehfDOd6gYCMv7qY 3Cag== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=BznQ8zGVHl5jKhxZOtySYB9SzQZYnGYHn0jQg+d3/Ys=; b=fBCXAoX6+RxsYtMOmiVzvY2rFH1FZqmdZWgd4wzaQ8OuyKaiDMvk1yb3bkdXg7IxTo Is9PPp6nqLfp71o1/rOsFhfAXvjyZ3tD71YGRo5GSqTziXsUrHuQ8Ej+2yGHUWHuJfQ6 Ys+BB6YIZo4Eb7LLcj1och0G97J0C7j0knqI8qmLTDMq0Jfbv0odGm0NmYzS0XUBMLzk h1oUPVxz07YoIZlyBEmiNU/zLyBPpTiUyiDrA+uxAOrm9hSbF3VViQz9EIK0f6YYsvs5 LP/kbV1ino4QTCnpv8mMevS9mnfJialyI37ZLbTpMQxn7gJXAuGvXbZwYAg4LenDrLFm n6Ww== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 110si4033355otj.303.2020.02.29.16.29.56; Sat, 29 Feb 2020 16:30:10 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727244AbgCAA3j (ORCPT + 99 others); Sat, 29 Feb 2020 19:29:39 -0500 Received: from gloria.sntech.de ([185.11.138.130]:55746 "EHLO gloria.sntech.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726786AbgCAA3j (ORCPT ); Sat, 29 Feb 2020 19:29:39 -0500 Received: from p508fcd9d.dip0.t-ipconnect.de ([80.143.205.157] helo=phil.localnet) by gloria.sntech.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1j8CU0-0004yv-LN; Sun, 01 Mar 2020 01:29:24 +0100 From: Heiko Stuebner To: Justin Swartz , Mauro Carvalho Chehab Cc: Jacob Chen , Ezequiel Garcia , Rob Herring , Mark Rutland , linux-media@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v4 1/3] [media] dt-bindings: Add binding for rk3228 rga Date: Sun, 01 Mar 2020 01:29:23 +0100 Message-ID: <7950264.35eqgo7tFu@phil> In-Reply-To: <4e66b3f029c56d7c7709d39ed15894b86f51fd37.1580768038.git.justin.swartz@risingedge.co.za> References: <4e66b3f029c56d7c7709d39ed15894b86f51fd37.1580768038.git.justin.swartz@risingedge.co.za> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Mauro, Am Montag, 3. Februar 2020, 23:40:15 CET schrieb Justin Swartz: > Indicate that the rk3228 rga is compatible with that of the rk3288. > > But if any rk3228-specific quirks are identified in future that > require handling logic that differs from what is provided for the > rk3288, then allow for the compatibility string "rockchip,rk3228-rga" > to be matched instead of "rockchip,rk3288-rga". > > Signed-off-by: Justin Swartz what is the process in the media-world for this dt-binding only patch? Do you want to apply it, or should I just also apply it with the following 2 dt-patches? There shouldn't be any conflicts with the media tree as this patch really only affects the rga binding document. Thanks Heiko > --- > Documentation/devicetree/bindings/media/rockchip-rga.txt | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/Documentation/devicetree/bindings/media/rockchip-rga.txt b/Documentation/devicetree/bindings/media/rockchip-rga.txt > index fd5276abf..c53a8e513 100644 > --- a/Documentation/devicetree/bindings/media/rockchip-rga.txt > +++ b/Documentation/devicetree/bindings/media/rockchip-rga.txt > @@ -6,8 +6,9 @@ BitBLT, alpha blending and image blur/sharpness. > > Required properties: > - compatible: value should be one of the following > - "rockchip,rk3288-rga"; > - "rockchip,rk3399-rga"; > + "rockchip,rk3228-rga", "rockchip,rk3288-rga": for Rockchip RK3228 > + "rockchip,rk3288-rga": for Rockchip RK3288 > + "rockchip,rk3399-rga": for Rockchip RK3399 > > - interrupts: RGA interrupt specifier. > >