SUPERH platform development
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	linux-sh@vger.kernel.org, dri-devel@lists.freedesktop.org,
	magnus.damm@gmail.com
Subject: Re: [PATCH 0/3] R-Car Display Unit DRM driver
Date: Fri, 01 Feb 2013 03:26:41 +0000	[thread overview]
Message-ID: <20130201032641.GC15639@verge.net.au> (raw)
In-Reply-To: <226620406.loYPPLmWhQ@avalon>

On Fri, Feb 01, 2013 at 04:15:31AM +0100, Laurent Pinchart wrote:
> Hi Simon,
> 
> On Thursday 31 January 2013 15:38:38 Simon Horman wrote:
> > On Thu, Jan 31, 2013 at 02:45:00AM +0100, Laurent Pinchart wrote:
> > > Hello,
> > > 
> > > Here's a new DRM driver for the Renesas R-Car Display Unit (DU).
> > > 
> > > The DU features two superposition processors (modeled as CRTCs) and eight
> > > planes that can be shared between the superposition processors.
> > > 
> > > The driver supports the superposition processors (currently in pure
> > > overlay mode without alpha blending), all eight planes and all hardware
> > > supported formats except 8-bit indexed color more and 32-bit RGB666 mode
> > > (that would be [31:0] x:R:x:G:x:B:x 8:6:2:6:2:6:2 little endian, not
> > > supported by DRM at the moment).
> > > 
> > > On the output side only sync master non-interlaced modes are currently
> > > supported. Only the VGA output has been tested, as I lack an LVDS panel
> > > for the development board. The second CRTC hasn't been tested for the same
> > > reason.
> > > 
> > > Platform data are subject to change with the common display framework.
> > > This is why I haven't implemented DT bindings yet.
> > > 
> > > Laurent Pinchart (2):
> > >   drm: Renesas R-Car Display Unit DRM driver
> > >   ARM: shmobile: marzen: Add Display Unit support
> > 
> > I assume that the above patch is dependent on the other two patches in the
> > series. If so please let me know how you would like to handle the merge.
> 
> It would probably easier to push everything through your tree, as the only 
> risk of conflict in the DRM patch is in Kconfig/Makefile. I'll first give time 
> to reviewers anway.

That is fine by me.

      reply	other threads:[~2013-02-01  3:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31  1:45 [PATCH 0/3] R-Car Display Unit DRM driver Laurent Pinchart
2013-01-31  1:45 ` [PATCH 1/3] r8a7779: Add Display Unit clock support Laurent Pinchart
2013-01-31  6:35   ` Simon Horman
2013-01-31 10:14     ` Laurent Pinchart
2013-02-01  0:06       ` Simon Horman
2013-02-07  2:20       ` Simon Horman
2013-03-12 15:08   ` Laurent Pinchart
2013-03-12 15:52   ` Simon Horman
2013-01-31  1:45 ` [PATCH 2/3] drm: Renesas R-Car Display Unit DRM driver Laurent Pinchart
2013-02-07  2:15   ` Simon Horman
2013-02-07 12:53     ` Laurent Pinchart
2013-02-07  7:32   ` Simon Horman
2013-02-07  8:23     ` Kuninori Morimoto
2013-02-07 16:08       ` Laurent Pinchart
2013-02-13 12:28   ` Simon Horman
2013-02-13 18:18     ` Laurent Pinchart
2013-02-14  0:40       ` Simon Horman
2013-01-31  1:45 ` [PATCH 3/3] ARM: shmobile: marzen: Add Display Unit support Laurent Pinchart
2013-02-07  4:27   ` Kuninori Morimoto
2013-02-07 12:51     ` Laurent Pinchart
2013-02-08  0:17       ` Kuninori Morimoto
2013-01-31  6:38 ` [PATCH 0/3] R-Car Display Unit DRM driver Simon Horman
2013-02-01  3:15   ` Laurent Pinchart
2013-02-01  3:26     ` 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=20130201032641.GC15639@verge.net.au \
    --to=horms@verge.net.au \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.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