From: Tony Lindgren <tony@atomide.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Janusz Krzysztofik <jmkrzyszt@gmail.com>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Amitoj Kaur Chawla <amitoj1606@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
devel@driverdev.osuosl.org, linux-omap@vger.kernel.org
Subject: Re: [RFC] [PATCH 0/3] media: an attempt to refresh omap1_camera driver
Date: Fri, 17 Jun 2016 03:03:07 -0700 [thread overview]
Message-ID: <20160617100307.GE22406@atomide.com> (raw)
In-Reply-To: <5763A114.2080309@xs4all.nl>
* Hans Verkuil <hverkuil@xs4all.nl> [160617 00:07]:
> Hi Janusz,
>
> On 06/16/2016 07:21 PM, Janusz Krzysztofik wrote:
> > As requested by media subsystem maintainers, here is an attempt to
> > convert the omap1_camera driver to the vb2 framework. Also, conversion
> > to the dmaengine framework, long awaited by ARM/OMAP maintainers, is
> > done.
Janusz, thanks for updating to the dmaengine :)
> > Next, I'm going to approach removal of soc-camera dependency. Please
> > let me know how much time I have for that, i.e., when the soc-camera
> > framework is going to be depreciated.
>
> Well, it is already deprecated (i.e. new drivers cannot use it), but it won't
> be removed any time soon. There are still drivers depending on it, and some
> aren't easy to rewrite.
>
> I have to say that it is totally unexpected to see that this omap1 driver is still
> used. In fact, we've already merged a patch that removed it for the upcoming
> 4.8 kernel. Based on this new development I'll revert that for the omap1
> driver.
>
> Out of curiosity: is supporting the Amstrad Delta something you do as a hobby
> or are there other reasons?
Hmm if that IP old phone works fine with mainline kernel, why not keep
using it? :)
> A final note: once you've managed to drop the soc-camera dependency you should
> run the v4l2-compliance test over the video node (https://git.linuxtv.org/v4l-utils.git/).
>
> If that passes without failures, then this driver is in good shape and can be
> moved out of staging again.
Sounds good to me also, thanks guys.
Tony
next prev parent reply other threads:[~2016-06-17 10:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 17:21 [RFC] [PATCH 0/3] media: an attempt to refresh omap1_camera driver Janusz Krzysztofik
2016-06-16 17:21 ` [RFC] [PATCH 1/3] staging: media: omap1: drop videobuf-dma-sg mode Janusz Krzysztofik
2016-06-16 17:21 ` [RFC] [PATCH 2/3] staging: media: omap1: convert to videobuf2 Janusz Krzysztofik
2016-06-16 17:21 ` [RFC] [PATCH 3/3] staging: media: omap1: use dmaengine Janusz Krzysztofik
2016-06-17 7:04 ` [RFC] [PATCH 0/3] media: an attempt to refresh omap1_camera driver Hans Verkuil
2016-06-17 10:03 ` Tony Lindgren [this message]
2016-07-01 7:37 ` Hans Verkuil
2016-07-03 23:32 ` Aaro Koskinen
2016-07-04 6:50 ` Hans Verkuil
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=20160617100307.GE22406@atomide.com \
--to=tony@atomide.com \
--cc=amitoj1606@gmail.com \
--cc=arnd@arndb.de \
--cc=devel@driverdev.osuosl.org \
--cc=g.liakhovetski@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil@xs4all.nl \
--cc=jmkrzyszt@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mchehab@osg.samsung.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;
as well as URLs for NNTP newsgroup(s).