From: martin@neutronstar.dyndns.org
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Igor Grinberg <grinberg@compulab.co.il>,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, Hiremath Vaibhav <hvaibhav@ti.com>,
linux-media@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] arm: omap3evm: Add support for an MT9M032 based camera board.
Date: Wed, 14 Dec 2011 19:22:29 +0100 [thread overview]
Message-ID: <1323886950.295978.31313@localhost> (raw)
In-Reply-To: <201112141415.23885.laurent.pinchart@ideasonboard.com>
On Wed, Dec 14, 2011 at 02:15:22PM +0100, Laurent Pinchart wrote:
> Hi Igor,
>
> On Wednesday 14 December 2011 10:31:35 Igor Grinberg wrote:
> > On 12/14/11 03:25, Martin Hostettler wrote:
> > > Adds board support for an MT9M032 based camera to omap3evm.
> > >
> > > Signed-off-by: Martin Hostettler <martin@neutronstar.dyndns.org>
>
> [snip]
>
> > > diff --git a/arch/arm/mach-omap2/board-omap3evm-camera.c
> > > b/arch/arm/mach-omap2/board-omap3evm-camera.c new file mode 100644
> > > index 0000000..bffd5b8
> > > --- /dev/null
> > > +++ b/arch/arm/mach-omap2/board-omap3evm-camera.c
> > > @@ -0,0 +1,155 @@
>
> [snip]
>
> > > +#include <linux/i2c.h>
> > > +#include <linux/init.h>
> > > +#include <linux/platform_device.h>
> > > +
> > > +#include <linux/gpio.h>
> > > +#include <plat/mux.h>
> > > +#include "mux.h"
> > > +
> > > +#include "../../../drivers/media/video/omap3isp/isp.h"
> >
> > Laurent,
> > In one of the previous reviews, you stated:
> > "I'll probably split it and move the part required by board files to
> > include/media/omap3isp.h".
> > Is there any progress on that?
>
> Yes, it has been half-fixed in mainline. Half only because all the structures
> and macros that should be used by board code are now in <media/omap3isp.h>,
> but some boards need to access OMAP3 ISP internals from board code, which
> still requires drivers/media/video/omap3isp/isp.h. This will eventually be
> fixed, when the generic struct clk object will be available.
>
> After a quick look at this patch it seems that <media/omap3isp.h> should be
> enough here.
Almost. The code uses ISPCTRL_PAR_BRIDGE_DISABLE which is only available
from drivers/media/video/omap3isp/ispreg.h.
So i'd say it's better to keep that include than to duplicate this constant
in the code.
What do you think?
By the way, it seems drivers/media/video/omap3isp/ispvideo.c is missing a
#include <linux/module.h> at the moment. I had to patch that line in to get
omap3isp to compile as module.
>
> > > +#include "media/mt9m032.h"
>
> And this should be <media/mt9m032.h>
I'll change this.
Regards,
- Martin Hostettler
>
> > > +#include "devices.h"
>
> --
> Regards,
>
> Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: martin@neutronstar.dyndns.org (martin at neutronstar.dyndns.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] arm: omap3evm: Add support for an MT9M032 based camera board.
Date: Wed, 14 Dec 2011 19:22:29 +0100 [thread overview]
Message-ID: <1323886950.295978.31313@localhost> (raw)
In-Reply-To: <201112141415.23885.laurent.pinchart@ideasonboard.com>
On Wed, Dec 14, 2011 at 02:15:22PM +0100, Laurent Pinchart wrote:
> Hi Igor,
>
> On Wednesday 14 December 2011 10:31:35 Igor Grinberg wrote:
> > On 12/14/11 03:25, Martin Hostettler wrote:
> > > Adds board support for an MT9M032 based camera to omap3evm.
> > >
> > > Signed-off-by: Martin Hostettler <martin@neutronstar.dyndns.org>
>
> [snip]
>
> > > diff --git a/arch/arm/mach-omap2/board-omap3evm-camera.c
> > > b/arch/arm/mach-omap2/board-omap3evm-camera.c new file mode 100644
> > > index 0000000..bffd5b8
> > > --- /dev/null
> > > +++ b/arch/arm/mach-omap2/board-omap3evm-camera.c
> > > @@ -0,0 +1,155 @@
>
> [snip]
>
> > > +#include <linux/i2c.h>
> > > +#include <linux/init.h>
> > > +#include <linux/platform_device.h>
> > > +
> > > +#include <linux/gpio.h>
> > > +#include <plat/mux.h>
> > > +#include "mux.h"
> > > +
> > > +#include "../../../drivers/media/video/omap3isp/isp.h"
> >
> > Laurent,
> > In one of the previous reviews, you stated:
> > "I'll probably split it and move the part required by board files to
> > include/media/omap3isp.h".
> > Is there any progress on that?
>
> Yes, it has been half-fixed in mainline. Half only because all the structures
> and macros that should be used by board code are now in <media/omap3isp.h>,
> but some boards need to access OMAP3 ISP internals from board code, which
> still requires drivers/media/video/omap3isp/isp.h. This will eventually be
> fixed, when the generic struct clk object will be available.
>
> After a quick look at this patch it seems that <media/omap3isp.h> should be
> enough here.
Almost. The code uses ISPCTRL_PAR_BRIDGE_DISABLE which is only available
from drivers/media/video/omap3isp/ispreg.h.
So i'd say it's better to keep that include than to duplicate this constant
in the code.
What do you think?
By the way, it seems drivers/media/video/omap3isp/ispvideo.c is missing a
#include <linux/module.h> at the moment. I had to patch that line in to get
omap3isp to compile as module.
>
> > > +#include "media/mt9m032.h"
>
> And this should be <media/mt9m032.h>
I'll change this.
Regards,
- Martin Hostettler
>
> > > +#include "devices.h"
>
> --
> Regards,
>
> Laurent Pinchart
next prev parent reply other threads:[~2011-12-14 18:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 1:25 [PATCH v3] arm: omap3evm: Add support for an MT9M032 based camera board Martin Hostettler
2011-12-14 1:25 ` Martin Hostettler
2011-12-14 9:31 ` Igor Grinberg
2011-12-14 9:31 ` Igor Grinberg
2011-12-14 13:15 ` Laurent Pinchart
2011-12-14 13:15 ` Laurent Pinchart
2011-12-14 18:22 ` martin [this message]
2011-12-14 18:22 ` martin at neutronstar.dyndns.org
2011-12-15 12:02 ` Laurent Pinchart
2011-12-15 12:02 ` Laurent Pinchart
2011-12-14 18:14 ` martin
2011-12-14 18:14 ` martin at neutronstar.dyndns.org
2011-12-15 10:18 ` Igor Grinberg
2011-12-15 10:18 ` Igor Grinberg
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=1323886950.295978.31313@localhost \
--to=martin@neutronstar.dyndns.org \
--cc=grinberg@compulab.co.il \
--cc=hvaibhav@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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.