From: Linus Heckemann <linus@sphalerite.org>
To: Hugh Cole-Baker <sigmaris@gmail.com>,
heiko@sntech.de, hjc@rock-chips.com
Cc: linux-rockchip@lists.infradead.org, ezequiel@collabora.com,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org,
Hugh Cole-Baker <sigmaris@gmail.com>
Subject: Re: [PATCH v2 1/3] drm/rockchip: define gamma registers for RK3399
Date: Tue, 13 Sep 2022 14:58:32 +0200 [thread overview]
Message-ID: <ygaa6735t3b.fsf@localhost> (raw)
In-Reply-To: <20211019215843.42718-2-sigmaris@gmail.com>
Hugh Cole-Baker <sigmaris@gmail.com> writes:
>
> The VOP on RK3399 has a different approach from previous versions for
> setting a gamma lookup table, using an update_gamma_lut register. As
> this differs from RK3288, give RK3399 its own set of "common" register
> definitions.
>
> Signed-off-by: Hugh Cole-Baker <sigmaris@gmail.com>
> Tested-by: "Milan P. Stanić" <mps@arvanta.net>
> ---
>
> Changes from v1: no changes in this patch
>
This series makes gammastep on sway for adjusting colour temperature
work wonderfully. I'd really appreciate if it found its way upstream!
Tested-by: Linus Heckemann <git@sphalerite.org>
next prev parent reply other threads:[~2022-09-14 7:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 21:58 [PATCH v2 0/3] drm/rockchip: support gamma control on RK3399 Hugh Cole-Baker
2021-10-19 21:58 ` [PATCH v2 1/3] drm/rockchip: define gamma registers for RK3399 Hugh Cole-Baker
2022-08-07 12:38 ` Milan P. Stanić
2022-09-13 12:58 ` Linus Heckemann [this message]
2021-10-19 21:58 ` [PATCH v2 2/3] drm/rockchip: support gamma control on RK3399 Hugh Cole-Baker
2021-10-19 21:58 ` [PATCH v2 3/3] arm64: dts: rockchip: enable " Hugh Cole-Baker
2022-09-15 14:40 ` Robin Murphy
2022-09-15 16:53 ` Hugh Cole-Baker
2022-09-15 17:11 ` Robin Murphy
2022-09-15 13:40 ` (subset) [PATCH v2 0/3] drm/rockchip: support " Heiko Stuebner
2022-09-15 13:49 ` Heiko Stuebner
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=ygaa6735t3b.fsf@localhost \
--to=linus@sphalerite.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ezequiel@collabora.com \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=sigmaris@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).