From: doudahwezomiechahtah@xff.cz (Ondřej Jirman)
To: linux-arm-kernel@lists.infradead.org
Subject: [v2] drm/sun4i: add lvds mode_valid function
Date: Thu, 19 Apr 2018 15:34:21 +0200 [thread overview]
Message-ID: <20180419133421.6fx3whge7h364vd3@core> (raw)
In-Reply-To: <1520940019-68977-1-git-send-email-giulio.benetti@micronovasrl.com>
Hello Giulio,
this patch breaks LVDS output on A83T. Without it, modesetting works,
with it there's no output.
Some more info below...
On Tue, Mar 13, 2018 at 12:20:19PM +0100, Giulio Benetti wrote:
> mode_valid function is missing for lvds.
>
> Add it making it pointed by encoder helper functions.
>
> Signed-off-by: Giulio Benetti <giulio.benetti@micronovasrl.com>
> ---
> drivers/gpu/drm/sun4i/sun4i_lvds.c | 55 ++++++++++++++++++++++++++++++++++++++
> 1 file changed, 55 insertions(+)
>
> diff --git a/drivers/gpu/drm/sun4i/sun4i_lvds.c b/drivers/gpu/drm/sun4i/sun4i_lvds.c
> index be3f14d..bffff4c 100644
> --- a/drivers/gpu/drm/sun4i/sun4i_lvds.c
> +++ b/drivers/gpu/drm/sun4i/sun4i_lvds.c
> @@ -94,9 +94,64 @@ static void sun4i_lvds_encoder_disable(struct drm_encoder *encoder)
> }
> }
>
> +static enum drm_mode_status sun4i_lvds_encoder_mode_valid(struct drm_encoder *crtc,
> + const struct drm_display_mode *mode)
> +{
> + struct sun4i_lvds *lvds = drm_encoder_to_sun4i_lvds(crtc);
> + struct sun4i_tcon *tcon = lvds->tcon;
> + u32 hsync = mode->hsync_end - mode->hsync_start;
> + u32 vsync = mode->vsync_end - mode->vsync_start;
> + unsigned long rate = mode->clock * 1000;
> + long rounded_rate;
> +
> + DRM_DEBUG_DRIVER("Validating modes...\n");
> +
> + if (hsync < 1)
> + return MODE_HSYNC_NARROW;
> +
> + if (hsync > 0x3ff)
> + return MODE_HSYNC_WIDE;
> +
> + if ((mode->hdisplay < 1) || (mode->htotal < 1))
> + return MODE_H_ILLEGAL;
> +
> + if ((mode->hdisplay > 0x7ff) || (mode->htotal > 0xfff))
> + return MODE_BAD_HVALUE;
> +
> + DRM_DEBUG_DRIVER("Horizontal parameters OK\n");
> +
> + if (vsync < 1)
> + return MODE_VSYNC_NARROW;
> +
> + if (vsync > 0x3ff)
> + return MODE_VSYNC_WIDE;
> +
> + if ((mode->vdisplay < 1) || (mode->vtotal < 1))
> + return MODE_V_ILLEGAL;
> +
> + if ((mode->vdisplay > 0x7ff) || (mode->vtotal > 0xfff))
> + return MODE_BAD_VVALUE;
> +
> + DRM_DEBUG_DRIVER("Vertical parameters OK\n");
> +
> + tcon->dclk_min_div = 7;
> + tcon->dclk_max_div = 7;
Why would validation function change any state anywhere?
> + rounded_rate = clk_round_rate(tcon->dclk, rate);
The issue is here, on A83T TBS A711 tablet, I get...
sun4i-tcon 1c0c000.lcd-controller: XXX: hsync=20 hdisplay=1024 htotal=1384
vsync=5 vdisplay=600 vtotal=640 rate=52000000 rounded_rate=51857142
> + if (rounded_rate < rate)
> + return MODE_CLOCK_LOW;
> +
> + if (rounded_rate > rate)
> + return MODE_CLOCK_HIGH;
... while the previous conditions require an exact match for some reason.
But HW works fine without an exact rate match. Why is exact match required here?
thank you,
Ondrej
> + DRM_DEBUG_DRIVER("Clock rate OK\n");
> +
> + return MODE_OK;
> +}
> +
> static const struct drm_encoder_helper_funcs sun4i_lvds_enc_helper_funcs = {
> .disable = sun4i_lvds_encoder_disable,
> .enable = sun4i_lvds_encoder_enable,
> + .mode_valid = sun4i_lvds_encoder_mode_valid,
> };
>
> static const struct drm_encoder_funcs sun4i_lvds_enc_funcs = {
next prev parent reply other threads:[~2018-04-19 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 11:20 [PATCH v2] drm/sun4i: add lvds mode_valid function Giulio Benetti
2018-03-14 9:30 ` Maxime Ripard
2018-04-19 13:34 ` Ondřej Jirman [this message]
2018-04-19 13:36 ` [v2] " Chen-Yu Tsai
2018-04-19 14:02 ` Giulio Benetti
2018-04-20 13:10 ` Ondřej Jirman
2018-04-20 20:39 ` Maxime Ripard
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=20180419133421.6fx3whge7h364vd3@core \
--to=doudahwezomiechahtah@xff.cz \
--cc=linux-arm-kernel@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