From: Philippe De Muyter <phdm@macq.eu>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Steve Longerbeam <steve_longerbeam@mentor.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org,
Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: i.mx6 camera interface (CSI) and mainline kernel
Date: Thu, 3 Mar 2016 09:36:43 +0100 [thread overview]
Message-ID: <20160303083643.GA4303@frolo.macqel> (raw)
In-Reply-To: <56D7E59B.6050605@xs4all.nl>
Hi Steve,
On Thu, Mar 03, 2016 at 08:19:55AM +0100, Hans Verkuil wrote:
> On 03/03/2016 03:02 AM, Steve Longerbeam wrote:
> > On 02/25/2016 02:05 PM, Laurent Pinchart wrote:
> >> Hello Philippe,
> >>
> >> CC'ing Philipp and Steve.
> >>
> >> Philipp, Steve, are you still interested in getting a driver for the i.MX6
> >> camera interface upstreamed ?
> >
> > Hi Laurent, Philippe(s),
> >
> > I spent a few days updating my mx6-media-staging branch at
First of all, thank you very much, Steve.
> > git@github.com:slongerbeam/linux-meibp-314.git, moved forward
> > to latest master at 4.5-rc3.
Just to be sure : do you mean https://github.com/slongerbeam/mediatree.git
or something else ?
> >
> > So far I have retested video capture with the SabreAuto/ADV7180 and
> > the SabreSD/OV5640-mipi-csi2, and video capture is working fine on
> > those platforms.
> >
> > There is also a mem2mem that should work fine, but haven't tested yet.
> >
> > I removed camera preview support. At Mentor Graphics we have made
> > quite a few changes to ipu-v3 driver to allow camera preview to initialize
> > and control an overlay display plane independently of imx-drm, by adding
> > a subsystem independent ipu-plane sub-unit. Note we also have a video
> > output overlay driver that also makes use of ipu-plane. But those changes are
> > extensive and touch imx-drm as well as ipu-v3, so I am leaving camera preview
> > and the output overlay driver out (in fact, camera preview is not of much
> > utility so I probably won't bring it back in upstream version).
> >
> > The video capture driver is not quite ready for upstream review yet. It still:
> >
> > - uses the old cropping APIs but should move forward to selection APIs.
> >
> > - uses custom sensor subdev drivers for ADV7180 and OV564x. Still
> > need to switch to upstream subdevs.
Is it only a problem of those sensor drivers (which exact files ?) or
is it a problem of the capture driver itself ?
I must update a sensor driver I wrote for the intdev interface found
in the freescale kernel, and I'd like to start from a working subdev
example. Which driver should I choose as an example ?
> >
> > - still does not implement the media device framework.
>
> After fixing the first two items on that list, would that be a good time to
> add this driver to staging?
>
> i.MX6 is quite popular, so having support for this device upstream would be
> very nice indeed.
>
> I'd really like to see some upstream support for this SoC soon.
There are a bunch of people expecting that (and trying to help) :)
Best regards
Philippe
>
> Regards,
>
> Hans
>
> >
> >
> > Steve
> >
> >>
> >> On Tuesday 23 February 2016 15:12:58 Philippe De Muyter wrote:
> >>> Update.
> >>>
> >>> On Tue, Feb 23, 2016 at 12:49:43PM +0100, Philippe De Muyter wrote:
> >>>> Hello,
> >>>>
> >>>> We use a custom imx6 based board with a canera sensor on it.
> >>>> I have written the driver for the camera sensor, based on
> >>>> the freescale so-called "3.10" and even "3.14" linux versions.
> >>>>
> >>>> The camera works perfectly, but we would like to switch to
> >>>> a mainline kernel for all the usual reasons (including being
> >>>> able to contribute our fixes).
> >>>>
> >>>> >From an old mail thread (*), I have found two git repositories
> >>>>
> >>>> that used to contain not-yet-approved versions of mainline
> >>>> imx6 ipu-v3 drivers :
> >>>>
> >>>> git://git.pengutronix.de/git/pza/linux.git test/nitrogen6x-ipu-media
> >>>> https://github.com:slongerbeam/mediatree.git, mx6-camera-staging
> >>>>
> >>>> I have tried to compile them with the imx_v6_v7_defconfig, but both
> >>>> fail directly at compile time. because of later changes in the
> >>>> v4l2_subdev infrastructure, not ported to the those branches.
> >>> What I wrote is true for Steve Longerbeam's branch, but for Philipp Zabel's
> >>> branch the problem (so far) was only that CONFIG_MEDIA_CONTROLLER
> >>> is not defined in imx_v6_v7_defconfig, but is required for a succesfull
> >>> compilation of Philipp's tree.
> >>>
> >>>> Can someone point me to compilable versions (either not rebased
> >>>> versions of those branches, or updated versions of those branches,
> >>>> or yet another place to look at). ?
> >>>>
> >>>> Thanks in advance
> >>>>
> >>>> Philippe
> >>>>
> >>>> (*)
> >>>> http://linux-media.vger.kernel.narkive.com/cZQ8NrZ2/i-mx6-status-for-ipu-> > vpu-gpu
> >
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-media" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
--
Philippe De Muyter +32 2 6101532 Macq SA rue de l'Aeronef 2 B-1140 Bruxelles
next prev parent reply other threads:[~2016-03-03 8:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 11:49 i.mx6 camera interface (CSI) and mainline kernel Philippe De Muyter
2016-02-23 14:12 ` Philippe De Muyter
2016-02-25 22:05 ` Laurent Pinchart
2016-03-03 2:02 ` Steve Longerbeam
2016-03-03 7:19 ` Hans Verkuil
2016-03-03 8:36 ` Philippe De Muyter [this message]
2016-03-03 17:45 ` Steve Longerbeam
2016-03-03 17:52 ` Philippe De Muyter
2016-03-07 16:19 ` Tim Harvey
2016-03-09 2:06 ` Steve Longerbeam
2016-03-09 22:44 ` Tim Harvey
2016-03-10 0:12 ` Steve Longerbeam
2016-03-10 7:30 ` Hans Verkuil
2016-03-14 14:55 ` Philippe De Muyter
2016-03-15 20:54 ` Tim Harvey
2016-06-02 13:29 ` Tim Harvey
2016-06-02 13:55 ` Hans Verkuil
2016-06-02 16:50 ` Steve Longerbeam
2016-06-06 16:48 ` Steve Longerbeam
2016-06-10 15:58 ` Jack Mitchell
2016-06-10 16:34 ` Steve Longerbeam
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=20160303083643.GA4303@frolo.macqel \
--to=phdm@macq.eu \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=steve_longerbeam@mentor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox