From: g.liakhovetski@gmx.de (Guennadi Liakhovetski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv4 1/3] mx2_camera: Add soc_camera support for i.MX25/i.MX27
Date: Wed, 30 Jun 2010 09:20:36 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.1006300918190.17489@axis700.grange> (raw)
In-Reply-To: <20100630070717.GA11746@pengutronix.de>
On Wed, 30 Jun 2010, Uwe Kleine-K?nig wrote:
> On Mon, Jun 21, 2010 at 08:15:58AM +0300, Baruch Siach wrote:
> > This is the soc_camera support developed by Sascha Hauer for the i.MX27. Alan
> > Carvalho de Assis modified the original driver to get it working on more recent
> > kernels. I modified it further to add support for i.MX25. This driver has been
> > tested on i.MX25 and i.MX27 based platforms.
> >
> > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> > ---
> > arch/arm/plat-mxc/include/mach/memory.h | 4 +-
> > arch/arm/plat-mxc/include/mach/mx2_cam.h | 46 +
> > drivers/media/video/Kconfig | 13 +
> > drivers/media/video/Makefile | 1 +
> > drivers/media/video/mx2_camera.c | 1493 ++++++++++++++++++++++++++++++
> > 5 files changed, 1555 insertions(+), 2 deletions(-)
> > create mode 100644 arch/arm/plat-mxc/include/mach/mx2_cam.h
> > create mode 100644 drivers/media/video/mx2_camera.c
> >
> > diff --git a/arch/arm/plat-mxc/include/mach/memory.h b/arch/arm/plat-mxc/include/mach/memory.h
> > index c4b40c3..5803836 100644
> > --- a/arch/arm/plat-mxc/include/mach/memory.h
> > +++ b/arch/arm/plat-mxc/include/mach/memory.h
> > @@ -44,12 +44,12 @@
> > */
> > #define CONSISTENT_DMA_SIZE SZ_8M
> >
> > -#elif defined(CONFIG_MX1_VIDEO)
> > +#elif defined(CONFIG_MX1_VIDEO) || defined(CONFIG_MX2_VIDEO)
> > /*
> > * Increase size of DMA-consistent memory region.
> > * This is required for i.MX camera driver to capture at least four VGA frames.
> > */
> > #define CONSISTENT_DMA_SIZE SZ_4M
> > -#endif /* CONFIG_MX1_VIDEO */
> > +#endif /* CONFIG_MX1_VIDEO || CONFIG_MX2_VIDEO */
> Why not use CONFIG_VIDEO_MX2 here and get rid of CONFIG_MX2_VIDEO?
Well, firstly for uniformity with MX1 and MX3, secondly not to have to use
(CONFIG_VIDEO_MX2 || CONFIG_VIDEO_MX2_MODULE), also note, that
CONFIG_MX1_VIDEO is also used for linking of the FIQ handler for the camera.
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
next prev parent reply other threads:[~2010-06-30 7:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 5:15 [PATCHv4 0/3] Driver for the i.MX2x CMOS Sensor Interface Baruch Siach
2010-06-21 5:15 ` [PATCHv4 1/3] mx2_camera: Add soc_camera support for i.MX25/i.MX27 Baruch Siach
2010-06-29 19:47 ` Guennadi Liakhovetski
2010-06-30 3:03 ` Baruch Siach
2010-06-30 6:24 ` Uwe Kleine-König
2010-06-30 7:07 ` Uwe Kleine-König
2010-06-30 7:20 ` Guennadi Liakhovetski [this message]
2010-06-30 7:28 ` Uwe Kleine-König
2010-06-30 9:08 ` Guennadi Liakhovetski
2010-06-30 9:38 ` Uwe Kleine-König
2010-07-01 5:00 ` Baruch Siach
2010-06-21 5:15 ` [PATCHv4 2/3] mx27: add support for the CSI device Baruch Siach
2010-06-21 5:16 ` [PATCHv4 3/3] mx25: " Baruch Siach
2010-06-21 7:19 ` [PATCHv4 0/3] Driver for the i.MX2x CMOS Sensor Interface 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.1006300918190.17489@axis700.grange \
--to=g.liakhovetski@gmx.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