[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=UpZAjrWkQ7qj5Wo2tf2wkg5Q-34Sun0MOtYLBAwY731Q@mail.gmail.com>
Date: Thu, 20 Jun 2019 09:43:33 -0700
From: Doug Anderson <dianders@...omium.org>
To: Ezequiel Garcia <ezequiel@...labora.com>
Cc: dri-devel <dri-devel@...ts.freedesktop.org>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
Heiko Stübner <heiko@...ech.de>,
Sandy Huang <hjc@...k-chips.com>, kernel@...labora.com,
Sean Paul <seanpaul@...omium.org>,
Boris Brezillon <boris.brezillon@...labora.com>,
Jacopo Mondi <jacopo@...ndi.org>,
Ilia Mirkin <imirkin@...m.mit.edu>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3] dt-bindings: display: rockchip: document VOP gamma
LUT address
Hi,
On Tue, Jun 18, 2019 at 2:43 PM Ezequiel Garcia <ezequiel@...labora.com> wrote:
>
> Add the register specifier description for an
> optional gamma LUT address.
>
> Signed-off-by: Ezequiel Garcia <ezequiel@...labora.com>
> ---
> .../bindings/display/rockchip/rockchip-vop.txt | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/display/rockchip/rockchip-vop.txt b/Documentation/devicetree/bindings/display/rockchip/rockchip-vop.txt
> index 4f58c5a2d195..97ad78cc7e03 100644
> --- a/Documentation/devicetree/bindings/display/rockchip/rockchip-vop.txt
> +++ b/Documentation/devicetree/bindings/display/rockchip/rockchip-vop.txt
> @@ -20,6 +20,13 @@ Required properties:
> "rockchip,rk3228-vop";
> "rockchip,rk3328-vop";
>
> +- reg: Must contain one entry corresponding to the base address and length
> + of the register space. Can optionally contain a second entry
> + corresponding to the CRTC gamma LUT address.
> +
> +- reg-names: "base" for the base register space. If present, the CRTC
> + gamma LUT name should be "lut".
As per Rob Herring, current suggestion is to avoid reg-names when
possible. The code should just look for the presence of a 2nd entry
and assume that if it's there that it's the lut range. Full context:
https://lore.kernel.org/lkml/CAL_Jsq+MMunmVWqeW9v2RyzsMKP+=kMzeTHNMG4JDHM7Fy0HBg@mail.gmail.com/
-Doug
Powered by blists - more mailing lists