From: Stefan Agner <stefan@agner.ch>
To: dri-devel@lists.freedesktop.org, thierry.reding@gmail.com
Cc: airlied@linux.ie, daniel.vetter@ffwll.ch,
jianwei.wang.chn@gmail.com, alison.wang@freescale.com,
meng.yi@nxp.com, linux@arm.linux.org.uk, p.zabel@pengutronix.de,
denis@eukrea.com, eric@eukrea.com, ville.syrjala@linux.intel.com,
linux-kernel@vger.kernel.org, manfred.schlaegl@gmx.at,
tomi.valkeinen@ti.com, linux@arm.linux.org.uk,
boris.brezillon@free-electrons.com
Subject: Re: [PATCH v2 0/3] drm: introduce bus_flags for pixel clock polarity
Date: Tue, 23 Feb 2016 15:30:03 -0800 [thread overview]
Message-ID: <653e3f9d2d561a166a1768add0c59422@agner.ch> (raw)
In-Reply-To: <1454968663-30066-1-git-send-email-stefan@agner.ch>
Any comments on this?
Also added Manfred, Tomi and Boris to CC which previously attended in
similar discussions.
Previous discussions:
http://thread.gmane.org/gmane.linux.kernel.api/12830
http://thread.gmane.org/gmane.comp.video.dri.devel/96240/
I think one of the main observation so far was that the pixel clock
polarity is not a property of the mode, and therefor does not fit into
the DRM_MODE_FLAG. This has been pointed out nicely by Russel:
http://thread.gmane.org/gmane.comp.video.dri.devel/96240/focus=96260
Embedded displays connected through parallel bus make use of the
bus_formats field in drm_display_mode. This field defines what kind of
bus format the display requires. This patch follows that idea and adds
bus_flags. bus_flags can be used to define specific bus properties
required by the display, such as pixel clock or data enable polarity...
On 2016-02-08 13:57, Stefan Agner wrote:
> Hi,
>
> This is a new & split out version of the last patch of my
> "drm/fsl-dcu: fixes and enhancements" patchset:
> https://lkml.org/lkml/2015/11/18/949
>
> Instead of using struct drm_display_mode to convey the pixel clock
> polarity information, this patchset introduces a new field called
> bus_flags stored in struct drm_display_info.
Note that this solution has been briefly discussed on IRC:
https://people.freedesktop.org/~cbrill/dri-log/?channel=dri-devel&highlight_names=&date=2016-02-08
--
Stefan
>
> Changes since v1:
> - Introduce bus_flags to convey the pixel clock polarity from
> panel-simple.c to the driver.
>
> Stefan Agner (3):
> drm/fsl-dcu: use mode flags for hsync/vsync polarity
> drm: introduce bus_flags in drm_display_info
> drm/fsl-dcu: use bus_flags for pixel clock polarity
>
> drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c | 16 +++++++++++++---
> drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.h | 4 ++--
> drivers/gpu/drm/panel/panel-simple.c | 6 +++++-
> include/drm/drm_crtc.h | 9 +++++++++
> 4 files changed, 29 insertions(+), 6 deletions(-)
next prev parent reply other threads:[~2016-02-23 23:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 21:57 Stefan Agner
2016-02-08 21:57 ` [PATCH v2 1/3] drm/fsl-dcu: use mode flags for hsync/vsync polarity Stefan Agner
2016-02-25 16:48 ` Thierry Reding
2016-02-25 23:55 ` Stefan Agner
2016-02-08 21:57 ` [PATCH v2 2/3] drm: introduce bus_flags in drm_display_info Stefan Agner
2016-02-08 21:57 ` [PATCH v2 3/3] drm/fsl-dcu: use bus_flags for pixel clock polarity Stefan Agner
2016-02-23 23:30 ` Stefan Agner [this message]
2016-02-24 10:28 ` [PATCH v2 0/3] drm: introduce " Philipp Zabel
2016-02-25 7:59 ` Manfred Schlaegl
2016-02-24 11:06 ` Tomi Valkeinen
2016-02-24 19:02 ` Stefan Agner
2016-02-24 20:17 ` Ville Syrjälä
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=653e3f9d2d561a166a1768add0c59422@agner.ch \
--to=stefan@agner.ch \
--cc=airlied@linux.ie \
--cc=alison.wang@freescale.com \
--cc=boris.brezillon@free-electrons.com \
--cc=daniel.vetter@ffwll.ch \
--cc=denis@eukrea.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@eukrea.com \
--cc=jianwei.wang.chn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=manfred.schlaegl@gmx.at \
--cc=meng.yi@nxp.com \
--cc=p.zabel@pengutronix.de \
--cc=thierry.reding@gmail.com \
--cc=tomi.valkeinen@ti.com \
--cc=ville.syrjala@linux.intel.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
Powered by JetHome