From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] IPU DMFC bandwidth allocation fix and cleanups
Date: Fri, 21 Jun 2013 10:57:17 +0200 [thread overview]
Message-ID: <1371805041-9299-1-git-send-email-p.zabel@pengutronix.de> (raw)
Hi,
the following patches remove some unused variables, replace some
hard-coded channel numbers with existing descriptive defines, fix
the DMFC bandwidth (or rather: FIFO space) allocation, and update
ipu_page_flip() to immediately set crtc->fb.
regards
Philipp
---
drivers/staging/imx-drm/imx-drm-core.c | 3 ---
drivers/staging/imx-drm/ipu-v3/ipu-dmfc.c | 22 ++++++++++++++++------
drivers/staging/imx-drm/ipuv3-crtc.c | 7 +------
3 files changed, 17 insertions(+), 15 deletions(-)
next reply other threads:[~2013-06-21 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 8:57 Philipp Zabel [this message]
2013-06-21 8:57 ` [PATCH 1/4] staging: drm/imx: remove unused variables Philipp Zabel
2013-06-21 8:57 ` [PATCH 2/4] staging: drm/imx: ipu-dmfc: fix bandwidth allocation Philipp Zabel
2013-06-21 8:57 ` [PATCH 3/4] staging: drm/imx: ipuv3-crtc: immediately update crtc->fb in ipu_page_flip Philipp Zabel
2013-06-21 8:57 ` [PATCH 4/4] staging: drm/imx: ipu-dmfc: use defines for ipu channel numbers Philipp Zabel
2013-06-24 19:42 ` [PATCH 0/4] IPU DMFC bandwidth allocation fix and cleanups Sascha Hauer
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=1371805041-9299-1-git-send-email-p.zabel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--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).