public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: dri-devel@lists.freedesktop.org
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-samsung-soc@vger.kernel.org"
	<linux-samsung-soc@vger.kernel.org>,
	Sean Paul <seanpaul@google.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Ajay Kumar <ajaykumar.rs@samsung.com>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>,
	Ajay kumar <ajaynumb@gmail.com>,
	Kukjin Kim <kgene.kim@samsung.com>,
	Pannaga Bhushan Reddy Patel <bhushan.r@samsung.com>,
	Prashanth G <prashanth.g@samsung.com>,
	Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V8 00/14] drm/exynos: few patches to enhance bridge chip support
Date: Tue, 16 Dec 2014 01:37:51 +0200	[thread overview]
Message-ID: <3197445.qizQc0zeRb@avalon> (raw)
In-Reply-To: <548ABAB6.6010200@collabora.co.uk>

Hi Javier,

On Friday 12 December 2014 10:51:50 Javier Martinez Canillas wrote:
> Hello,
> 
> On 11/18/2014 07:20 AM, Ajay kumar wrote:
> > On Sat, Nov 15, 2014 at 3:24 PM, Ajay Kumar wrote:
> >> This series is based on master branch of Linus tree at:
> >> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> 
> This series has been in the mailing lists for months and have been tested
> by many people. What else is missing before it can be merged?
> 
> It would be great to have proper display support on platforms that have a
> eDP to LVDS bridge chip (e.g: Snow, Peach Pit and Spring Chromebooks) and
> everything is in place but this series which had been missing many kernel
> releases already.
> 
> >> Changes since V7:
> >>         -- Address comments from Tomi and Laurent:
> >>                 -- Use videoports and endpoints to represent the
> >>                 connection between
> >>                 
> >>                    encoder, bridge and the panel, instead of using
> >>                    phandles.
> >>         
> >>         -- Address comments from Daniel:
> >>                 -- Make the patch description more descriptive.
> >>                 -- remove device pointer from drm_bridge, and just use
> >>                 
> >>                    device_node instead.
> >>                 
> >>                 -- don't pass encoder pointer to bridge_attach.
> >>         
> >>         -- Address comments from Sean Paul:
> >>                 -- Remove bridge from mode_config, and pull out
> >>                 drm_bridge
> >>                 
> >>                    functions from drm_crtc.c to drm_bridge.c
> 
> Tomi and Laurent,
> 
> You asked Ajay to change his series to use the video port and enpoints DT
> bindings instead of phandles, could you please review his latest version?
> 
> I guess is now too late for 3.19 since we are in the middle of the merge
> window but it would be great if this series can at least made it to 3.20.

I don't have time to review the series in details right now, but I'm happy 
with the DT bindings, and have no big issue with the rest of the patches. I 
don't really like the of_drm_find_bridge() concept introduced in 03/14 but I 
won't nack it given lack of time to implement an alternative proposal. It's an 
internal API, it can always be reworked later anyway.

-- 
Regards,

Laurent Pinchart

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

  parent reply	other threads:[~2014-12-15 23:37 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-15  9:54 [PATCH V8 00/14] drm/exynos: few patches to enhance bridge chip support Ajay Kumar
2014-11-15  9:54 ` [PATCH V8 01/14] drm/bridge: ptn3460: Few trivial cleanups Ajay Kumar
2014-11-15  9:54 ` [PATCH V8 02/14] drm/bridge: do not pass drm_bridge_funcs to drm_bridge_init Ajay Kumar
2014-11-15  9:54 ` [PATCH V8 03/14] drm/bridge: make bridge registration independent of drm flow Ajay Kumar
2014-12-02  6:01   ` Ajay kumar
2014-12-08 10:24     ` Ajay kumar
2014-11-15  9:54 ` [PATCH V8 04/14] drm/bridge: ptn3460: Convert to i2c driver model Ajay Kumar
2014-11-15  9:55 ` [PATCH V8 05/14] drm/exynos: dp: support drm_bridge Ajay Kumar
2014-11-15  9:55 ` [PATCH V8 06/14] drm/bridge: ptn3460: support drm_panel Ajay Kumar
2014-11-15  9:55 ` [PATCH V8 07/14] drm/bridge: ptn3460: probe connector at the end of bridge attach Ajay Kumar
2014-11-15  9:55 ` [PATCH V8 08/14] drm/bridge: ptn3460: use gpiod interface Ajay Kumar
2014-11-15  9:55 ` [PATCH V8 09/14] Documentation: drm: bridge: move to video/bridge Ajay Kumar
2014-11-15  9:55 ` [PATCH V8 10/14] Documentation: devicetree: Add vendor prefix for parade Ajay Kumar
2014-11-15  9:55 ` [PATCH V8 11/14] Documentation: bridge: Add documentation for ps8622 DT properties Ajay Kumar
2014-11-15  9:55 ` [PATCH V8 12/14] drm/bridge: Add i2c based driver for ps8622/ps8625 bridge Ajay Kumar
2014-11-15  9:55 ` [PATCH V8 13/14] ARM: dts: snow: represent the connection between bridge and panel using videoport and endpoints Ajay Kumar
2014-11-15  9:55 ` [PATCH V8 14/14] ARM: dts: peach-pit: " Ajay Kumar
2014-11-18  6:20 ` [PATCH V8 00/14] drm/exynos: few patches to enhance bridge chip support Ajay kumar
2014-11-19  9:35   ` Javier Martinez Canillas
2014-11-19  9:38     ` Ajay kumar
2014-11-19  9:51       ` Javier Martinez Canillas
2014-11-19 10:55     ` Paolo Pisati
2014-11-19 11:20       ` Javier Martinez Canillas
2014-11-19 16:22         ` Paolo Pisati
2014-11-19 16:28           ` Javier Martinez Canillas
2014-11-19 16:44             ` Andreas Färber
2014-11-19 19:19       ` Kevin Hilman
2014-12-12  9:51   ` Javier Martinez Canillas
2014-12-15 14:30     ` Tomi Valkeinen
2014-12-15 23:37     ` Laurent Pinchart [this message]
2014-12-17  9:31       ` Javier Martinez Canillas
2014-12-17 11:29         ` Laurent Pinchart
2015-01-02 13:10         ` Daniel Stone
2015-01-02 13:14           ` Ajay kumar
2015-01-02 13:19             ` Daniel Stone
2015-01-03  6:47             ` Inki Dae
2015-01-05 13:50           ` Thierry Reding
     [not found]             ` <20150105135015.GA12010-AwZRO8vwLAwmlAP/+Wk3EA@public.gmane.org>
2015-01-19 10:27               ` Javier Martinez Canillas
2015-01-19 16:30                 ` Thierry Reding
2015-01-19 17:01                   ` Gustavo Padovan
2015-01-19 17:43                     ` Sjoerd Simons
     [not found]                   ` <20150119163043.GB7751-AwZRO8vwLAwmlAP/+Wk3EA@public.gmane.org>
2015-01-19 17:05                     ` Javier Martinez Canillas
2015-01-20 10:56                       ` Ajay kumar
2015-01-20 23:37                       ` 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=3197445.qizQc0zeRb@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=ajaykumar.rs@samsung.com \
    --cc=ajaynumb@gmail.com \
    --cc=bhushan.r@samsung.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=javier.martinez@collabora.co.uk \
    --cc=kgene.kim@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=prashanth.g@samsung.com \
    --cc=seanpaul@google.com \
    --cc=tomi.valkeinen@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox