From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v3 0/9] DU DT support for Marzen, Lager and Koelsch
Date: Mon, 27 Oct 2014 00:09:04 +0000 [thread overview]
Message-ID: <20141027000901.GA25692@verge.net.au> (raw)
In-Reply-To: <1411564828-30272-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
On Fri, Oct 24, 2014 at 03:04:49PM +0300, Laurent Pinchart wrote:
> Hi Simon,
>
> On Friday 24 October 2014 16:20:24 Simon Horman wrote:
> > On Fri, Oct 24, 2014 at 02:09:43PM +0900, Simon Horman wrote:
> > > On Wed, Sep 24, 2014 at 04:20:19PM +0300, Laurent Pinchart wrote:
> > > > Hello,
> > > >
> > > > This patch series enable the DU device in DT for the Marzen, Lager and
> > > > Koelsch boards (in their multiplatform implementation only).
> > > >
> > > > Compared to v2,
> > > >
> > > > - the Marzen and Lager adv7123 DT nodes have been renamed to vga-encoder
> > > >
> > > > - the Marzen and Lager adv7123 DT nodes now correctly set the "reg"
> > > > property in their port subnodes.
> > > >
> > > > Compared to v1,
> > > >
> > > > - support for the external LVDS panel commonly used with the three
> > > > boards has been moved to a separate file (r8a77xx-aa104xd12-panel.dtsi)
> > > > that can be included at the end of the Marzen, Lager or Koelsch DTS
> > > >
> > > > - the DU DT nodes have been renamed to "display"
> > > >
> > > > - the s/remote/remove/ typo has been fixed in commit messages.
> > > >
> > > > The first three patches add the DU nodes to the SoC .dtsi files. Patch
> > > > 04 adds the panel .dtsi. Patches 05 enables the DU device in DT for the
> > > > Marzen board, and patches 06 to 09 perform the same operation for the
> > > > Lager and Koelsch boards, removing the C code DU platform device in the
> > > > process.
> > > >
> > > > Please note that HDMI output isn't supported yet, another patch set will
> > > > come in the next few days.
> > > >
> > > > The patches are based on top of the DU changes from the "[PATCH 00/16]
> > > > R-Car Display Unit DT bindings" series that will be merged in v3.18.
> > > > This series is thus targeted at v3.19. Fast-tracking it to v3.18 is
> > > > still possible if desired, in which case I would need to ask Dave
> > > > Airlie to provide a stable branch with the driver changes. The clock is
> > > > ticking, if anyone would like DU DT in v3.18, speak now or forever hold
> > > > your peace.
> > > >
> > > > I've pushed a test branch that includes all patches to
> > > >
> > > > git://linuxtv.org/pinchartl/fbdev.git drm/du/dt
> > >
> > > Thanks for this, I'm very happy to see these changes.
> > >
> > > Now that v3.18-rc1 is part of my devel tree could you consider
> > > rebasing these patches?
>
> Done.
Thanks.
> > If it is appropriate could you also consider an shmobile_defconfig
> > update to accompany this series.
>
> The rcar-du-drm driver is already enabled in shmobile_defconfig.
Thanks, got it.
prev parent reply other threads:[~2014-10-27 0:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 13:20 [PATCH v3 0/9] DU DT support for Marzen, Lager and Koelsch Laurent Pinchart
2014-10-24 5:09 ` Simon Horman
2014-10-24 7:20 ` Simon Horman
2014-10-24 12:04 ` Laurent Pinchart
2014-10-27 0:09 ` Simon Horman [this message]
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=20141027000901.GA25692@verge.net.au \
--to=horms@verge.net.au \
--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).