From: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> To: dri-devel@lists.freedesktop.org Cc: linux-renesas-soc@vger.kernel.org, Kieran Bingham <kieran.bingham@ideasonboard.com> Subject: [PATCH/RFC 09/15] drm: rcar-du: lvds: Adjust operating frequency for D3 and E3 Date: Thu, 7 Mar 2019 01:23:39 +0200 [thread overview] Message-ID: <20190306232345.23052-10-laurent.pinchart+renesas@ideasonboard.com> (raw) In-Reply-To: <20190306232345.23052-1-laurent.pinchart+renesas@ideasonboard.com> The D3 and E3 SoCs have different pixel clock frequency limits for the LVDS encoder than the other SoCs in the Gen3 family. Adjust the mode fixup implementation accordingly. Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> --- drivers/gpu/drm/rcar-du/rcar_lvds.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/rcar-du/rcar_lvds.c b/drivers/gpu/drm/rcar-du/rcar_lvds.c index cd202157264a..b1abe737dc05 100644 --- a/drivers/gpu/drm/rcar-du/rcar_lvds.c +++ b/drivers/gpu/drm/rcar-du/rcar_lvds.c @@ -515,11 +515,16 @@ static bool rcar_lvds_mode_fixup(struct drm_bridge *bridge, const struct drm_display_mode *mode, struct drm_display_mode *adjusted_mode) { + struct rcar_lvds *lvds = bridge_to_rcar_lvds(bridge); + int min_freq; + /* * The internal LVDS encoder has a restricted clock frequency operating - * range (31MHz to 148.5MHz). Clamp the clock accordingly. + * range, from 5MHz to 148.5MHz on D3 and E3, and from 31MHz to + * 148.5MHz on all other platforms. Clamp the clock accordingly. */ - adjusted_mode->clock = clamp(adjusted_mode->clock, 31000, 148500); + min_freq = lvds->info->quirks & RCAR_LVDS_QUIRK_EXT_PLL ? 5000 : 31000; + adjusted_mode->clock = clamp(adjusted_mode->clock, min_freq, 148500); return true; } -- Regards, Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> To: dri-devel@lists.freedesktop.org Cc: linux-renesas-soc@vger.kernel.org, Kieran Bingham <kieran.bingham@ideasonboard.com> Subject: [PATCH/RFC 09/15] drm: rcar-du: lvds: Adjust operating frequency for D3 and E3 Date: Thu, 7 Mar 2019 01:23:39 +0200 [thread overview] Message-ID: <20190306232345.23052-10-laurent.pinchart+renesas@ideasonboard.com> (raw) In-Reply-To: <20190306232345.23052-1-laurent.pinchart+renesas@ideasonboard.com> The D3 and E3 SoCs have different pixel clock frequency limits for the LVDS encoder than the other SoCs in the Gen3 family. Adjust the mode fixup implementation accordingly. Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> --- drivers/gpu/drm/rcar-du/rcar_lvds.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/rcar-du/rcar_lvds.c b/drivers/gpu/drm/rcar-du/rcar_lvds.c index cd202157264a..b1abe737dc05 100644 --- a/drivers/gpu/drm/rcar-du/rcar_lvds.c +++ b/drivers/gpu/drm/rcar-du/rcar_lvds.c @@ -515,11 +515,16 @@ static bool rcar_lvds_mode_fixup(struct drm_bridge *bridge, const struct drm_display_mode *mode, struct drm_display_mode *adjusted_mode) { + struct rcar_lvds *lvds = bridge_to_rcar_lvds(bridge); + int min_freq; + /* * The internal LVDS encoder has a restricted clock frequency operating - * range (31MHz to 148.5MHz). Clamp the clock accordingly. + * range, from 5MHz to 148.5MHz on D3 and E3, and from 31MHz to + * 148.5MHz on all other platforms. Clamp the clock accordingly. */ - adjusted_mode->clock = clamp(adjusted_mode->clock, 31000, 148500); + min_freq = lvds->info->quirks & RCAR_LVDS_QUIRK_EXT_PLL ? 5000 : 31000; + adjusted_mode->clock = clamp(adjusted_mode->clock, min_freq, 148500); return true; } -- Regards, Laurent Pinchart _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-03-06 23:24 UTC|newest] Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-03-06 23:23 [PATCH/RFC 00/15] R-Car DU: LVDS dual-link mode support Laurent Pinchart 2019-03-06 23:23 ` Laurent Pinchart 2019-03-06 23:23 ` [PATCH/RFC 01/15] drm: Clarify definition of the DRM_BUS_FLAG_(PIXDATA|SYNC)_* macros Laurent Pinchart 2019-03-06 23:23 ` Laurent Pinchart 2019-04-24 8:15 ` Kieran Bingham 2019-04-24 8:15 ` Kieran Bingham 2019-03-06 23:23 ` [PATCH/RFC 02/15] drm: Use new DRM_BUS_FLAG_*_(DRIVE|SAMPLE)_(POS|NEG)EDGE flags Laurent Pinchart 2019-03-06 23:23 ` Laurent Pinchart 2019-04-24 8:15 ` Kieran Bingham 2019-04-24 8:15 ` Kieran Bingham 2019-05-11 20:44 ` Laurent Pinchart 2019-05-11 20:44 ` Laurent Pinchart 2019-03-06 23:23 ` [PATCH/RFC 03/15] drm/bridge: use bus flags in bridge timings Laurent Pinchart 2019-03-06 23:23 ` Laurent Pinchart 2019-04-24 8:13 ` Kieran Bingham 2019-04-24 8:13 ` Kieran Bingham 2019-03-06 23:23 ` [PATCH/RFC 04/15] drm: bridge: Add dual_link field to the drm_bridge_timings structure Laurent Pinchart 2019-03-06 23:23 ` Laurent Pinchart 2019-04-24 8:12 ` Kieran Bingham 2019-04-24 8:12 ` Kieran Bingham 2019-05-11 20:36 ` Laurent Pinchart 2019-05-11 20:36 ` Laurent Pinchart 2019-03-06 23:23 ` [PATCH/RFC 05/15] dt-bindings: display: bridge: thc63lvd1024: Document dual-link operation Laurent Pinchart 2019-03-06 23:23 ` Laurent Pinchart 2019-03-08 16:49 ` Jacopo Mondi 2019-03-08 16:49 ` Jacopo Mondi 2019-03-08 17:57 ` Laurent Pinchart 2019-03-08 17:57 ` Laurent Pinchart 2019-03-09 11:23 ` Jacopo Mondi 2019-03-09 11:23 ` Jacopo Mondi 2019-03-09 11:51 ` Laurent Pinchart 2019-03-09 11:51 ` Laurent Pinchart 2019-03-06 23:23 ` [PATCH/RFC 06/15] drm: bridge: thc63: Report input bus mode through bridge timings Laurent Pinchart 2019-03-06 23:23 ` Laurent Pinchart 2019-03-08 17:32 ` Jacopo Mondi 2019-03-08 17:32 ` Jacopo Mondi 2019-03-08 18:00 ` Laurent Pinchart 2019-03-08 18:00 ` Laurent Pinchart 2019-03-09 11:24 ` Jacopo Mondi 2019-03-09 11:24 ` Jacopo Mondi 2019-03-09 11:45 ` Laurent Pinchart 2019-03-09 11:45 ` Laurent Pinchart 2019-03-06 23:23 ` [PATCH/RFC 07/15] dt-bindings: display: renesas: lvds: Add renesas, companion property Laurent Pinchart 2019-03-06 23:23 ` [PATCH/RFC 07/15] dt-bindings: display: renesas: lvds: Add renesas,companion property Laurent Pinchart 2019-03-18 10:21 ` Geert Uytterhoeven 2019-03-18 10:21 ` Geert Uytterhoeven 2019-03-18 14:22 ` Laurent Pinchart 2019-03-18 14:22 ` Laurent Pinchart 2019-03-06 23:23 ` [PATCH/RFC 08/15] drm: rcar-du: lvds: Remove LVDS double-enable checks Laurent Pinchart 2019-03-06 23:23 ` Laurent Pinchart 2019-03-06 23:23 ` Laurent Pinchart [this message] 2019-03-06 23:23 ` [PATCH/RFC 09/15] drm: rcar-du: lvds: Adjust operating frequency for D3 and E3 Laurent Pinchart 2019-03-08 16:28 ` Jacopo Mondi 2019-03-08 16:28 ` Jacopo Mondi 2019-03-06 23:23 ` [PATCH/RFC 10/15] drm: rcar-du: lvds: Set LVEN and LVRES bits together on D3 Laurent Pinchart 2019-03-06 23:23 ` Laurent Pinchart 2019-03-08 16:25 ` Jacopo Mondi 2019-03-08 16:25 ` Jacopo Mondi 2019-03-08 18:07 ` Laurent Pinchart 2019-03-08 18:07 ` Laurent Pinchart 2019-03-06 23:23 ` [PATCH/RFC 11/15] drm: rcar-du: lvds: Add support for dual-link mode Laurent Pinchart 2019-03-06 23:23 ` Laurent Pinchart 2019-03-08 17:20 ` Jacopo Mondi 2019-03-08 17:20 ` Jacopo Mondi 2019-03-08 18:12 ` Laurent Pinchart 2019-03-08 18:12 ` Laurent Pinchart 2019-03-09 11:11 ` Jacopo Mondi 2019-03-09 11:11 ` Jacopo Mondi 2019-03-09 11:25 ` Laurent Pinchart 2019-03-09 11:25 ` Laurent Pinchart 2019-03-06 23:23 ` [PATCH/RFC 12/15] drm: rcar-du: Skip LVDS1 output on Gen3 when using dual-link LVDS mode Laurent Pinchart 2019-03-06 23:23 ` Laurent Pinchart 2019-03-06 23:23 ` [PATCH/RFC 13/15] arm64: dts: renesas: r8a7799[05]: Point LVDS0 to its companion LVDS1 Laurent Pinchart 2019-03-06 23:23 ` Laurent Pinchart 2019-03-06 23:23 ` [PATCH/RFC 14/15] [HACK] arm64: dts: renesas: draak: Enable LVDS dual-link operation Laurent Pinchart 2019-03-06 23:23 ` Laurent Pinchart 2019-03-06 23:23 ` [PATCH/RFC 15/15] [HACK] arm64: dts: renesas: ebisu: " Laurent Pinchart 2019-03-06 23:23 ` Laurent Pinchart
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=20190306232345.23052-10-laurent.pinchart+renesas@ideasonboard.com \ --to=laurent.pinchart+renesas@ideasonboard.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=kieran.bingham@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.