From: Sascha Hauer <s.hauer@pengutronix.de>
To: Andy Yan <andy.yan@rock-chips.com>
Cc: Andy Yan <andyshrk@163.com>,
heiko@sntech.de, hjc@rock-chips.com,
dri-devel@lists.freedesktop.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
devicetree@vger.kernel.org, sebastian.reichel@collabora.com,
kever.yang@rock-chips.com, chris.obbard@collabora.com
Subject: Re: [PATCH 09/11] drm/rockchip: vop2: Add support for rk3588
Date: Thu, 16 Nov 2023 08:50:15 +0100 [thread overview]
Message-ID: <20231116075015.GG3359458@pengutronix.de> (raw)
In-Reply-To: <229557d7-beec-44e0-9ee6-4a962b33ec79@rock-chips.com>
On Thu, Nov 16, 2023 at 03:24:54PM +0800, Andy Yan wrote:
> > case ROCKCHIP_VOP2_EP_HDMI0:
> > case ROCKCHIP_VOP2_EP_HDMI1:
> > ...
> > }
> >
> > would look a bit better overall.
> >
> > > + /*
> > > + * K = 2: dclk_core = if_pixclk_rate > if_dclk_rate
> > > + * K = 1: dclk_core = hdmie_edp_dclk > if_pixclk_rate
> > > + */
> > > + if (output_mode == ROCKCHIP_OUT_MODE_YUV420) {
> > > + dclk_rate = dclk_rate >> 1;
> > > + K = 2;
> > > + }
> > > +
> > > + if_pixclk_rate = (dclk_core_rate << 1) / K;
> > > + if_dclk_rate = dclk_core_rate / K;
> > > +
> > > + *if_pixclk_div = dclk_rate / if_pixclk_rate;
> > > + *if_dclk_div = dclk_rate / if_dclk_rate;
> > Not sure if this will change with future extensions, but currently
> > *if_pixclk_div will always be 2 and *if_dclk_div will alway be 4,
> > so maybe better write it like this
>
>
> Yes, the calculation of *if_pixclk_div is always 2 and *if_dclk_div is always 4,
>
> I think calculation formula can give us a clear explanation why is 2 or 4.
>
> considering the great power of rk3588, i think it can calculate it very easy.
Sure it can. My concern is not the CPU time it takes to do that
equation, but more the readability of the code. For me as a reader it
might be more easily acceptable that both dividers have fixed values
than it is to understand the equation.
Your mileage may vary, I won't insist on this.
>
> >
> >
> > > + *dclk_core_div = dclk_rate / dclk_core_rate;
> > *dclk_core_div is calculated the same way for all cases. You could pull
> > this out of the if/else.
> Okay, will do.
> >
> > > + } else if (vop2_output_if_is_edp(id)) {
> > > + /* edp_pixclk = edp_dclk > dclk_core */
> > > + if_pixclk_rate = v_pixclk / K;
> > > + if_dclk_rate = v_pixclk / K;
> > if_dclk_rate is unused here.
>
>
> It will be removed in next version.
>
> >
> > > + dclk_rate = if_pixclk_rate * K;
> > > + *dclk_core_div = dclk_rate / dclk_core_rate;
> > > + *if_pixclk_div = dclk_rate / if_pixclk_rate;
> > > + *if_dclk_div = *if_pixclk_div;
> > Both *if_pixclk_div and *if_dclk_div will always be 1.
>
> Actually, they will be the value of K here, if it work at split mode(two
>
> edp connect to one VP, one show the image for left half, one for right half,
>
> a function like a dual channel mipi dsi).
>
> I know it split mode is not supported by the current mainline, but i think keep
Ok.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2023-11-16 7:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 11:25 [PATCH 00/11] Add VOP2 support on rk3588 Andy Yan
2023-11-14 11:27 ` [PATCH 01/11] drm/rockchip: move output interface related definition to rockchip_drm_drv.h Andy Yan
2023-11-14 11:27 ` [PATCH 02/11] Revert "drm/rockchip: vop2: Use regcache_sync() to fix suspend/resume" Andy Yan
2023-11-14 11:27 ` [PATCH 03/11] drm/rockchip: vop2: set half_block_en bit in all mode Andy Yan
2023-11-14 11:27 ` [PATCH 04/11] drm/rockchip: vop2: clear afbc en and transform bit for cluster window at linear mode Andy Yan
2023-11-14 11:27 ` [PATCH 05/11] drm/rockchip: vop2: Set YUV/RGB overlay mode Andy Yan
2023-11-14 11:28 ` [PATCH 06/11] drm/rockchip: vop2: rename grf to sys_grf Andy Yan
2023-11-14 11:28 ` [PATCH 07/11] dt-bindings: soc: rockchip: add rk3588 vop/vo syscon Andy Yan
2023-11-16 19:26 ` Rob Herring
2023-11-14 11:28 ` [PATCH 08/11] dt-bindings: display: vop2: Add rk3588 support Andy Yan
2023-11-14 13:44 ` Rob Herring
2023-11-14 21:54 ` Heiko Stübner
2023-11-15 2:45 ` Andy Yan
2023-11-14 11:28 ` [PATCH 09/11] drm/rockchip: vop2: Add support for rk3588 Andy Yan
2023-11-14 23:34 ` Heiko Stübner
2023-11-15 2:02 ` Andy Yan
2023-11-15 8:24 ` Heiko Stübner
2023-11-15 9:08 ` Sascha Hauer
2023-11-16 7:24 ` Andy Yan
2023-11-16 7:50 ` Sascha Hauer [this message]
2023-11-16 8:00 ` Andy Yan
2023-11-16 10:39 ` Andy Yan
2023-11-16 13:47 ` Sebastian Reichel
2023-11-17 7:06 ` Andy Yan
2023-11-17 9:39 ` Sascha Hauer
2023-11-16 19:27 ` Rob Herring
2023-11-17 23:46 ` Jonas Karlman
2023-11-18 0:31 ` Andy Yan
2023-11-14 11:29 ` [PATCH 10/11] drm/rockchip: vop2: Add debugfs support Andy Yan
2023-11-14 11:29 ` [PATCH 11/11] arm64: dts: rockchip: Add vop on rk3588 Andy Yan
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=20231116075015.GG3359458@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=andy.yan@rock-chips.com \
--cc=andyshrk@163.com \
--cc=chris.obbard@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.reichel@collabora.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