From: Ezequiel Garcia <ezequiel@collabora.com>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: dri-devel@lists.freedesktop.org,
linux-rockchip@lists.infradead.org,
Sandy Huang <hjc@rock-chips.com>,
kernel@collabora.com, Sean Paul <seanpaul@chromium.org>,
Boris Brezillon <boris.brezillon@collabora.com>,
Douglas Anderson <dianders@chromium.org>,
Jacopo Mondi <jacopo@jmondi.org>,
Ilia Mirkin <imirkin@alum.mit.edu>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] RK3288 Gamma LUT
Date: Tue, 02 Jul 2019 08:26:22 -0300 [thread overview]
Message-ID: <3c68bf286d8b75ac339df0eab43d276667e073c2.camel@collabora.com> (raw)
In-Reply-To: <20190621211346.1324-1-ezequiel@collabora.com>
Hi Heiko,
On Fri, 2019-06-21 at 18:13 -0300, Ezequiel Garcia wrote:
> Let's support Gamma LUT configuration on RK3288 SoCs.
>
> In order to do so, this series adds a new and optional
> address resource.
>
> A separate address resource is required because on this RK3288,
> the LUT address is after the MMU address, which is requested
> by the iommu driver. This prevents the DRM driver
> from requesting an entire register space.
>
> The current implementation works for RGB 10-bit tables, as that
> is what seems to work on RK3288.
>
> This has been tested on a Rock2 Square board, using
> a hacked 'modetest' tool, with legacy and atomic APIs.
>
> Thanks,
> Eze
>
> Changes from v1:
> * drop explicit linear LUT after finding a proper
> way to disable gamma correction.
> * avoid setting gamma is the CRTC is not active.
> * s/int/unsigned int as suggested by Jacopo.
> * only enable color management and set gamma size
> if gamma LUT is supported, suggested by Doug.
> * drop the reg-names usage, and instead just use indexed reg
> specifiers, suggested by Doug.
>
> Changes from RFC:
> * Request (an optional) address resource for the LUT.
> * Add devicetree changes.
> * Drop support for RK3399, which doesn't seem to work
> out of the box and needs more research.
> * Support pass-thru setting when GAMMA_LUT is NULL.
> * Add a check for the gamma size, as suggested by Ilia.
> * Move gamma setting to atomic_commit_tail, as pointed
> out by Jacopo/Laurent, is the correct way.
>
> Ezequiel Garcia (3):
> dt-bindings: display: rockchip: document VOP gamma LUT address
> drm/rockchip: Add optional support for CRTC gamma LUT
> ARM: dts: rockchip: Add RK3288 VOP gamma LUT address
>
> .../display/rockchip/rockchip-vop.txt | 6 +-
> arch/arm/boot/dts/rk3288.dtsi | 4 +-
> drivers/gpu/drm/rockchip/rockchip_drm_fb.c | 3 +
> drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 114 ++++++++++++++++++
> drivers/gpu/drm/rockchip/rockchip_drm_vop.h | 7 ++
> drivers/gpu/drm/rockchip/rockchip_vop_reg.c | 2 +
> 6 files changed, 133 insertions(+), 3 deletions(-)
>
Any other feedback on this series? If you are happy with the approach now,
I am wondering if you can take it or if it's way too late.
Thanks,
Eze
next prev parent reply other threads:[~2019-07-02 11:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 21:13 Ezequiel Garcia
2019-06-21 21:13 ` [PATCH v2 1/3] dt-bindings: display: rockchip: document VOP gamma LUT address Ezequiel Garcia
2019-06-24 19:25 ` Doug Anderson
2019-07-09 22:50 ` Rob Herring
2019-06-21 21:13 ` [PATCH v2 2/3] drm/rockchip: Add optional support for CRTC gamma LUT Ezequiel Garcia
2019-06-24 20:03 ` Doug Anderson
2019-06-25 8:05 ` Jacopo Mondi
2019-06-26 18:49 ` Ezequiel Garcia
2019-06-21 21:13 ` [PATCH v2 3/3] ARM: dts: rockchip: Add RK3288 VOP gamma LUT address Ezequiel Garcia
2019-06-24 20:03 ` Doug Anderson
2019-07-02 11:26 ` Ezequiel Garcia [this message]
2019-07-02 20:14 ` [PATCH v2 0/3] RK3288 Gamma LUT Doug Anderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3c68bf286d8b75ac339df0eab43d276667e073c2.camel@collabora.com \
--to=ezequiel@collabora.com \
--cc=boris.brezillon@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=imirkin@alum.mit.edu \
--cc=jacopo@jmondi.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=seanpaul@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®