linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v14 06/10] drm: drm_display_mode: add signal polarity flags
Date: Wed, 25 Jun 2014 00:13:19 +0200	[thread overview]
Message-ID: <20140624221318.GA30183@mithrandir> (raw)
In-Reply-To: <20140624145745.GR32514@n2100.arm.linux.org.uk>

On Tue, Jun 24, 2014 at 03:57:46PM +0100, Russell King - ARM Linux wrote:
> On Mon, Jun 16, 2014 at 12:11:20PM +0200, Denis Carikli wrote:
> > We need a way to pass signal polarity informations
> >   between DRM panels, and the display drivers.
> > 
> > To do that, a pol_flags field was added to drm_display_mode.
> > 
> > Signed-off-by: Denis Carikli <denis@eukrea.com>
> 
> This patch needs an ack from the DRM people - can someone review it
> please?  This series has now been round 14 revisions and it's about
> time it was properly reviewed - or a statement made if it's
> unacceptable.

I didn't follow all of the earlier discussions around this, but it seems
to me like data-enable polarity and the pixel data edge flags are
properties of the interface rather than the video mode.

struct drm_display_mode represents the video timings and I'm not sure if
it's a good idea to extend it with this type of information.

Maybe we need to add a separate type of device to store these parameters
(much like we've done for MIPI DSI devices).

Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140625/400d1e9e/attachment.sig>

  reply	other threads:[~2014-06-24 22:13 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16 10:11 [PATCH v14 01/10] [media] v4l2: add new V4L2_PIX_FMT_RGB666 pixel format Denis Carikli
2014-06-16 10:11 ` [PATCH v14 02/10] imx-drm: Add RGB666 support for parallel display Denis Carikli
2014-06-16 10:15   ` Russell King - ARM Linux
2014-06-16 10:11 ` [PATCH v14 03/10] imx-drm: Correct BGR666 and the board's dts that use them Denis Carikli
2014-06-16 10:15   ` Russell King - ARM Linux
2014-06-16 10:11 ` [PATCH v14 04/10] imx-drm: use defines for clock polarity settings Denis Carikli
2014-06-24 15:13   ` Russell King - ARM Linux
2014-06-24 16:25     ` Denis Carikli
2014-06-24 16:35       ` Russell King - ARM Linux
2014-06-25  4:48   ` Sascha Hauer
2014-06-25  8:43     ` Russell King - ARM Linux
2014-06-25  9:46       ` Sascha Hauer
2014-06-25  9:44     ` Denis Carikli
2014-06-26 20:56       ` Russell King - ARM Linux
2014-06-27 14:17         ` [PATCH v14 updated] " Denis Carikli
2014-06-16 10:11 ` [PATCH v14 05/10] ARM: dts: imx5*, imx6*: correct display-timings nodes Denis Carikli
2014-06-24 15:01   ` Russell King - ARM Linux
2014-06-25  2:29     ` Shawn Guo
2014-06-16 10:11 ` [PATCH v14 06/10] drm: drm_display_mode: add signal polarity flags Denis Carikli
2014-06-24 14:57   ` Russell King - ARM Linux
2014-06-24 22:13     ` Thierry Reding [this message]
2014-06-16 10:11 ` [PATCH v14 07/10] imx-drm: Use drm_display_mode timings flags Denis Carikli
2014-06-25  9:20   ` Russell King - ARM Linux
2014-06-16 10:11 ` [PATCH v14 08/10] drm/panel: Add Eukrea mbimxsd51 displays Denis Carikli
2014-06-24 15:06   ` Russell King - ARM Linux
2014-06-24 19:52     ` Rob Herring
2014-06-24 21:56       ` Thierry Reding
2014-06-25  9:42     ` Denis Carikli
2014-06-24 21:49   ` Thierry Reding
2014-06-24 21:56     ` Eric Bénard
2014-06-24 22:04       ` Thierry Reding
2014-06-25  8:27         ` Denis Carikli
2014-06-16 10:11 ` [PATCH v14 09/10] ARM: dts: mbimx51sd: Add display support Denis Carikli
2014-06-16 12:29   ` Denis Carikli
2014-06-17 13:46     ` Denis Carikli
2014-06-16 10:11 ` [PATCH v14 10/10] ARM: dts: mbimx51sd: Add CMO-QVGA backlight support Denis Carikli
2014-06-16 10:14 ` [PATCH v14 01/10] [media] v4l2: add new V4L2_PIX_FMT_RGB666 pixel format Russell King - ARM Linux

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=20140624221318.GA30183@mithrandir \
    --to=thierry.reding@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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).