From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm: rcar-du: Restrict DPLL duty cycle workaround to H3 ES1.x
Date: Mon, 26 Jun 2017 21:36:01 +0200 [thread overview]
Message-ID: <CAMuHMdVjHJP7OoN6h2T5-UgReyqb9E2uwgxaAT3zLTBQor0vHw@mail.gmail.com> (raw)
In-Reply-To: <20170621090407.4093-1-laurent.pinchart+renesas@ideasonboard.com>
Hi Laurent,
On Wed, Jun 21, 2017 at 11:04 AM, Laurent Pinchart
<laurent.pinchart+renesas@ideasonboard.com> wrote:
> --- a/drivers/gpu/drm/rcar-du/rcar_du_crtc.c
> +++ b/drivers/gpu/drm/rcar-du/rcar_du_crtc.c
> @@ -158,6 +157,11 @@ static void rcar_du_dpll_divider(struct rcar_du_crtc *rcrtc,
> best_diff);
> }
>
> +static const struct soc_device_attribute rcar_du_r8a7795_es1[] = {
> + { .soc_id = "r8a7795", .revision = "ES1.*" },
> + { /* sentinel */ }
> +};
> +
> static void rcar_du_crtc_set_display_timing(struct rcar_du_crtc *rcrtc)
> {
> const struct drm_display_mode *mode = &rcrtc->crtc.state->adjusted_mode;
> @@ -185,7 +189,20 @@ static void rcar_du_crtc_set_display_timing(struct rcar_du_crtc *rcrtc)
>
> extclk = clk_get_rate(rcrtc->extclock);
> if (rcdu->info->dpll_ch & (1 << rcrtc->index)) {
> - rcar_du_dpll_divider(rcrtc, &dpll, extclk, mode_clock);
> + unsigned long target = mode_clock;
> +
> + /*
> + * The H3 ES1.x exhibits dot clock duty cycle stability
> + * issues. We can work around them by configuring the
> + * DPLL to twice the desired frequency, coupled with a
> + * /2 post-divider. This isn't needed on other SoCs and
> + * breaks HDMI output on M3-W for a currently unknown
> + * reason, so restrict the workaround to H3 ES1.x.
> + */
> + if (soc_device_match(rcar_du_r8a7795_es1))
Matching is done over and over again, on every display enable/resume.
Can it be done at probe time?
Or in rcar_du_crtc_create(), which has access to rcrtc?
> + target *= 2;
You can also store the multiplier in rcar_du_r8a7795_es1.data
(store 1 in .data of the sentinel), removing the need for an if clause.
> +
> + rcar_du_dpll_divider(rcrtc, &dpll, extclk, target);
> extclk = dpll.output;
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-06-26 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 9:04 [PATCH 1/2] drm: rcar-du: Restrict DPLL duty cycle workaround to H3 ES1.x Laurent Pinchart
2017-06-21 9:04 ` [PATCH 2/2] drm: rcar-du: Add HDMI outputs to R8A7796 device description Laurent Pinchart
2017-07-12 13:51 ` Kieran Bingham
2017-07-12 14:19 ` Geert Uytterhoeven
2017-07-12 14:27 ` Kieran Bingham
2017-06-26 19:36 ` Geert Uytterhoeven [this message]
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=CAMuHMdVjHJP7OoN6h2T5-UgReyqb9E2uwgxaAT3zLTBQor0vHw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-renesas-soc@vger.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 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).