From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: linux-fbdev-devel@lists.sourceforge.net, adaplas@gmail.com,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-arm-kernel@lists.arm.linux.org.uk,
Dan Williams <dan.j.williams@intel.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH 0/4 v6] i.MX31: dmaengine and framebuffer drivers
Date: Fri, 26 Dec 2008 18:11:13 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0812261714290.4895@axis700.grange> (raw)
Hi,
This is version 6 of dmaengine and framebuffer drivers for i.MX31.
Changes since version 5: as requested by Sascha Hauer switched to dynamic
IPU IRQ mapping. Instead of statically allocating 137 irq_desc[] elements,
I provide a configuration variable to specify how many interrupt slots
should be allocated. The default value is 4, minimum 2, maximum 137. Then
these slots are used to dynamically map interrupts upon user requests to
available IRQ numbers. Also removed all traces of overlay framebuffer, and
removed bogus use of nonstd field from the framebuffer driver, as
requested by Geert Uytterhoeven. Thanks to all who commented.
Changes since version 4: addressed comments from Sascha Hauer, apart from:
the idmac driver still uses two locks - a mutex and a spinlock, the "ugly"
construction like "to_ipu(to_idmac(ichan->dma_chan.device));" is still
there, still all 144 IRQs are registered. So now the driver is under
drivers/dma, also fixed all docbook comments.
Changes since version 3: fixed idmac_issue_pending() to not reset the
current buffer, fixed return value from idmac_tx_submit(), fixed
framebuffer panning.
Changes since version 2: now uses a tasklet to clean up completed
transaction descriptors, as suggested by Dan Williams.
Changes since version 1: rebased on the updated dmaengine framework.
Aimed at 2.6.29.
Based on linux-next as of commit f0e0e8954d03b414927650a6129ace01d554afdc.
Thanks
Guennadi
---
Guennadi Liakhovetski
next reply other threads:[~2008-12-26 17:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-26 17:11 Guennadi Liakhovetski [this message]
2008-12-26 17:11 ` [PATCH 1/4 v6] dmaengine: add async_tx_clear_ack() macro Guennadi Liakhovetski
2008-12-26 17:11 ` [PATCH 2/4 v6] i.MX31: Image Processing Unit DMA and IRQ drivers Guennadi Liakhovetski
2008-12-26 17:11 ` [PATCH 3/4 v6] i.MX31: framebuffer driver Guennadi Liakhovetski
2008-12-26 17:11 ` [PATCH 4/4 v6] i.MX31: platform bindings and initialisation for IPU and framebuffer drivers Guennadi Liakhovetski
2009-01-05 19:43 ` [PATCH 0/4 v6] i.MX31: dmaengine " Dan Williams
2009-01-05 21:02 ` Guennadi Liakhovetski
2009-01-05 21:35 ` Dan Williams
2009-01-16 10:09 ` Guennadi Liakhovetski
2009-01-16 17:39 ` Dan Williams
2009-01-06 9:04 ` Sascha Hauer
2009-01-06 9:51 ` Guennadi Liakhovetski
2009-01-06 10:19 ` Sascha Hauer
2009-01-06 13:20 ` Hans J. Koch
2009-01-08 11:15 ` [PATCH 2/4 v7] i.MX31: Image Processing Unit DMA and IRQ drivers Guennadi Liakhovetski
2009-01-08 10:50 ` [PATCH 0/4 v6] i.MX31: dmaengine and framebuffer drivers 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=Pine.LNX.4.64.0812261714290.4895@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=adaplas@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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