All of lore.kernel.org
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
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:28:08 +0200	[thread overview]
Message-ID: <20100630072808.GD11746@pengutronix.de> (raw)
In-Reply-To: <Pine.LNX.4.64.1006300918190.17489@axis700.grange>

Hi Guennadi,

On Wed, Jun 30, 2010 at 09:20:36AM +0200, Guennadi Liakhovetski wrote:
> > > --- 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,
Using a common scheme for names on all platforms is fine, but if the
existing names are bad better establish a nicer scheme.

>                                                secondly not to have to use 
> (CONFIG_VIDEO_MX2 || CONFIG_VIDEO_MX2_MODULE),
ah, didn't notice that MX?_VIDEO is bool while VIDEO_MX? is tristate.
That's fine.  Still I would prefer a better naming that doesn't force
having to look up which variable is for the driver and which is for the
arch stuff.

>                                                also note, that 
> CONFIG_MX1_VIDEO is also used for linking of the FIQ handler for the camera.
This is just a matter of fixing the corresponding Makefile.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

WARNING: multiple messages have this Message-ID (diff)
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Baruch Siach <baruch@tkos.co.il>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Sascha Hauer <kernel@pengutronix.de>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv4 1/3] mx2_camera: Add soc_camera support for i.MX25/i.MX27
Date: Wed, 30 Jun 2010 09:28:08 +0200	[thread overview]
Message-ID: <20100630072808.GD11746@pengutronix.de> (raw)
In-Reply-To: <Pine.LNX.4.64.1006300918190.17489@axis700.grange>

Hi Guennadi,

On Wed, Jun 30, 2010 at 09:20:36AM +0200, Guennadi Liakhovetski wrote:
> > > --- 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,
Using a common scheme for names on all platforms is fine, but if the
existing names are bad better establish a nicer scheme.

>                                                secondly not to have to use 
> (CONFIG_VIDEO_MX2 || CONFIG_VIDEO_MX2_MODULE),
ah, didn't notice that MX?_VIDEO is bool while VIDEO_MX? is tristate.
That's fine.  Still I would prefer a better naming that doesn't force
having to look up which variable is for the driver and which is for the
arch stuff.

>                                                also note, that 
> CONFIG_MX1_VIDEO is also used for linking of the FIQ handler for the camera.
This is just a matter of fixing the corresponding Makefile.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2010-06-30  7:28 UTC|newest]

Thread overview: 28+ 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 ` 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-21  5:15   ` Baruch Siach
2010-06-29 19:47   ` Guennadi Liakhovetski
2010-06-29 19:47     ` Guennadi Liakhovetski
2010-06-30  3:03     ` Baruch Siach
2010-06-30  3:03       ` Baruch Siach
2010-06-30  6:24       ` Uwe Kleine-König
2010-06-30  6:24         ` Uwe Kleine-König
2010-06-30  7:07   ` Uwe Kleine-König
2010-06-30  7:07     ` Uwe Kleine-König
2010-06-30  7:20     ` Guennadi Liakhovetski
2010-06-30  7:20       ` Guennadi Liakhovetski
2010-06-30  7:28       ` Uwe Kleine-König [this message]
2010-06-30  7:28         ` Uwe Kleine-König
2010-06-30  9:08         ` Guennadi Liakhovetski
2010-06-30  9:08           ` Guennadi Liakhovetski
2010-06-30  9:38           ` Uwe Kleine-König
2010-06-30  9:38             ` Uwe Kleine-König
2010-07-01  5:00           ` Baruch Siach
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:15   ` Baruch Siach
2010-06-21  5:16 ` [PATCHv4 3/3] mx25: " Baruch Siach
2010-06-21  5:16   ` Baruch Siach
2010-06-21  7:19 ` [PATCHv4 0/3] Driver for the i.MX2x CMOS Sensor Interface Sascha Hauer
2010-06-21  7:19   ` 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=20100630072808.GD11746@pengutronix.de \
    --to=u.kleine-koenig@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 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.