From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] i.MX53 IPU + TVE patches
Date: Fri, 21 Jun 2013 10:27:37 +0200 [thread overview]
Message-ID: <1371803259-18369-1-git-send-email-p.zabel@pengutronix.de> (raw)
Hi,
converting the IPU IRQ handling to use irq_domain_add_linear is listed in
drivers/staging/imx-drm/TODO as one of the tasks to be done before the IPU
driver can be moved out of staging. These patches fix the number IPU_NUM_IRQS
and add a linear irq domain.
regards
Philipp
---
drivers/staging/imx-drm/TODO | 1 -
drivers/staging/imx-drm/ipu-v3/ipu-common.c | 66 +++++++++++++++++++----------
drivers/staging/imx-drm/ipu-v3/ipu-prv.h | 4 +-
3 files changed, 45 insertions(+), 26 deletions(-)
next reply other threads:[~2013-06-21 8:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 8:27 Philipp Zabel [this message]
2013-06-21 8:27 ` [PATCH 1/2] staging: drm/imx: fix number of IPU IRQs Philipp Zabel
2013-06-21 8:27 ` [PATCH 2/2] staging: drm/imx: convert IPU irq driver to irq_domain_add_linear Philipp Zabel
2013-06-21 8:40 ` [PATCH 0/2] i.MX53 IPU + TVE patches Philipp Zabel
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=1371803259-18369-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).