From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Paolo Pisati <p.pisati@gmail.com>
Cc: Ajay kumar <ajaynumb@gmail.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Ajay Kumar <ajaykumar.rs@samsung.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
InKi Dae <inki.dae@samsung.com>,
Kukjin Kim <kgene.kim@samsung.com>,
Sean Paul <seanpaul@google.com>,
Thierry Reding <thierry.reding@gmail.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Pannaga Bhushan Reddy Patel <bhushan.r@samsung.com>,
Prashanth G <prashanth.g@samsung.com>,
gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: Re: [PATCH V8 00/14] drm/exynos: few patches to enhance bridge chip support
Date: Wed, 19 Nov 2014 17:28:54 +0100 [thread overview]
Message-ID: <546CC546.5090900@collabora.co.uk> (raw)
In-Reply-To: <20141119162224.GB5396@luxor.wired.org>
Hello Paolo,
On 11/19/2014 05:22 PM, Paolo Pisati wrote:
> On Wed, Nov 19, 2014 at 12:20:53PM +0100, Javier Martinez Canillas wrote:
>>
>> If someone else is interested, I've pushed a branch [0] with 3.18-rc5 + all
>> the needed patches.
>>
>> Ajay, feel free to add to your series:
>>
>> Tested-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
>>
>> Best regards,
>> Javier
>>
>> [0]: git://git.collabora.co.uk/git/user/javier/linux.git wip/exynos/dp-integ
>
> doesn't peach pi require the same dts modification as peach pit/snow?
>
No, because the Peach Pit and Snow have an eDP to LVDS bridge chip but the
Peach Pi does not have a bridge. Ajay's series is to add DRM bridge support
to Exynos Display Port driver and so is only relevant to Snow and Pit.
Best regards,
Javier
next prev parent reply other threads:[~2014-11-19 16:28 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 [this message]
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
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=546CC546.5090900@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--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=gustavo.padovan@collabora.co.uk \
--cc=inki.dae@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=p.pisati@gmail.com \
--cc=prashanth.g@samsung.com \
--cc=seanpaul@google.com \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).