* [PATCH] drm/rockchip: Properly adjust to a true clock in adjusted_mode
@ 2016-08-08 19:29 Sean Paul
2016-08-09 2:53 ` Yakir Yang
2016-08-09 3:28 ` Mark yao
0 siblings, 2 replies; 3+ messages in thread
From: Sean Paul @ 2016-08-08 19:29 UTC (permalink / raw)
To: dianders, mark.yao, ykk, dri-devel; +Cc: linux-rockchip
From: Douglas Anderson <dianders@chromium.org>
When fixing up the clock in vop_crtc_mode_fixup() we're not doing it
quite correctly. Specifically if we've got the true clock 266666667 Hz,
we'll perform this calculation:
266666667 / 1000 => 266666
Later when we try to set the clock we'll do clk_set_rate(266666 *
1000). The common clock framework won't actually pick the proper clock
in this case since it always wants clocks <= the specified one.
Let's solve this by using DIV_ROUND_UP.
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Signed-off-by: Sean Paul <seanpaul@chromium.org>
---
drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop.c b/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
index 31744fe..1bbffaf 100644
--- a/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
+++ b/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
@@ -891,7 +891,8 @@ static bool vop_crtc_mode_fixup(struct drm_crtc *crtc,
struct vop *vop = to_vop(crtc);
adjusted_mode->clock =
- clk_round_rate(vop->dclk, mode->clock * 1000) / 1000;
+ DIV_ROUND_UP(clk_round_rate(vop->dclk, mode->clock * 1000),
+ 1000);
return true;
}
--
2.8.0.rc3.226.g39d4020
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] drm/rockchip: Properly adjust to a true clock in adjusted_mode
2016-08-08 19:29 [PATCH] drm/rockchip: Properly adjust to a true clock in adjusted_mode Sean Paul
@ 2016-08-09 2:53 ` Yakir Yang
2016-08-09 3:28 ` Mark yao
1 sibling, 0 replies; 3+ messages in thread
From: Yakir Yang @ 2016-08-09 2:53 UTC (permalink / raw)
To: Sean Paul, dianders, mark.yao, dri-devel; +Cc: linux-rockchip
Sean,
On 08/09/2016 03:29 AM, Sean Paul wrote:
> From: Douglas Anderson <dianders@chromium.org>
>
> When fixing up the clock in vop_crtc_mode_fixup() we're not doing it
> quite correctly. Specifically if we've got the true clock 266666667 Hz,
> we'll perform this calculation:
> 266666667 / 1000 => 266666
>
> Later when we try to set the clock we'll do clk_set_rate(266666 *
> 1000). The common clock framework won't actually pick the proper clock
> in this case since it always wants clocks <= the specified one.
>
> Let's solve this by using DIV_ROUND_UP.
>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> Signed-off-by: Sean Paul <seanpaul@chromium.org>
After discuss with Zheng Xing (Rockchip clock contributor), we think
this patch looks good, so:
Reviewed-by: Yakir Yang <ykk@rock-chips.com>
> ---
> drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop.c b/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
> index 31744fe..1bbffaf 100644
> --- a/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
> +++ b/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
> @@ -891,7 +891,8 @@ static bool vop_crtc_mode_fixup(struct drm_crtc *crtc,
> struct vop *vop = to_vop(crtc);
>
> adjusted_mode->clock =
> - clk_round_rate(vop->dclk, mode->clock * 1000) / 1000;
> + DIV_ROUND_UP(clk_round_rate(vop->dclk, mode->clock * 1000),
> + 1000);
>
> return true;
> }
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] drm/rockchip: Properly adjust to a true clock in adjusted_mode
2016-08-08 19:29 [PATCH] drm/rockchip: Properly adjust to a true clock in adjusted_mode Sean Paul
2016-08-09 2:53 ` Yakir Yang
@ 2016-08-09 3:28 ` Mark yao
1 sibling, 0 replies; 3+ messages in thread
From: Mark yao @ 2016-08-09 3:28 UTC (permalink / raw)
To: Sean Paul, dianders, ykk, dri-devel; +Cc: linux-rockchip
On 2016年08月09日 03:29, Sean Paul wrote:
> From: Douglas Anderson <dianders@chromium.org>
>
> When fixing up the clock in vop_crtc_mode_fixup() we're not doing it
> quite correctly. Specifically if we've got the true clock 266666667 Hz,
> we'll perform this calculation:
> 266666667 / 1000 => 266666
>
> Later when we try to set the clock we'll do clk_set_rate(266666 *
> 1000). The common clock framework won't actually pick the proper clock
> in this case since it always wants clocks <= the specified one.
>
> Let's solve this by using DIV_ROUND_UP.
Good, applied to my drm fixes.
Thanks
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> Signed-off-by: Sean Paul <seanpaul@chromium.org>
> ---
> drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop.c b/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
> index 31744fe..1bbffaf 100644
> --- a/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
> +++ b/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
> @@ -891,7 +891,8 @@ static bool vop_crtc_mode_fixup(struct drm_crtc *crtc,
> struct vop *vop = to_vop(crtc);
>
> adjusted_mode->clock =
> - clk_round_rate(vop->dclk, mode->clock * 1000) / 1000;
> + DIV_ROUND_UP(clk_round_rate(vop->dclk, mode->clock * 1000),
> + 1000);
>
> return true;
> }
--
Mark Yao
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-08-09 3:29 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-08-08 19:29 [PATCH] drm/rockchip: Properly adjust to a true clock in adjusted_mode Sean Paul
2016-08-09 2:53 ` Yakir Yang
2016-08-09 3:28 ` Mark yao
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).