From: Doug Anderson <dianders@chromium.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: "Ajay kumar" <ajaynumb@gmail.com>,
"Ajay Kumar" <ajaykumar.rs@samsung.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Vincent Palatin" <vpalatin@chromium.org>,
"InKi Dae" <inki.dae@samsung.com>,
"Sean Paul" <seanpaul@google.com>,
"Rob Clark" <robdclark@gmail.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Thierry Reding" <thierry.reding@gmail.com>,
"sunil joshi" <joshi@samsung.com>,
"Prashanth G" <prashanth.g@samsung.com>,
"Stéphane Marchesin" <marcheu@chromium.org>,
"Rahul Sharma" <rahul.sharma@samsung.com>
Subject: Re: [PATCH V4 00/10] drm: exynos: few patches to enhance bridge chip support
Date: Mon, 7 Jul 2014 13:27:20 -0700 [thread overview]
Message-ID: <CAD=FV=VwJM9ReuZAEPc+1hv_GaF5r497bFDZR59ukE++sRYaNw@mail.gmail.com> (raw)
In-Reply-To: <53B6A6F0.1070108@suse.de>
Andreas,
On Fri, Jul 4, 2014 at 6:06 AM, Andreas Färber <afaerber@suse.de> wrote:
>> Doug can help you in adding changes required for tps65090.
>
> Hm, Doug had pointed out an issue with tps65090 in my v1, so I dropped
> it: https://patchwork.kernel.org/patch/4397321/
tps65090 on Spring is nowhere near obvious due to the EC commands that
were available during the Spring timeframe. See
http://crbug.com/391797 for some details.
-Doug
next prev parent reply other threads:[~2014-07-07 20:27 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 18:26 [PATCH V4 00/10] drm: exynos: few patches to enhance bridge chip support Ajay Kumar
2014-06-11 18:26 ` [PATCH V4 01/10] drm/exynos: Move DP setup out of hotplug workqueue Ajay Kumar
2014-06-20 8:07 ` Ajay kumar
2014-06-11 18:27 ` [PATCH V4 02/10] drm/panel: add prepare and unprepare routines Ajay Kumar
2014-06-20 8:07 ` Ajay kumar
2014-06-11 18:27 ` [PATCH V4 03/10] drm/exynos: dp: modify driver to support drm_panel Ajay Kumar
2014-06-20 8:08 ` Ajay kumar
2014-06-11 18:27 ` [PATCH V4 04/10] drm/panel: Add driver for lvds/edp based panels Ajay Kumar
2014-06-20 8:07 ` Ajay kumar
[not found] ` <1402511228-18945-5-git-send-email-ajaykumar.rs-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-06-23 15:30 ` Javier Martinez Canillas
2014-06-24 8:18 ` Ajay kumar
2014-06-23 16:55 ` Christian Gmeiner
2014-06-24 8:22 ` Ajay kumar
2014-06-11 18:27 ` [PATCH V4 05/10] drm/bridge: add helper functions to support bridge chain Ajay Kumar
2014-06-20 8:07 ` Ajay kumar
2014-06-11 18:27 ` [PATCH V4 06/10] drm/bridge: Add a driver which binds drm_bridge with drm_panel Ajay Kumar
[not found] ` <1402511228-18945-7-git-send-email-ajaykumar.rs-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-06-20 8:08 ` Ajay kumar
2014-06-11 18:27 ` [PATCH V4 07/10] drm/bridge: ptn3460: Support bridge chaining Ajay Kumar
2014-06-20 8:09 ` Ajay kumar
2014-06-11 18:27 ` [PATCH V4 08/10] drm/exynos: dp: create bridge chain using ptn3460 and panel_binder Ajay Kumar
2014-06-20 8:09 ` Ajay kumar
2014-06-11 18:27 ` [PATCH V4 09/10] drm/bridge: Add ps8622/ps8625 bridge driver Ajay Kumar
2014-06-20 8:09 ` Ajay kumar
2014-06-23 16:05 ` Javier Martinez Canillas
2014-06-24 8:15 ` Ajay kumar
2014-06-11 18:27 ` [PATCH V4 10/10] drm/exynos: Add ps8622 lvds bridge discovery to DP driver Ajay Kumar
2014-06-20 8:09 ` Ajay kumar
2014-06-20 8:06 ` [PATCH V4 00/10] drm: exynos: few patches to enhance bridge chip support Ajay kumar
2014-06-20 15:51 ` Inki Dae
2014-06-23 13:58 ` Rahul Sharma
2014-06-23 14:38 ` Tomasz Figa
2014-06-24 3:25 ` Rahul Sharma
2014-06-23 16:15 ` Javier Martinez Canillas
2014-07-03 5:19 ` Andreas Färber
2014-07-03 14:55 ` Ajay kumar
2014-07-04 13:06 ` Andreas Färber
2014-07-07 20:27 ` Doug Anderson [this message]
2014-07-07 20:46 ` Doug Anderson
2014-07-09 6:11 ` Ajay kumar
2014-07-14 17:22 ` Olof Johansson
2014-07-15 5:37 ` Inki Dae
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='CAD=FV=VwJM9ReuZAEPc+1hv_GaF5r497bFDZR59ukE++sRYaNw@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=afaerber@suse.de \
--cc=ajaykumar.rs@samsung.com \
--cc=ajaynumb@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=joshi@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=marcheu@chromium.org \
--cc=prashanth.g@samsung.com \
--cc=rahul.sharma@samsung.com \
--cc=robdclark@gmail.com \
--cc=seanpaul@google.com \
--cc=thierry.reding@gmail.com \
--cc=vpalatin@chromium.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: 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.