All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	dri-devel@lists.freedesktop.org,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 04/12] drm: rcar-du: Convert LVDS encoder code to bridge driver
Date: Mon, 15 Jan 2018 22:32:38 +0200	[thread overview]
Message-ID: <84235223.mW0iJ7b1HL@avalon> (raw)
In-Reply-To: <9a2806f3-d232-b587-bc77-733e9d45c138@cogentembedded.com>

Hi Sergei,

On Monday, 15 January 2018 22:25:16 EET Sergei Shtylyov wrote:
> On 01/13/2018 02:14 AM, Laurent Pinchart wrote:
> > The LVDS encoders used to be described in DT as part of the DU. They now
> > have their own DT node, linked to the DU using the OF graph bindings.
> > This allows moving internal LVDS encoder support to a separate driver
> > modelled as a DRM bridge. Backward compatibility is retained as legacy
> > DT is patched live to move to the new bindings.
> > 
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
> 
> [...]
> 
> > diff --git a/drivers/gpu/drm/rcar-du/rcar_du_drv.c
> > b/drivers/gpu/drm/rcar-du/rcar_du_drv.c index 6e02c762a557..06a3fbdd728a
> > 100644
> > --- a/drivers/gpu/drm/rcar-du/rcar_du_drv.c
> > +++ b/drivers/gpu/drm/rcar-du/rcar_du_drv.c
> 
> [...]
> 
> >   /* --------------------------------------------------------------------
> > @@ -74,7 +75,6 @@ static const struct rcar_du_device_info
> > rzg1_du_r8a7745_info = {
> >   			.port = 1,
 >   		},
> >   	},
> > -	.num_lvds = 0,
> >   };
> >   
> >   static const struct rcar_du_device_info rcar_du_r8a7779_info = {
> > @@ -95,14 +95,13 @@ static const struct rcar_du_device_info
> > rcar_du_r8a7779_info = {
> >   			.port = 1,
> >   		},
> >   	},
> > -	.num_lvds = 0,
> >   };
> >   
> >   static const struct rcar_du_device_info rcar_du_r8a7790_info = {
> >   	.gen = 2,
> >   	.features = RCAR_DU_FEATURE_CRTC_IRQ_CLOCK
> >   		  | RCAR_DU_FEATURE_EXT_CTRL_REGS,
> > -	.quirks = RCAR_DU_QUIRK_ALIGN_128B | RCAR_DU_QUIRK_LVDS_LANES,
> > +	.quirks = RCAR_DU_QUIRK_ALIGN_128B,
> >   	.num_crtcs = 3,
> >   	.routes = {
> >   		/*
> > @@ -164,7 +163,6 @@ static const struct rcar_du_device_info
> > rcar_du_r8a7792_info = {
> >   			.port = 1,
> >   		},
> >   	},
> > -	.num_lvds = 0,
> >   };
> >   
> >   static const struct rcar_du_device_info rcar_du_r8a7794_info = {
> > @@ -186,7 +184,6 @@ static const struct rcar_du_device_info
> > rcar_du_r8a7794_info = {
> >   			.port = 1,
> >   		},
> >   	},
> > -	.num_lvds = 0,
> 
> I think you can remove *all* such initializers and the field itself with
> them -- otherwise it looks like you're doing a not-quite-related drive-by
> clean up...

The OF compatibility code uses the .num_lvds field, that's why I haven't 
removed it.

-- 
Regards,

Laurent Pinchart

WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: linux-renesas-soc@vger.kernel.org,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 04/12] drm: rcar-du: Convert LVDS encoder code to bridge driver
Date: Mon, 15 Jan 2018 22:32:38 +0200	[thread overview]
Message-ID: <84235223.mW0iJ7b1HL@avalon> (raw)
In-Reply-To: <9a2806f3-d232-b587-bc77-733e9d45c138@cogentembedded.com>

Hi Sergei,

On Monday, 15 January 2018 22:25:16 EET Sergei Shtylyov wrote:
> On 01/13/2018 02:14 AM, Laurent Pinchart wrote:
> > The LVDS encoders used to be described in DT as part of the DU. They now
> > have their own DT node, linked to the DU using the OF graph bindings.
> > This allows moving internal LVDS encoder support to a separate driver
> > modelled as a DRM bridge. Backward compatibility is retained as legacy
> > DT is patched live to move to the new bindings.
> > 
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
> 
> [...]
> 
> > diff --git a/drivers/gpu/drm/rcar-du/rcar_du_drv.c
> > b/drivers/gpu/drm/rcar-du/rcar_du_drv.c index 6e02c762a557..06a3fbdd728a
> > 100644
> > --- a/drivers/gpu/drm/rcar-du/rcar_du_drv.c
> > +++ b/drivers/gpu/drm/rcar-du/rcar_du_drv.c
> 
> [...]
> 
> >   /* --------------------------------------------------------------------
> > @@ -74,7 +75,6 @@ static const struct rcar_du_device_info
> > rzg1_du_r8a7745_info = {
> >   			.port = 1,
 >   		},
> >   	},
> > -	.num_lvds = 0,
> >   };
> >   
> >   static const struct rcar_du_device_info rcar_du_r8a7779_info = {
> > @@ -95,14 +95,13 @@ static const struct rcar_du_device_info
> > rcar_du_r8a7779_info = {
> >   			.port = 1,
> >   		},
> >   	},
> > -	.num_lvds = 0,
> >   };
> >   
> >   static const struct rcar_du_device_info rcar_du_r8a7790_info = {
> >   	.gen = 2,
> >   	.features = RCAR_DU_FEATURE_CRTC_IRQ_CLOCK
> >   		  | RCAR_DU_FEATURE_EXT_CTRL_REGS,
> > -	.quirks = RCAR_DU_QUIRK_ALIGN_128B | RCAR_DU_QUIRK_LVDS_LANES,
> > +	.quirks = RCAR_DU_QUIRK_ALIGN_128B,
> >   	.num_crtcs = 3,
> >   	.routes = {
> >   		/*
> > @@ -164,7 +163,6 @@ static const struct rcar_du_device_info
> > rcar_du_r8a7792_info = {
> >   			.port = 1,
> >   		},
> >   	},
> > -	.num_lvds = 0,
> >   };
> >   
> >   static const struct rcar_du_device_info rcar_du_r8a7794_info = {
> > @@ -186,7 +184,6 @@ static const struct rcar_du_device_info
> > rcar_du_r8a7794_info = {
> >   			.port = 1,
> >   		},
> >   	},
> > -	.num_lvds = 0,
> 
> I think you can remove *all* such initializers and the field itself with
> them -- otherwise it looks like you're doing a not-quite-related drive-by
> clean up...

The OF compatibility code uses the .num_lvds field, that's why I haven't 
removed it.

-- 
Regards,

Laurent Pinchart

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-01-15 20:32 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12 23:14 [PATCH v2 00/12] R-Car DU: Convert LVDS code to bridge driver Laurent Pinchart
2018-01-12 23:14 ` [PATCH v2 01/12] dt-bindings: display: renesas: Add R-Car LVDS encoder DT bindings Laurent Pinchart
2018-01-12 23:14   ` Laurent Pinchart
2018-01-19 22:47   ` Rob Herring
2018-01-12 23:14 ` [PATCH v2 02/12] dt-bindings: display: renesas: Deprecate LVDS support in the DU bindings Laurent Pinchart
2018-01-12 23:14   ` Laurent Pinchart
2018-01-12 23:14 ` [PATCH v2 03/12] drm: rcar-du: Fix legacy DT to create LVDS encoder nodes Laurent Pinchart
2018-01-12 23:14   ` Laurent Pinchart
2018-01-15 17:09   ` Rob Herring
2018-01-15 18:01     ` Laurent Pinchart
2018-01-15 18:01       ` Laurent Pinchart
2018-01-16  8:56       ` Geert Uytterhoeven
2018-01-16  8:56         ` Geert Uytterhoeven
2018-01-16 10:23         ` Laurent Pinchart
2018-01-16 10:23           ` Laurent Pinchart
2018-01-16 15:08         ` Rob Herring
2018-01-16 15:31           ` Geert Uytterhoeven
2018-01-16 15:31             ` Geert Uytterhoeven
2018-01-15 19:12     ` Frank Rowand
2018-01-15 19:22       ` Laurent Pinchart
2018-01-15 19:22         ` Laurent Pinchart
2018-01-15 20:12         ` Frank Rowand
2018-01-15 20:12           ` Frank Rowand
2018-01-15 20:29           ` Laurent Pinchart
2018-01-15 20:29             ` Laurent Pinchart
2018-01-15 23:46             ` Frank Rowand
2018-01-15 23:46               ` Frank Rowand
2018-01-15 23:57               ` Frank Rowand
2018-01-16 14:35               ` Rob Herring
2018-01-16 14:35                 ` Rob Herring
2018-01-16 16:32                 ` Laurent Pinchart
2018-01-16 16:32                   ` Laurent Pinchart
2018-01-16 16:54                   ` Rob Herring
2018-01-16 16:54                     ` Rob Herring
2018-01-16 20:35                     ` Laurent Pinchart
2018-01-16 20:35                       ` Laurent Pinchart
2018-01-21  9:35   ` Sergei Shtylyov
2018-01-12 23:14 ` [PATCH v2 04/12] drm: rcar-du: Convert LVDS encoder code to bridge driver Laurent Pinchart
2018-01-15  8:30   ` Geert Uytterhoeven
2018-01-15  8:30     ` Geert Uytterhoeven
2018-01-15  8:32     ` Laurent Pinchart
2018-01-15 20:25   ` Sergei Shtylyov
2018-01-15 20:25     ` Sergei Shtylyov
2018-01-15 20:32     ` Laurent Pinchart [this message]
2018-01-15 20:32       ` Laurent Pinchart
2018-01-15 21:01       ` Sergei Shtylyov
2018-01-12 23:14 ` [PATCH v2 05/12] ARM: dts: porter: Fix HDMI output routing Laurent Pinchart
2018-01-12 23:14 ` [PATCH v2 06/12] ARM: dts: r8a7790: Convert to new LVDS DT bindings Laurent Pinchart
2018-01-15 12:30   ` Sergei Shtylyov
2018-01-15 12:30     ` Sergei Shtylyov
2018-01-12 23:14 ` [PATCH v2 07/12] ARM: dts: r8a7791: " Laurent Pinchart
2018-01-15 12:27   ` Sergei Shtylyov
2018-01-15 12:27     ` Sergei Shtylyov
2018-01-12 23:14 ` [PATCH v2 08/12] ARM: dts: r8a7792: Convert to new DU " Laurent Pinchart
2018-01-12 23:14 ` [PATCH v2 09/12] ARM: dts: r8a7793: Convert to new LVDS " Laurent Pinchart
2018-01-12 23:14 ` [PATCH v2 10/12] ARM: dts: r8a7794: Convert to new DU " Laurent Pinchart
2018-01-12 23:14 ` [PATCH v2 11/12] arm64: dts: renesas: r8a7795: Convert to new LVDS " Laurent Pinchart
2018-01-12 23:14 ` [PATCH v2 12/12] arm64: dts: renesas: r8a7796: " 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=84235223.mW0iJ7b1HL@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=sergei.shtylyov@cogentembedded.com \
    /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 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.