From: Stefan Agner <stefan@agner.ch>
To: dri-devel@lists.freedesktop.org, thierry.reding@gmail.com
Cc: meng.yi@nxp.com, linux@arm.linux.org.uk, eric@eukrea.com,
alison.wang@freescale.com, daniel.vetter@ffwll.ch,
linux-kernel@vger.kernel.org, denis@eukrea.com
Subject: [PATCH v2 0/3] drm: introduce bus_flags for pixel clock polarity
Date: Mon, 8 Feb 2016 13:57:40 -0800 [thread overview]
Message-ID: <1454968663-30066-1-git-send-email-stefan@agner.ch> (raw)
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.
--
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(-)
--
2.7.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-02-08 21:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 21:57 Stefan Agner [this message]
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 ` [PATCH v2 0/3] drm: introduce " Stefan Agner
2016-02-24 10:28 ` 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=1454968663-30066-1-git-send-email-stefan@agner.ch \
--to=stefan@agner.ch \
--cc=alison.wang@freescale.com \
--cc=daniel.vetter@ffwll.ch \
--cc=denis@eukrea.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@eukrea.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=meng.yi@nxp.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).