From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: linux-media@vger.kernel.org, sakari.ailus@iki.fi
Subject: Re: [PATCH] v4l: omap3isp: Enable driver compilation with COMPILE_TEST
Date: Sat, 22 Aug 2015 01:32:10 +0300 [thread overview]
Message-ID: <14726163.UmoqPsfLVT@avalon> (raw)
In-Reply-To: <20150821174515.360b87e9@recife.lan>
Hi Mauro,
On Friday 21 August 2015 17:45:15 Mauro Carvalho Chehab wrote:
> Em Fri, 21 Aug 2015 21:09:17 +0300 Laurent Pinchart escreveu:
> > The omap3isp driver can't be compiled on non-ARM platforms but has no
> > compile-time dependency on OMAP. Drop the OMAP dependency when
> > COMPILE_TEST is set.
> >
> > Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > ---
> >
> > drivers/media/platform/Kconfig | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/media/platform/Kconfig
> > b/drivers/media/platform/Kconfig index 484038185ae3..95f0f6e6bbc8 100644
> > --- a/drivers/media/platform/Kconfig
> > +++ b/drivers/media/platform/Kconfig
> > @@ -85,7 +85,9 @@ config VIDEO_M32R_AR_M64278
> >
> > config VIDEO_OMAP3
> > tristate "OMAP 3 Camera support"
> > - depends on VIDEO_V4L2 && I2C && VIDEO_V4L2_SUBDEV_API && ARCH_OMAP3
> > + depends on VIDEO_V4L2 && I2C && VIDEO_V4L2_SUBDEV_API
> > + depends on ARCH_OMAP3 || COMPILE_TEST
> > + depends on ARM
> > depends on HAS_DMA && OF
> > depends on OMAP_IOMMU
> > select ARM_DMA_USE_IOMMU
>
> Sorry, but this doesn't make sense.
>
> We can only add COMPILE_TEST after getting rid of those
> depends on OMAP_IOMMU
> select ARM_DMA_USE_IOMMU
>
> The COMPILE_TEST flag was added to support building drivers with
> allyesconfig/allmodconfig for all archs. Selecting a sub-arch
> specific configuration doesn't help at all (or make any difference,
> as if such subarch is already selected, a make allmodconfig/allyesconfig
> will build the driver anyway).
As explained in the commit message, the driver currently explicitly depends on
the OMAP IOMMU API (as well as the ARM DMA mapping API). That's something that
will be removed at some point in the future (it "only" requires finding time
to clean the code). COMPILE_TEST will then be useful and will need to be
enabled by a patch similar to this one. I thus don't see a big reason not to
enable COMPILE_TEST support now.
> One of the main reasons why this is interesting is to support the
> Coverity Scan community license, used by the Kernel janitors. This
> tool runs only on x86.
Not all drivers can be compiled on x86, some dependencies on ARM APIs can be
valid. COMPILE_TEST with a dependency on ARM is already useful as it gives a
much wider compile coverage than depending on a particular ARM platform. I
would even not be surprised if the Linux kernel was compiled for ARM more
often that x86 nowadays.
As for coverity, how does running on x86 doesn't preclude analyzing source
code written for ARM platforms ?
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2015-08-21 22:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 18:09 [PATCH] v4l: omap3isp: Enable driver compilation with COMPILE_TEST Laurent Pinchart
2015-08-21 20:45 ` Mauro Carvalho Chehab
2015-08-21 22:32 ` Laurent Pinchart [this message]
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=14726163.UmoqPsfLVT@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=sakari.ailus@iki.fi \
/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