From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Simon Horman <horms@verge.net.au>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-sh@vger.kernel.org, dri-devel@lists.freedesktop.org,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Subject: Re: [PATCH v3 0/9] Renesas R-Car DU HDMI support
Date: Thu, 30 Oct 2014 13:40:34 +0200 [thread overview]
Message-ID: <2727864.n2TjKgUQyN@avalon> (raw)
In-Reply-To: <CAGv-rZm=0rvvnO1cgBp0ZNdu0PvA-nwh6Nk05LSyTE=0vg0ipA@mail.gmail.com>
Hi Simon,
On Thursday 30 October 2014 20:29:22 Simon Horman wrote:
> 2014/10/30 20:05 "Laurent Pinchart" <laurent.pinchart@ideasonboard.com>:
> > On Tuesday 28 October 2014 15:30:05 Dave Airlie wrote:
> >>> The last patch instantiates the HDMI encoder in the Koelsch board DT
> >>> file and connects it to the DU output.
> >>>
> >>> The patch series depends on Koelsch DU DT enablement (scheduled for
> >>> merge in v3.19-rc1). Dave, I'd like to get this merged in v3.19-rc1, how
> >>> would you like to proceed ? Could it go through Simon's Renesas tree ?
> >>> There's a small risk of conflict in drivers/gpu/drm/drm_edid.c,
> >>> include/drm/drm_edid.h, drivers/gpu/drm/i2c/Kconfig and
> >>> drivers/gpu/drm/i2c/Makefile. Simon, could you alternatively provide a
> >>> stable branch with the required dependencies ?
> >>
> >> I'd probably like to take the drm patches into drm-next first, then
> >> maybe get a stable branch from Simon I could use to base the rest on.
> >
> > Simon, I believe that would be the dt-du-for-v3.19 branch of
> > git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git
> >
> > Is it correct ?
>
> Sorry I shuffled things around a bit and what you need should now be in the
> dt-for-v3.19 branch. I hope what is there now is stable. But I'd appreciate
> it if you could wait a few more days.
Sure, no problem. Could you please let me know when I can use it ?
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-10-30 11:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 15:24 [PATCH v3 0/9] Renesas R-Car DU HDMI support Laurent Pinchart
2014-10-26 15:24 ` [PATCH v3 7/9] video: Add ADV751[13] DT bindings documentation Laurent Pinchart
2014-10-28 5:30 ` [PATCH v3 0/9] Renesas R-Car DU HDMI support Dave Airlie
2014-10-30 11:05 ` Laurent Pinchart
2014-10-30 11:29 ` Simon Horman
2014-10-30 11:40 ` Laurent Pinchart [this message]
2014-10-31 8:18 ` Simon Horman
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=2727864.n2TjKgUQyN@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=horms@verge.net.au \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-sh@vger.kernel.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 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).