linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Dave Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org,
	Thierry Reding <thierry.reding@gmail.com>,
	linux-kernel@vger.kernel.org,
	Mauro Carvalho Chehab <m.chehab@samsung.com>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	linux-media@vger.kernel.org,
	Nicolas Ferre <nicolas.ferre@atmel.com>
Subject: Re: [PATCH v3 0/3] drm: describe display bus format
Date: Sun, 30 Nov 2014 13:40:08 +0100	[thread overview]
Message-ID: <20141130134008.4471abdd@bbrezillon> (raw)
In-Reply-To: <7292023.aOo0xYF6kL@avalon>

Hi Laurent,

On Sat, 29 Nov 2014 00:29:10 +0200
Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote:

> Hi Boris,
> 
> On Thursday 27 November 2014 14:37:50 Boris Brezillon wrote:
> > On Tue, 18 Nov 2014 14:46:17 +0100 Boris Brezillon wrote:
> > > Hello,
> > > 
> > > This series makes use of the MEDIA_BUS_FMT definition to describe how
> > > the data are transmitted to the display.
> > > 
> > > This will allow drivers to configure their output display bus according
> > > to the display capabilities.
> > > For example some display controllers support DPI (or raw RGB) connectors
> > > and need to specify which format will be transmitted on the DPI bus
> > > (RGB444, RGB565, RGB888, ...).
> > > 
> > > This series also adds a field to the panel_desc struct so that one
> > > can specify which format is natevely supported by a panel.
> > 
> > Thierry, Laurent, Dave, can you take a look at this patch series: this
> > is the last missing dependency to get the atmel-hlcdc DRM driver
> > mainlined, and I was expecting to get this driver in 3.19...
> 
> I've reviewed the series, it looks globally fine to me. I just had two small 
> comments on patch 1/3.
> 

Thanks for the review, I'll address your comments in the next version.

Regards,

Boris

-- 
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      reply	other threads:[~2014-11-30 12:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18 13:46 [PATCH v3 0/3] drm: describe display bus format Boris Brezillon
2014-11-18 13:46 ` [PATCH v3 1/3] drm: add bus_formats and nbus_formats fields to drm_display_info Boris Brezillon
2014-11-28 22:13   ` Laurent Pinchart
2014-11-30 12:39     ` Boris Brezillon
2014-11-18 13:46 ` [PATCH v3 2/3] drm: panel: simple-panel: add support for bus_format retrieval Boris Brezillon
2014-11-18 13:46 ` [PATCH v3 3/3] drm: panel: simple-panel: add bus format information for foxlink panel Boris Brezillon
2014-11-27 13:37 ` [PATCH v3 0/3] drm: describe display bus format Boris Brezillon
2014-11-28 22:29   ` Laurent Pinchart
2014-11-30 12:40     ` Boris Brezillon [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=20141130134008.4471abdd@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hans.verkuil@cisco.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=nicolas.ferre@atmel.com \
    --cc=thierry.reding@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;
as well as URLs for NNTP newsgroup(s).