From: Anatolij Gustschin <agust@denx.de>
To: linuxppc-dev@ozlabs.org
Cc: linux-fbdev@vger.kernel.org, wd@denx.de, dzu@denx.de,
devicetree-discuss@lists.ozlabs.org, yorksun@freescale.com
Subject: [PATCH 0/5] Rework MPC5121 DIU support (for 2.6.35)
Date: Fri, 30 Apr 2010 01:49:33 +0200 [thread overview]
Message-ID: <1272584978-19063-1-git-send-email-agust@denx.de> (raw)
This patch series rework DIU support patches submitted
previously. Comments to the previos patch series have
been addressed, not related changes are dropped and some
changes are split out to separate patches to simplify
review. Furthermore a patch has been added to support
setting display mode using EDID block in the device tree.
Anatolij Gustschin (5):
fsl-diu-fb: fix issue with re-enabling DIU area descriptor on MPC5121
fsl-diu-fb: move fsl-diu-fb.h to include/linux
powerpc/mpc5121: shared DIU framebuffer support
powerpc: doc/dts-bindings: update doc of FSL DIU bindings
fsl-diu-fb: Support setting display mode using EDID
Documentation/powerpc/dts-bindings/fsl/diu.txt | 20 ++-
arch/powerpc/platforms/512x/mpc5121_ads.c | 7 +
arch/powerpc/platforms/512x/mpc5121_generic.c | 12 +
arch/powerpc/platforms/512x/mpc512x.h | 2 +
arch/powerpc/platforms/512x/mpc512x_shared.c | 284 ++++++++++++++++++++++++
arch/powerpc/sysdev/fsl_soc.h | 1 +
drivers/video/Kconfig | 1 +
drivers/video/fsl-diu-fb.c | 104 ++++++++-
{drivers/video => include/linux}/fsl-diu-fb.h | 0
9 files changed, 419 insertions(+), 12 deletions(-)
rename {drivers/video => include/linux}/fsl-diu-fb.h (100%)
next reply other threads:[~2010-04-29 23:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 23:49 Anatolij Gustschin [this message]
2010-04-29 23:49 ` [PATCH 1/5] fsl-diu-fb: fix issue with re-enabling DIU area descriptor on MPC5121 Anatolij Gustschin
2010-04-29 23:49 ` [PATCH 2/5] fsl-diu-fb: move fsl-diu-fb.h to include/linux Anatolij Gustschin
2010-04-29 23:49 ` [PATCH 3/5] powerpc/mpc5121: shared DIU framebuffer support Anatolij Gustschin
2010-04-30 2:05 ` Timur Tabi
2010-04-30 10:19 ` Anatolij Gustschin
2010-04-30 15:08 ` Timur Tabi
2010-04-30 16:22 ` Scott Wood
2010-04-30 18:18 ` Timur Tabi
2010-04-30 20:40 ` Scott Wood
2010-05-01 15:15 ` Anatolij Gustschin
2010-04-30 17:00 ` Anatolij Gustschin
2010-04-30 18:29 ` Timur Tabi
2010-04-30 10:40 ` [PATCH v2 " Anatolij Gustschin
2010-05-03 10:49 ` [PATCH v3 " Anatolij Gustschin
2010-04-29 23:49 ` [PATCH 4/5] powerpc: doc/dts-bindings: update doc of FSL DIU bindings Anatolij Gustschin
2010-04-29 23:49 ` [PATCH 5/5] fsl-diu-fb: Support setting display mode using EDID Anatolij Gustschin
2010-04-30 1:44 ` Timur Tabi
2010-04-30 7:43 ` Anatolij Gustschin
2010-04-30 8:09 ` [PATCH v2 " Anatolij Gustschin
2010-04-30 1:39 ` [PATCH 0/5] Rework MPC5121 DIU support (for 2.6.35) Timur Tabi
2010-04-30 7:41 ` Anatolij Gustschin
2010-06-01 9:38 ` Anatolij Gustschin
2010-06-04 15:46 ` Timur Tabi
2010-06-16 7:38 ` Anatolij Gustschin
2010-06-16 15:42 ` Timur Tabi
2010-06-16 15:47 ` Anatolij Gustschin
2010-06-16 16:26 ` Timur Tabi
2010-06-16 17:34 ` Wolfram Sang
2010-06-16 20:00 ` Anatolij Gustschin
2010-06-22 16:29 ` Timur Tabi
2010-06-22 22:03 ` Anatolij Gustschin
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=1272584978-19063-1-git-send-email-agust@denx.de \
--to=agust@denx.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dzu@denx.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=wd@denx.de \
--cc=yorksun@freescale.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).