From: Heiko Stuebner <heiko@sntech.de>
To: robh@kernel.org, WeiHao Li <cn.liweihao@gmail.com>,
andy.yan@rock-chips.com
Cc: hjc@rock-chips.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-clk@vger.kernel.org,
WeiHao Li <cn.liweihao@gmail.com>
Subject: Re: [PATCH v1 2/7] drm/rockchip: vop: add lut_size for RK3368 vop_data
Date: Wed, 03 Sep 2025 14:16:04 +0200 [thread overview]
Message-ID: <5726817.Isy0gbHreE@phil> (raw)
In-Reply-To: <20250831104855.45883-3-cn.liweihao@gmail.com>
Hi,
Am Sonntag, 31. August 2025, 12:48:50 Mitteleuropäische Sommerzeit schrieb WeiHao Li:
> VOP driver need a correct lut_size to work normally.
please add a comment where that value is coming from.
Because the vop in the vendor kernel is so vastly different.
Thanks
Heiko
>
> Signed-off-by: WeiHao Li <cn.liweihao@gmail.com>
> ---
> drivers/gpu/drm/rockchip/rockchip_vop_reg.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/rockchip/rockchip_vop_reg.c b/drivers/gpu/drm/rockchip/rockchip_vop_reg.c
> index d1f788763..219f8c2fa 100644
> --- a/drivers/gpu/drm/rockchip/rockchip_vop_reg.c
> +++ b/drivers/gpu/drm/rockchip/rockchip_vop_reg.c
> @@ -880,6 +880,7 @@ static const struct vop_data rk3368_vop = {
> .win = rk3368_vop_win_data,
> .win_size = ARRAY_SIZE(rk3368_vop_win_data),
> .max_output = { 4096, 2160 },
> + .lut_size = 1024,
> };
>
> static const struct vop_intr rk3366_vop_intr = {
>
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: robh@kernel.org, WeiHao Li <cn.liweihao@gmail.com>,
andy.yan@rock-chips.com
Cc: hjc@rock-chips.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-clk@vger.kernel.org,
WeiHao Li <cn.liweihao@gmail.com>
Subject: Re: [PATCH v1 2/7] drm/rockchip: vop: add lut_size for RK3368 vop_data
Date: Wed, 03 Sep 2025 14:16:04 +0200 [thread overview]
Message-ID: <5726817.Isy0gbHreE@phil> (raw)
In-Reply-To: <20250831104855.45883-3-cn.liweihao@gmail.com>
Hi,
Am Sonntag, 31. August 2025, 12:48:50 Mitteleuropäische Sommerzeit schrieb WeiHao Li:
> VOP driver need a correct lut_size to work normally.
please add a comment where that value is coming from.
Because the vop in the vendor kernel is so vastly different.
Thanks
Heiko
>
> Signed-off-by: WeiHao Li <cn.liweihao@gmail.com>
> ---
> drivers/gpu/drm/rockchip/rockchip_vop_reg.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/rockchip/rockchip_vop_reg.c b/drivers/gpu/drm/rockchip/rockchip_vop_reg.c
> index d1f788763..219f8c2fa 100644
> --- a/drivers/gpu/drm/rockchip/rockchip_vop_reg.c
> +++ b/drivers/gpu/drm/rockchip/rockchip_vop_reg.c
> @@ -880,6 +880,7 @@ static const struct vop_data rk3368_vop = {
> .win = rk3368_vop_win_data,
> .win_size = ARRAY_SIZE(rk3368_vop_win_data),
> .max_output = { 4096, 2160 },
> + .lut_size = 1024,
> };
>
> static const struct vop_intr rk3366_vop_intr = {
>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-09-03 13:13 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 10:48 [PATCH v1 0/7] drm/rockchip: Add MIPI DSI support for RK3368 WeiHao Li
2025-08-31 10:48 ` WeiHao Li
2025-08-31 10:48 ` [PATCH v1 1/7] drm/rockchip: dsi: Add " WeiHao Li
2025-08-31 10:48 ` WeiHao Li
2025-09-03 12:07 ` Heiko Stuebner
2025-09-03 12:07 ` Heiko Stuebner
2025-09-03 13:37 ` 李维豪
2025-09-03 13:37 ` 李维豪
2025-08-31 10:48 ` [PATCH v1 2/7] drm/rockchip: vop: add lut_size for RK3368 vop_data WeiHao Li
2025-08-31 10:48 ` WeiHao Li
2025-09-03 12:16 ` Heiko Stuebner [this message]
2025-09-03 12:16 ` Heiko Stuebner
2025-08-31 10:48 ` [PATCH v1 3/7] dt-bindings: clock: rk3368: Add SCLK_MIPIDSI_24M WeiHao Li
2025-08-31 10:48 ` WeiHao Li
2025-08-31 15:00 ` Heiko Stübner
2025-08-31 15:00 ` Heiko Stübner
2025-09-01 0:17 ` 李维豪
2025-09-01 0:17 ` 李维豪
2025-09-02 6:49 ` Heiko Stuebner
2025-09-02 6:49 ` Heiko Stuebner
2025-09-03 13:22 ` 李维豪
2025-09-03 13:22 ` 李维豪
2025-09-01 21:32 ` Rob Herring (Arm)
2025-09-01 21:32 ` Rob Herring (Arm)
2025-08-31 10:48 ` [PATCH v1 4/7] clk: rockchip: use clock ids for SCLK_MIPIDSI_24M on rk3368 WeiHao Li
2025-08-31 10:48 ` WeiHao Li
2025-08-31 10:48 ` [PATCH v1 5/7] ARM: dts: rockchip: Add display subsystem for RK3368 WeiHao Li
2025-08-31 10:48 ` WeiHao Li
2025-08-31 15:04 ` Heiko Stübner
2025-08-31 15:04 ` Heiko Stübner
2025-09-01 0:20 ` 李维豪
2025-09-01 0:20 ` 李维豪
2025-08-31 10:48 ` [PATCH v1 6/7] ARM: dts: rockchip: Add D-PHY " WeiHao Li
2025-08-31 10:48 ` WeiHao Li
2025-08-31 15:06 ` Heiko Stübner
2025-08-31 15:06 ` Heiko Stübner
2025-09-01 0:33 ` 李维豪
2025-09-01 0:33 ` 李维豪
2025-08-31 10:48 ` [PATCH v1 7/7] ARM: dts: rockchip: Add DSI " WeiHao Li
2025-08-31 10:48 ` WeiHao Li
2025-08-31 15:09 ` [PATCH v1 0/7] drm/rockchip: Add MIPI DSI support " Heiko Stübner
2025-08-31 15:09 ` Heiko Stübner
2025-09-01 0:46 ` 李维豪
2025-09-01 0:46 ` 李维豪
2025-09-02 13:17 ` Rob Herring (Arm)
2025-09-02 13:17 ` Rob Herring (Arm)
2025-09-03 12:19 ` (subset) " Heiko Stuebner
2025-09-03 12:19 ` 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=5726817.Isy0gbHreE@phil \
--to=heiko@sntech.de \
--cc=andy.yan@rock-chips.com \
--cc=cn.liweihao@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hjc@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.