From: Dmitry Krivoschekov <dmitry.krivoschekov@gmail.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-kernel@vger.kernel.org,
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>
Subject: Re: [PATCH 2/4 v2] i.MX31: Image Processing Unit DMA and IRQ drivers
Date: Wed, 10 Dec 2008 16:26:33 +0300 [thread overview]
Message-ID: <493FC389.1010406@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0812101130400.4578@axis700.grange>
Hi,
Guennadi Liakhovetski wrote:
> From: Guennadi Liakhovetski <lg@denx.de>
>
> i.MX3x SoCs contain an Image Processing Unit, consisting of a Control
> Module (CM), Display Interface (DI), Synchronous Display Controller (SDC),
> Asynchronous Display Controller (ADC), Image Converter (IC), Post-Filter
> (PF), Camera Sensor Interface (CSI), and an Image DMA Controller (IDMAC).
> CM contains, among other blocks, an Interrupt Generator (IG) and a Clock
> and Reset Control Unit (CRCU). This driver serves IDMAC and IG. They are
> supported over dmaengine and irq-chip APIs respectively.
>
> IDMAC is a specialised DMA controller, its DMA channels cannot be used for
> general-purpose operations, even though it might be possible to configure
> a memory-to-memory channel for memcpy operation. This driver will not work
> with generic dmaengine clients, clients, wishing to use it must use
> respective wrapper structures, they also must specify which channels they
> require, as channels are hard-wired to specific IPU functions.
>
> Signed-off-by: Guennadi Liakhovetski <lg@denx.de>
> ---
> arch/arm/plat-mxc/include/mach/ipu.h | 180 ++++
> arch/arm/plat-mxc/include/mach/mx31.h | 139 +++-
> drivers/mfd/Kconfig | 16 +
> drivers/mfd/Makefile | 4 +-
> drivers/mfd/ipu/Makefile | 5 +
> drivers/mfd/ipu/ipu_idmac.c | 1617 +++++++++++++++++++++++++++++++++
> drivers/mfd/ipu/ipu_intern.h | 172 ++++
> drivers/mfd/ipu/ipu_irq.c | 277 ++++++
why do you think drivers/mfd is an appropriate location for this driver?
IPU is on-chip device, but it is not a separate multifunction device so
it should not be placed in drivers/mfd.
arch/arm/plat-mxc/ or drivers/video/ipu seem better places for this driver.
Dmitry
> 8 files changed, 2408 insertions(+), 2 deletions(-)
> create mode 100644 arch/arm/plat-mxc/include/mach/ipu.h
> create mode 100644 drivers/mfd/ipu/Makefile
> create mode 100644 drivers/mfd/ipu/ipu_idmac.c
> create mode 100644 drivers/mfd/ipu/ipu_intern.h
> create mode 100644 drivers/mfd/ipu/ipu_irq.c
next prev parent reply other threads:[~2008-12-10 13:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 10:35 [PATCH 0/4 v2] i.MX31: dmaengine and framebuffer drivers Guennadi Liakhovetski
2008-12-10 10:36 ` [PATCH 1/4 v2] dmaengine: add a tx_free method to struct dma_async_tx_descriptor Guennadi Liakhovetski
2008-12-10 19:58 ` Dan Williams
2008-12-11 0:30 ` Guennadi Liakhovetski
2008-12-11 2:01 ` Dan Williams
2008-12-11 15:55 ` Guennadi Liakhovetski
2008-12-11 16:43 ` Dan Williams
2008-12-11 16:56 ` Guennadi Liakhovetski
2008-12-10 10:36 ` [PATCH 2/4 v2] i.MX31: Image Processing Unit DMA and IRQ drivers Guennadi Liakhovetski
2008-12-10 13:26 ` Dmitry Krivoschekov [this message]
2008-12-10 13:49 ` Guennadi Liakhovetski
2008-12-10 10:36 ` [PATCH 3/4 v2] i.MX31: framebuffer driver Guennadi Liakhovetski
2008-12-10 16:23 ` Herring Robert
2008-12-10 16:23 ` Herring Robert
2008-12-10 16:47 ` Guennadi Liakhovetski
2008-12-10 16:47 ` Guennadi Liakhovetski
2008-12-11 1:32 ` Herring Robert
2008-12-11 1:32 ` Herring Robert
2008-12-10 10:36 ` [PATCH 4/4 v2] i.MX31: platform bindings and initialisation for IPU and framebuffer drivers Guennadi Liakhovetski
2008-12-10 10:36 ` Guennadi Liakhovetski
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=493FC389.1010406@gmail.com \
--to=dmitry.krivoschekov@gmail.com \
--cc=adaplas@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=g.liakhovetski@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.