From: Quentin Schulz <quentin.schulz@cherry.de>
To: Andy Yan <andyshrk@163.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
hjc@rock-chips.com, andy.yan@rock-chips.com,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Heiko Stuebner <heiko.stuebner@cherry.de>
Subject: Re: [PATCH 1/2] drm/rockchip: vop2: fix rk3588 dp+dsi maxclk verification
Date: Thu, 14 Nov 2024 10:38:56 +0100 [thread overview]
Message-ID: <030c3b0f-9396-4fbb-af4e-cf2cb58ffac1@cherry.de> (raw)
In-Reply-To: <72672888.8f9.1932826549b.Coremail.andyshrk@163.com>
Hi Andy,
On 11/14/24 1:50 AM, Andy Yan wrote:
>
> Hi,
>
> At 2024-05-06 15:44:36, "Quentin Schulz" <quentin.schulz@cherry.de> wrote:
>> Hi Heiko,
>>
>> On 4/25/24 9:55 PM, Heiko Stuebner wrote:
>>> From: Heiko Stuebner <heiko.stuebner@cherry.de>
>>>
>>> The clock is in Hz while the value checked against is in kHz, so
>>> actual frequencies will never be able to be below to max value.
>>> Fix this by specifying the max-value in Hz too.
>>>
>>> Fixes: 5a028e8f062f ("drm/rockchip: vop2: Add support for rk3588")
>>> Signed-off-by: Heiko Stuebner <heiko.stuebner@cherry.de>
>>> ---
>>> drivers/gpu/drm/rockchip/rockchip_drm_vop2.c | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c b/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c
>>> index 9bee1fd88e6a2..523880a4e8e74 100644
>>> --- a/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c
>>> +++ b/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c
>>> @@ -1719,7 +1719,7 @@ static unsigned long rk3588_calc_cru_cfg(struct vop2_video_port *vp, int id,
>>> else
>>> dclk_out_rate = v_pixclk >> 2;
>>>
>>> - dclk_rate = rk3588_calc_dclk(dclk_out_rate, 600000);
>>> + dclk_rate = rk3588_calc_dclk(dclk_out_rate, 600000000);
>>> if (!dclk_rate) {
>>> drm_err(vop2->drm, "DP dclk_out_rate out of range, dclk_out_rate: %ld KHZ\n",
>>
>> It seems the error message is incorrect as well and should be saying Hz
>> instead of KHz. (note also the lowercase z).
>
> I think kHz is fine, we can find many siminary usage in drm:
>
> drivers/gpu/drm/drm_vblank.c
> 656: drm_dbg_core(dev, "crtc %u: clock %d kHz framedur %d linedur %d\n",
The issue is that we print kHz for something that is in Hz, not that we
print a value in kHz.
The former is incorrect, the latter is fine. We are in the former
scenario here I believe, so it needs to be fixed.
Cheers,
Quentin
next prev parent reply other threads:[~2024-11-14 9:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 19:55 [PATCH 0/2] drm/rockchip: vop2: two fixes from working on DSI enablement Heiko Stuebner
2024-04-25 19:55 ` [PATCH 1/2] drm/rockchip: vop2: fix rk3588 dp+dsi maxclk verification Heiko Stuebner
2024-05-03 12:13 ` Quentin Schulz
2024-11-14 0:50 ` Andy Yan
2024-11-14 9:38 ` Quentin Schulz [this message]
2024-11-14 10:16 ` Andy Yan
2024-11-13 1:16 ` Andy Yan
2024-04-25 19:55 ` [PATCH 2/2] drm/rockchip: vop2: configure layers for vp3 on rk3588 Heiko Stuebner
2024-05-03 12:57 ` Quentin Schulz
2024-05-03 13:02 ` Heiko Stübner
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=030c3b0f-9396-4fbb-af4e-cf2cb58ffac1@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=andy.yan@rock-chips.com \
--cc=andyshrk@163.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko.stuebner@cherry.de \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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