From: Ulrich Hecht <uli@fpond.eu> To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>, dri-devel@lists.freedesktop.org Cc: linux-renesas-soc@vger.kernel.org, Kieran Bingham <kieran.bingham@ideasonboard.com> Subject: Re: [PATCH v2 04/16] drm: bridge: thc63: Restrict modes based on hardware operating frequency Date: Mon, 17 Sep 2018 12:53:43 +0200 (CEST) [thread overview] Message-ID: <891115091.239809.1537181623129@webmail.strato.com> (raw) In-Reply-To: <20180914091046.483-5-laurent.pinchart+renesas@ideasonboard.com> Thank you for your patch! > On September 14, 2018 at 11:10 AM Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> wrote: > > > The THC63LVD1024 is restricted to a pixel clock frequency in the range > of 8 to 135 MHz. Implement the bridge .mode_valid() operation > accordingly. > > Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> > Reviewed-by: Andrzej Hajda <a.hajda@samsung.com> > Tested-by: Jacopo Mondi <jacopo+renesas@jmondi.org> > --- > drivers/gpu/drm/bridge/thc63lvd1024.c | 18 ++++++++++++++++++ > 1 file changed, 18 insertions(+) > > diff --git a/drivers/gpu/drm/bridge/thc63lvd1024.c b/drivers/gpu/drm/bridge/thc63lvd1024.c > index c8b9edd5a7f4..63609ba16b6d 100644 > --- a/drivers/gpu/drm/bridge/thc63lvd1024.c > +++ b/drivers/gpu/drm/bridge/thc63lvd1024.c > @@ -45,6 +45,23 @@ static int thc63_attach(struct drm_bridge *bridge) > return drm_bridge_attach(bridge->encoder, thc63->next, bridge); > } > > +static enum drm_mode_status thc63_mode_valid(struct drm_bridge *bridge, > + const struct drm_display_mode *mode) > +{ > + /* > + * The THC63LVD0124 clock frequency range is 8 to 135 MHz in single-in, That should be THC63LVD1024. > + * single-out mode. For the input clock (that's what we're talking about, right?), that also applies to single-in/dual-out. Maybe just omit the "single-out" clause? > Note that the limits depends on the mode and will > + * need to be adjusted accordingly. > + */ I don't quite understand. Does that refer to the THC63 mode, or the DRM mode? > + if (mode->clock < 8000) > + return MODE_CLOCK_LOW; > + > + if (mode->clock > 135000) > + return MODE_CLOCK_HIGH; > + > + return MODE_OK; > +} > + > static void thc63_enable(struct drm_bridge *bridge) > { > struct thc63_dev *thc63 = to_thc63(bridge); > @@ -77,6 +94,7 @@ static void thc63_disable(struct drm_bridge *bridge) > > static const struct drm_bridge_funcs thc63_bridge_func = { > .attach = thc63_attach, > + .mode_valid = thc63_mode_valid, > .enable = thc63_enable, > .disable = thc63_disable, > }; > -- > Regards, > > Laurent Pinchart > CU Uli
WARNING: multiple messages have this Message-ID (diff)
From: Ulrich Hecht <uli@fpond.eu> To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>, dri-devel@lists.freedesktop.org Cc: linux-renesas-soc@vger.kernel.org, Kieran Bingham <kieran.bingham@ideasonboard.com> Subject: Re: [PATCH v2 04/16] drm: bridge: thc63: Restrict modes based on hardware operating frequency Date: Mon, 17 Sep 2018 12:53:43 +0200 (CEST) [thread overview] Message-ID: <891115091.239809.1537181623129@webmail.strato.com> (raw) In-Reply-To: <20180914091046.483-5-laurent.pinchart+renesas@ideasonboard.com> Thank you for your patch! > On September 14, 2018 at 11:10 AM Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> wrote: > > > The THC63LVD1024 is restricted to a pixel clock frequency in the range > of 8 to 135 MHz. Implement the bridge .mode_valid() operation > accordingly. > > Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> > Reviewed-by: Andrzej Hajda <a.hajda@samsung.com> > Tested-by: Jacopo Mondi <jacopo+renesas@jmondi.org> > --- > drivers/gpu/drm/bridge/thc63lvd1024.c | 18 ++++++++++++++++++ > 1 file changed, 18 insertions(+) > > diff --git a/drivers/gpu/drm/bridge/thc63lvd1024.c b/drivers/gpu/drm/bridge/thc63lvd1024.c > index c8b9edd5a7f4..63609ba16b6d 100644 > --- a/drivers/gpu/drm/bridge/thc63lvd1024.c > +++ b/drivers/gpu/drm/bridge/thc63lvd1024.c > @@ -45,6 +45,23 @@ static int thc63_attach(struct drm_bridge *bridge) > return drm_bridge_attach(bridge->encoder, thc63->next, bridge); > } > > +static enum drm_mode_status thc63_mode_valid(struct drm_bridge *bridge, > + const struct drm_display_mode *mode) > +{ > + /* > + * The THC63LVD0124 clock frequency range is 8 to 135 MHz in single-in, That should be THC63LVD1024. > + * single-out mode. For the input clock (that's what we're talking about, right?), that also applies to single-in/dual-out. Maybe just omit the "single-out" clause? > Note that the limits depends on the mode and will > + * need to be adjusted accordingly. > + */ I don't quite understand. Does that refer to the THC63 mode, or the DRM mode? > + if (mode->clock < 8000) > + return MODE_CLOCK_LOW; > + > + if (mode->clock > 135000) > + return MODE_CLOCK_HIGH; > + > + return MODE_OK; > +} > + > static void thc63_enable(struct drm_bridge *bridge) > { > struct thc63_dev *thc63 = to_thc63(bridge); > @@ -77,6 +94,7 @@ static void thc63_disable(struct drm_bridge *bridge) > > static const struct drm_bridge_funcs thc63_bridge_func = { > .attach = thc63_attach, > + .mode_valid = thc63_mode_valid, > .enable = thc63_enable, > .disable = thc63_disable, > }; > -- > Regards, > > Laurent Pinchart > CU Uli _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-09-17 16:20 UTC|newest] Thread overview: 118+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-09-14 9:10 [PATCH v2 00/16] R-Car D3/E3 display support (with LVDS PLL) Laurent Pinchart 2018-09-14 9:10 ` Laurent Pinchart 2018-09-14 9:10 ` [PATCH v2 01/16] dt-bindings: display: renesas: du: Document r8a77990 bindings Laurent Pinchart 2018-09-14 9:10 ` Laurent Pinchart 2018-09-17 10:53 ` Ulrich Hecht 2018-09-17 10:53 ` Ulrich Hecht 2018-09-14 9:10 ` [PATCH v2 02/16] dt-bindings: display: renesas: lvds: " Laurent Pinchart 2018-09-14 9:10 ` Laurent Pinchart 2018-09-17 10:53 ` Ulrich Hecht 2018-09-17 10:53 ` Ulrich Hecht 2018-09-24 11:36 ` Kieran Bingham 2018-09-24 11:36 ` Kieran Bingham 2018-09-14 9:10 ` [PATCH v2 03/16] dt-bindings: display: renesas: lvds: Add EXTAL and DU_DOTCLKIN clocks Laurent Pinchart 2018-09-14 9:10 ` Laurent Pinchart 2018-09-17 10:53 ` Ulrich Hecht 2018-09-17 10:53 ` Ulrich Hecht 2018-09-24 19:04 ` Kieran Bingham 2018-09-24 19:04 ` Kieran Bingham 2018-09-14 9:10 ` [PATCH v2 04/16] drm: bridge: thc63: Restrict modes based on hardware operating frequency Laurent Pinchart 2018-09-14 9:10 ` Laurent Pinchart 2018-09-17 10:53 ` Ulrich Hecht [this message] 2018-09-17 10:53 ` Ulrich Hecht 2018-09-17 12:23 ` Laurent Pinchart 2018-09-17 12:23 ` Laurent Pinchart 2018-09-14 9:10 ` [PATCH v2 05/16] drm: rcar-du: lvds: D3/E3 support Laurent Pinchart 2018-09-14 9:10 ` Laurent Pinchart 2018-09-17 10:53 ` Ulrich Hecht 2018-09-17 10:53 ` Ulrich Hecht 2018-09-17 12:41 ` Laurent Pinchart 2018-09-17 12:41 ` Laurent Pinchart 2018-09-17 12:49 ` jacopo mondi 2018-09-17 12:49 ` jacopo mondi 2018-09-14 9:10 ` [PATCH v2 06/16] drm: rcar-du: Perform the initial CRTC setup from rcar_du_crtc_get() Laurent Pinchart 2018-09-14 9:10 ` Laurent Pinchart 2018-09-17 12:50 ` jacopo mondi 2018-09-17 12:50 ` jacopo mondi 2018-09-26 15:55 ` Ulrich Hecht 2018-09-26 15:55 ` Ulrich Hecht 2018-09-28 15:14 ` Laurent Pinchart 2018-09-28 15:14 ` Laurent Pinchart 2018-09-14 9:10 ` [PATCH v2 07/16] drm: rcar-du: Use LVDS PLL clock as dot clock when possible Laurent Pinchart 2018-09-14 9:10 ` Laurent Pinchart 2018-09-17 12:55 ` jacopo mondi 2018-09-17 12:55 ` jacopo mondi 2018-09-26 15:55 ` Ulrich Hecht 2018-09-26 15:55 ` Ulrich Hecht 2018-11-27 0:44 ` Kuninori Morimoto 2018-11-27 0:44 ` Kuninori Morimoto 2018-12-06 9:50 ` Laurent Pinchart 2018-12-06 9:50 ` Laurent Pinchart 2018-12-07 1:25 ` Kuninori Morimoto 2018-12-07 1:25 ` Kuninori Morimoto 2018-09-14 9:10 ` [PATCH v2 08/16] drm: rcar-du: Enable configurable DPAD0 routing on Gen3 Laurent Pinchart 2018-09-14 9:10 ` Laurent Pinchart 2018-09-17 12:56 ` jacopo mondi 2018-09-17 12:56 ` jacopo mondi 2018-09-26 15:55 ` Ulrich Hecht 2018-09-26 15:55 ` Ulrich Hecht 2018-09-14 9:10 ` [PATCH v2 09/16] drm: rcar-du: Cache DSYSR value to ensure known initial value Laurent Pinchart 2018-09-14 9:10 ` Laurent Pinchart 2018-09-24 11:18 ` Kieran Bingham 2018-09-24 11:18 ` Kieran Bingham 2018-09-26 15:55 ` Ulrich Hecht 2018-09-26 15:55 ` Ulrich Hecht 2018-09-14 9:10 ` [PATCH v2 10/16] drm: rcar-du: Don't use TV sync mode when not supported by the hardware Laurent Pinchart 2018-09-14 9:10 ` Laurent Pinchart 2018-09-24 11:26 ` Kieran Bingham 2018-09-24 11:26 ` Kieran Bingham 2018-09-26 15:55 ` Ulrich Hecht 2018-09-26 15:55 ` Ulrich Hecht 2018-09-14 9:10 ` [PATCH v2 11/16] drm: rcar-du: Add r8a77990 and r8a77995 device support Laurent Pinchart 2018-09-14 9:10 ` Laurent Pinchart 2018-09-24 11:41 ` Kieran Bingham 2018-09-24 11:41 ` Kieran Bingham 2018-09-14 9:10 ` [PATCH v2 12/16] arm64: dts: renesas: r8a77990: Add I2C device nodes Laurent Pinchart 2018-09-14 9:10 ` Laurent Pinchart 2018-09-17 7:33 ` Simon Horman 2018-09-17 7:33 ` Simon Horman 2018-09-17 8:08 ` Laurent Pinchart 2018-09-17 8:08 ` Laurent Pinchart 2018-09-14 9:10 ` [PATCH v2 13/16] arm64: dts: renesas: r8a77990: Add display output support Laurent Pinchart 2018-09-14 9:10 ` Laurent Pinchart 2018-09-17 7:50 ` Simon Horman 2018-09-17 7:50 ` Simon Horman 2018-09-17 8:14 ` Simon Horman 2018-09-17 8:14 ` Simon Horman 2018-09-17 8:47 ` Laurent Pinchart 2018-09-17 8:47 ` Laurent Pinchart 2018-09-17 8:54 ` Laurent Pinchart 2018-09-17 8:54 ` Laurent Pinchart 2018-09-17 8:59 ` Laurent Pinchart 2018-09-17 8:59 ` Laurent Pinchart 2018-09-19 8:35 ` Simon Horman 2018-09-19 8:35 ` Simon Horman 2018-09-19 13:11 ` Laurent Pinchart 2018-09-19 13:11 ` Laurent Pinchart 2018-09-21 7:16 ` Simon Horman 2018-09-21 7:16 ` Simon Horman 2018-09-21 8:41 ` Laurent Pinchart 2018-09-21 8:41 ` Laurent Pinchart 2018-09-17 8:38 ` Laurent Pinchart 2018-09-17 8:38 ` Laurent Pinchart 2018-09-17 8:51 ` Simon Horman 2018-09-17 8:51 ` Simon Horman 2018-09-17 9:08 ` Laurent Pinchart 2018-09-17 9:08 ` Laurent Pinchart 2018-09-17 9:48 ` Geert Uytterhoeven 2018-09-17 9:48 ` Geert Uytterhoeven 2018-09-17 10:01 ` Laurent Pinchart 2018-09-17 10:01 ` Laurent Pinchart 2018-09-14 9:10 ` [PATCH v2 14/16] arm64: dts: renesas: r8a77995: Add LVDS support Laurent Pinchart 2018-09-14 9:10 ` Laurent Pinchart 2018-09-14 9:10 ` [PATCH v2 15/16] arm64: dts: renesas: r8a77990: ebisu: Enable VGA and HDMI outputs Laurent Pinchart 2018-09-14 9:10 ` Laurent Pinchart 2018-09-26 15:55 ` Ulrich Hecht 2018-09-26 15:55 ` Ulrich Hecht 2018-09-14 9:10 ` [PATCH v2 16/16] arm64: dts: renesas: r8a77995: draak: Enable HDMI display output Laurent Pinchart 2018-09-14 9:10 ` 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=891115091.239809.1537181623129@webmail.strato.com \ --to=uli@fpond.eu \ --cc=dri-devel@lists.freedesktop.org \ --cc=kieran.bingham@ideasonboard.com \ --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: 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.