linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 07/12] drm: drm_display_mode: add signal polarity flags
Date: Mon, 17 Mar 2014 16:44:26 +0100	[thread overview]
Message-ID: <2777667.XJdaUSpRsD@avalon> (raw)
In-Reply-To: <20140317161436.06169b33@ipc1.ka-ro>

Hi Lothar,

On Monday 17 March 2014 16:14:36 Lothar Wa?mann wrote:
> Laurent Pinchart wrote:
> > On Monday 17 March 2014 14:41:09 Andrzej Hajda wrote:
> > > On 03/13/2014 06:17 PM, 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>
> > > > ---
> > > > ChangeLog v10->v11:
> > > > - Since the imx-drm won't be able to retrive its regulators
> > > > 
> > > >   from the device tree when using display-timings nodes,
> > > >   and that I was told that the drm simple-panel driver
> > > >   already supported that, I then, instead, added what was
> > > >   lacking to make the eukrea displays work with the
> > > >   drm-simple-panel driver.
> > > >   
> > > >   That required a way to get back the display polarity
> > > >   informations from the imx-drm driver without affecting
> > > >   userspace.
> > > > 
> > > > ---
> > > > 
> > > >  include/drm/drm_crtc.h |    8 ++++++++
> > > >  1 file changed, 8 insertions(+)
> > > > 
> > > > diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h
> > > > index f764654..61a4fe1 100644
> > > > --- a/include/drm/drm_crtc.h
> > > > +++ b/include/drm/drm_crtc.h
> > > > @@ -131,6 +131,13 @@ enum drm_mode_status {
> > > > 
> > > >  #define DRM_MODE_FLAG_3D_MAX	DRM_MODE_FLAG_3D_SIDE_BY_SIDE_HALF
> > > > 
> > > > +#define DRM_MODE_FLAG_POL_PIXDATA_NEGEDGE	BIT(1)
> > > > +#define DRM_MODE_FLAG_POL_PIXDATA_POSEDGE	BIT(2)
> > > > +#define DRM_MODE_FLAG_POL_PIXDATA_PRESERVE	BIT(3)
> > > > +#define DRM_MODE_FLAG_POL_DE_NEGEDGE		BIT(4)
> > > > +#define DRM_MODE_FLAG_POL_DE_POSEDGE		BIT(5)
> > > > +#define DRM_MODE_FLAG_POL_DE_PRESERVE		BIT(6)
> > > 
> > > Could you add some description to these flags.
> > > What are *_PRESERVE flags for?
> > > Are those flags 1:1 compatible with respective 'videomode:flags'?
> > > I guess DE flags should be rather DRM_MODE_FLAG_POL_DE_(LOW|HIGH), am I
> > > right?
> > 
> > Possibly nitpicking, I wouldn't call the clock edge on which data signals
> > are generated/sampled "data polarity". This is clock polarity
> > information.
> > 
> > Have you seen cases where pixel data and DE are geenrated or need to be
> > sampled on different edges ?
> 
> DE is not a clock signal, but an 'Enable' signal whose value (high or
> low) defines the window in which the pixel data is valid.
> The flag defines whether data is valid during the HIGH or LOW period of
> DE.

The DRM_MODE_FLAG_POL_DE_(LOW|HIGH) do, by my impression of the proposed new 
DRM_MODE_FLAG_POL_DE_*EDGE flags is that they define sampling clock edges, not 
active levels.

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2014-03-17 15:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13 17:17 [PATCH v11][ 01/12] [media] v4l2: add new V4L2_PIX_FMT_RGB666 pixel format Denis Carikli
2014-03-13 17:17 ` [PATCH v11][ 02/12] imx-drm: Add RGB666 support for parallel display Denis Carikli
2014-03-13 17:17 ` [PATCH v11][ 03/12] imx-drm: Correct BGR666 and the board's dts that use them Denis Carikli
2014-03-13 17:17 ` [PATCH v11][ 04/12] imx-drm: Match ipu_di_signal_cfg's clk_pol with its description Denis Carikli
2014-03-13 17:17 ` [PATCH v11][ 05/12] imx-drm: use defines for clock polarity settings Denis Carikli
2014-03-13 17:17 ` [PATCH v11][ 06/12] ARM: dts: imx5*, imx6*: correct display-timings nodes Denis Carikli
2014-03-13 17:17 ` [PATCH 07/12] drm: drm_display_mode: add signal polarity flags Denis Carikli
2014-03-17 13:41   ` Andrzej Hajda
2014-03-17 13:58     ` Laurent Pinchart
2014-03-17 15:14       ` Lothar Waßmann
2014-03-17 15:44         ` Laurent Pinchart [this message]
2014-03-18  7:50           ` Lothar Waßmann
2014-03-18  9:30             ` Russell King - ARM Linux
2014-03-18 12:41             ` Laurent Pinchart
2014-03-18 12:56               ` Russell King - ARM Linux
2014-03-18 13:05                 ` Laurent Pinchart
2014-03-18 13:05               ` Lothar Waßmann
2014-03-13 17:17 ` [PATCH 08/12] imx-drm: Use drm_display_mode timings flags Denis Carikli
2014-03-18 13:04   ` Lothar Waßmann
2014-03-13 17:17 ` [PATCH 09/12] drm/panel: Add Eukrea mbimxsd51 displays Denis Carikli
2014-03-13 17:17 ` [PATCH 10/12] ARM: dts: mbimx51sd: Add display support Denis Carikli
2014-03-13 17:17 ` [PATCH 11/12] ARM: dts: mbimx51sd: Add CMO-QVGA backlight support Denis Carikli
2014-03-13 17:17 ` [PATCH 12/12] ARM: imx_v6_v7_defconfig: Add more drm drivers Denis Carikli

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=2777667.XJdaUSpRsD@avalon \
    --to=laurent.pinchart@ideasonboard.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).