From: Fabrizio Castro <fabrizio.castro@bp.renesas.com> To: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Cc: Andrzej Hajda <a.hajda@samsung.com>, David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>, Maarten Lankhorst <maarten.lankhorst@linux.intel.com>, Maxime Ripard <maxime.ripard@bootlin.com>, Sean Paul <sean@poorly.run>, "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, Simon Horman <horms@verge.net.au>, Geert Uytterhoeven <geert+renesas@glider.be>, Chris Paterson <Chris.Paterson2@renesas.com>, Biju Das <biju.das@bp.renesas.com>, "linux-renesas-soc@vger.kernel.org" <linux-renesas-soc@vger.kernel.org>, Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>, Jacopo Mondi <jacopo+renesas@jmondi.org>, "sam@ravnborg.org" <sam@ravnborg.org> Subject: RE: [PATCH v3 5/8] drm: bridge: thc63: Do not report input bus mode through bridge timings Date: Fri, 6 Dec 2019 15:38:24 +0000 [thread overview] Message-ID: <TY1PR01MB177084C7006801D3D03D7CF7C05F0@TY1PR01MB1770.jpnprd01.prod.outlook.com> (raw) In-Reply-To: <20191107195215.GJ24983@pendragon.ideasonboard.com> Hi Laurent, Thank you for your feedback! > From: linux-kernel-owner@vger.kernel.org <linux-kernel-owner@vger.kernel.org> On Behalf Of Laurent Pinchart > Sent: 07 November 2019 19:52 > Subject: Re: [PATCH v3 5/8] drm: bridge: thc63: Do not report input bus mode through bridge timings > > Hi Fabrizio, > > Thank you for the patch. > > On Wed, Aug 28, 2019 at 07:36:39PM +0100, Fabrizio Castro wrote: > > No need to report the input bus mode through bridge timings > > anymore, that's now done through the DT, as specified by the > > dt-bindings. > > Doesn't this break backward compatibility with older DT, as mentioned in > the review of 4/8 ? > I'll drop this patch in v4 Thanks, Fab > > Signed-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com> > > > > --- > > v2->v3: > > * new patch > > --- > > drivers/gpu/drm/bridge/thc63lvd1024.c | 9 ++++----- > > include/drm/drm_bridge.h | 8 -------- > > 2 files changed, 4 insertions(+), 13 deletions(-) > > > > diff --git a/drivers/gpu/drm/bridge/thc63lvd1024.c b/drivers/gpu/drm/bridge/thc63lvd1024.c > > index 3d74129b..730f682 100644 > > --- a/drivers/gpu/drm/bridge/thc63lvd1024.c > > +++ b/drivers/gpu/drm/bridge/thc63lvd1024.c > > @@ -34,7 +34,7 @@ struct thc63_dev { > > struct drm_bridge bridge; > > struct drm_bridge *next; > > > > - struct drm_bridge_timings timings; > > + bool dual_link; > > }; > > > > static inline struct thc63_dev *to_thc63(struct drm_bridge *bridge) > > @@ -62,7 +62,7 @@ static enum drm_mode_status thc63_mode_valid(struct drm_bridge *bridge, > > * isn't supported by the driver yet, simply derive the limits from the > > * input mode. > > */ > > - if (thc63->timings.dual_link) { > > + if (thc63->dual_link) { > > min_freq = 40000; > > max_freq = 150000; > > } else { > > @@ -157,13 +157,13 @@ static int thc63_parse_dt(struct thc63_dev *thc63) > > > > if (remote) { > > if (of_device_is_available(remote)) > > - thc63->timings.dual_link = true; > > + thc63->dual_link = true; > > of_node_put(remote); > > } > > } > > > > dev_dbg(thc63->dev, "operating in %s-link mode\n", > > - thc63->timings.dual_link ? "dual" : "single"); > > + thc63->dual_link ? "dual" : "single"); > > > > return 0; > > } > > @@ -221,7 +221,6 @@ static int thc63_probe(struct platform_device *pdev) > > thc63->bridge.driver_private = thc63; > > thc63->bridge.of_node = pdev->dev.of_node; > > thc63->bridge.funcs = &thc63_bridge_func; > > - thc63->bridge.timings = &thc63->timings; > > > > drm_bridge_add(&thc63->bridge); > > > > diff --git a/include/drm/drm_bridge.h b/include/drm/drm_bridge.h > > index 7616f65..3228018 100644 > > --- a/include/drm/drm_bridge.h > > +++ b/include/drm/drm_bridge.h > > @@ -362,14 +362,6 @@ struct drm_bridge_timings { > > * input signal after the clock edge. > > */ > > u32 hold_time_ps; > > - /** > > - * @dual_link: > > - * > > - * True if the bus operates in dual-link mode. The exact meaning is > > - * dependent on the bus type. For LVDS buses, this indicates that even- > > - * and odd-numbered pixels are received on separate links. > > - */ > > - bool dual_link; > > }; > > > > /** > > -- > Regards, > > Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Fabrizio Castro <fabrizio.castro@bp.renesas.com> To: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Cc: Maxime Ripard <maxime.ripard@bootlin.com>, Geert Uytterhoeven <geert+renesas@glider.be>, David Airlie <airlied@linux.ie>, "sam@ravnborg.org" <sam@ravnborg.org>, Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>, Biju Das <biju.das@bp.renesas.com>, "linux-renesas-soc@vger.kernel.org" <linux-renesas-soc@vger.kernel.org>, Simon Horman <horms@verge.net.au>, Chris Paterson <Chris.Paterson2@renesas.com>, Jacopo Mondi <jacopo+renesas@jmondi.org>, Sean Paul <sean@poorly.run> Subject: RE: [PATCH v3 5/8] drm: bridge: thc63: Do not report input bus mode through bridge timings Date: Fri, 6 Dec 2019 15:38:24 +0000 [thread overview] Message-ID: <TY1PR01MB177084C7006801D3D03D7CF7C05F0@TY1PR01MB1770.jpnprd01.prod.outlook.com> (raw) In-Reply-To: <20191107195215.GJ24983@pendragon.ideasonboard.com> Hi Laurent, Thank you for your feedback! > From: linux-kernel-owner@vger.kernel.org <linux-kernel-owner@vger.kernel.org> On Behalf Of Laurent Pinchart > Sent: 07 November 2019 19:52 > Subject: Re: [PATCH v3 5/8] drm: bridge: thc63: Do not report input bus mode through bridge timings > > Hi Fabrizio, > > Thank you for the patch. > > On Wed, Aug 28, 2019 at 07:36:39PM +0100, Fabrizio Castro wrote: > > No need to report the input bus mode through bridge timings > > anymore, that's now done through the DT, as specified by the > > dt-bindings. > > Doesn't this break backward compatibility with older DT, as mentioned in > the review of 4/8 ? > I'll drop this patch in v4 Thanks, Fab > > Signed-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com> > > > > --- > > v2->v3: > > * new patch > > --- > > drivers/gpu/drm/bridge/thc63lvd1024.c | 9 ++++----- > > include/drm/drm_bridge.h | 8 -------- > > 2 files changed, 4 insertions(+), 13 deletions(-) > > > > diff --git a/drivers/gpu/drm/bridge/thc63lvd1024.c b/drivers/gpu/drm/bridge/thc63lvd1024.c > > index 3d74129b..730f682 100644 > > --- a/drivers/gpu/drm/bridge/thc63lvd1024.c > > +++ b/drivers/gpu/drm/bridge/thc63lvd1024.c > > @@ -34,7 +34,7 @@ struct thc63_dev { > > struct drm_bridge bridge; > > struct drm_bridge *next; > > > > - struct drm_bridge_timings timings; > > + bool dual_link; > > }; > > > > static inline struct thc63_dev *to_thc63(struct drm_bridge *bridge) > > @@ -62,7 +62,7 @@ static enum drm_mode_status thc63_mode_valid(struct drm_bridge *bridge, > > * isn't supported by the driver yet, simply derive the limits from the > > * input mode. > > */ > > - if (thc63->timings.dual_link) { > > + if (thc63->dual_link) { > > min_freq = 40000; > > max_freq = 150000; > > } else { > > @@ -157,13 +157,13 @@ static int thc63_parse_dt(struct thc63_dev *thc63) > > > > if (remote) { > > if (of_device_is_available(remote)) > > - thc63->timings.dual_link = true; > > + thc63->dual_link = true; > > of_node_put(remote); > > } > > } > > > > dev_dbg(thc63->dev, "operating in %s-link mode\n", > > - thc63->timings.dual_link ? "dual" : "single"); > > + thc63->dual_link ? "dual" : "single"); > > > > return 0; > > } > > @@ -221,7 +221,6 @@ static int thc63_probe(struct platform_device *pdev) > > thc63->bridge.driver_private = thc63; > > thc63->bridge.of_node = pdev->dev.of_node; > > thc63->bridge.funcs = &thc63_bridge_func; > > - thc63->bridge.timings = &thc63->timings; > > > > drm_bridge_add(&thc63->bridge); > > > > diff --git a/include/drm/drm_bridge.h b/include/drm/drm_bridge.h > > index 7616f65..3228018 100644 > > --- a/include/drm/drm_bridge.h > > +++ b/include/drm/drm_bridge.h > > @@ -362,14 +362,6 @@ struct drm_bridge_timings { > > * input signal after the clock edge. > > */ > > u32 hold_time_ps; > > - /** > > - * @dual_link: > > - * > > - * True if the bus operates in dual-link mode. The exact meaning is > > - * dependent on the bus type. For LVDS buses, this indicates that even- > > - * and odd-numbered pixels are received on separate links. > > - */ > > - bool dual_link; > > }; > > > > /** > > -- > 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-12-06 15:38 UTC|newest] Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-08-28 18:36 [PATCH v3 0/8] Add dual-LVDS panel support to EK874 Fabrizio Castro 2019-08-28 18:36 ` [PATCH v3 1/8] dt-bindings: display: Add bindings for LVDS bus-timings Fabrizio Castro 2019-08-29 7:57 ` Geert Uytterhoeven 2019-08-29 7:57 ` Geert Uytterhoeven 2019-08-29 9:14 ` Fabrizio Castro 2019-08-29 9:14 ` Fabrizio Castro 2019-08-29 14:03 ` Rob Herring 2019-08-29 14:03 ` Rob Herring 2019-08-29 14:38 ` Fabrizio Castro 2019-08-29 14:38 ` Fabrizio Castro 2019-11-07 18:00 ` Laurent Pinchart 2019-11-07 18:00 ` Laurent Pinchart 2019-11-07 18:00 ` Laurent Pinchart 2019-12-06 15:11 ` Fabrizio Castro 2019-12-06 15:11 ` Fabrizio Castro 2019-12-06 15:10 ` Fabrizio Castro 2019-12-06 15:10 ` Fabrizio Castro 2019-08-28 18:36 ` [PATCH v3 2/8] dt-bindings: display: Add idk-2121wr binding Fabrizio Castro 2019-11-07 18:12 ` Laurent Pinchart 2019-11-07 18:12 ` Laurent Pinchart 2019-12-06 15:17 ` Fabrizio Castro 2019-12-06 15:17 ` Fabrizio Castro 2019-08-28 18:36 ` [PATCH v3 3/8] drm: Add bus timings helper Fabrizio Castro 2019-11-07 19:26 ` Laurent Pinchart 2019-11-07 19:26 ` Laurent Pinchart 2019-11-07 19:30 ` Daniel Vetter 2019-11-07 19:30 ` Daniel Vetter 2019-12-06 15:25 ` Fabrizio Castro 2019-12-06 15:25 ` Fabrizio Castro 2019-12-06 15:24 ` Fabrizio Castro 2019-12-06 15:24 ` Fabrizio Castro 2019-08-28 18:36 ` [PATCH v3 4/8] drm: rcar-du: lvds: Add dual-LVDS panels support Fabrizio Castro 2019-11-07 19:50 ` Laurent Pinchart 2019-11-07 19:50 ` Laurent Pinchart 2019-12-06 15:35 ` Fabrizio Castro 2019-12-06 15:35 ` Fabrizio Castro 2019-08-28 18:36 ` [PATCH v3 5/8] drm: bridge: thc63: Do not report input bus mode through bridge timings Fabrizio Castro 2019-11-07 19:52 ` Laurent Pinchart 2019-11-07 19:52 ` Laurent Pinchart 2019-12-06 15:38 ` Fabrizio Castro [this message] 2019-12-06 15:38 ` Fabrizio Castro 2019-08-28 18:36 ` [PATCH v3 6/8] arm64: dts: renesas: Add EK874 board with idk-2121wr display support Fabrizio Castro 2019-11-07 19:55 ` Laurent Pinchart 2019-08-28 18:36 ` [PATCH v3 7/8] [HACK] arm64: dts: renesas: draak: Enable LVDS Fabrizio Castro 2019-11-07 19:57 ` Laurent Pinchart 2019-12-06 15:40 ` Fabrizio Castro 2019-08-28 18:36 ` [PATCH v3 8/8] [HACK] arm64: dts: renesas: draak: Enable LVDS dual-link operation Fabrizio Castro 2019-08-29 15:26 ` [PATCH v3 0/8] Add dual-LVDS panel support to EK874 Rob Herring 2019-08-29 15:26 ` Rob Herring 2019-09-02 10:01 ` Fabrizio Castro 2019-09-02 10:01 ` Fabrizio Castro 2019-10-22 16:30 ` Fabrizio Castro 2019-10-22 16:30 ` Fabrizio Castro
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=TY1PR01MB177084C7006801D3D03D7CF7C05F0@TY1PR01MB1770.jpnprd01.prod.outlook.com \ --to=fabrizio.castro@bp.renesas.com \ --cc=Chris.Paterson2@renesas.com \ --cc=a.hajda@samsung.com \ --cc=airlied@linux.ie \ --cc=biju.das@bp.renesas.com \ --cc=daniel@ffwll.ch \ --cc=dri-devel@lists.freedesktop.org \ --cc=geert+renesas@glider.be \ --cc=horms@verge.net.au \ --cc=jacopo+renesas@jmondi.org \ --cc=kieran.bingham+renesas@ideasonboard.com \ --cc=laurent.pinchart@ideasonboard.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-renesas-soc@vger.kernel.org \ --cc=maarten.lankhorst@linux.intel.com \ --cc=maxime.ripard@bootlin.com \ --cc=sam@ravnborg.org \ --cc=sean@poorly.run \ /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.