From: Janusz Krzysztofik <jmkrzyszt@gmail.com>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Hans Verkuil <hverkuil@xs4all.nl>,
Amitoj Kaur Chawla <amitoj1606@gmail.com>,
Arnd Bergmann <arnd@arndb.de>, Tony Lindgren <tony@atomide.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
devel@driverdev.osuosl.org, linux-omap@vger.kernel.org,
Janusz Krzysztofik <jmkrzyszt@gmail.com>
Subject: [RFC] [PATCH 0/3] media: an attempt to refresh omap1_camera driver
Date: Thu, 16 Jun 2016 19:21:31 +0200 [thread overview]
Message-ID: <1466097694-8660-1-git-send-email-jmkrzyszt@gmail.com> (raw)
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.
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.
Thanks,
Janusz
Janusz Krzysztofik (3):
staging: media: omap1: drop videobuf-dma-sg mode
staging: media: omap1: convert to videobuf2
staging: media: omap1: use dmaengine
drivers/staging/media/omap1/Kconfig | 5 +-
drivers/staging/media/omap1/omap1_camera.c | 948 +++++------------------
include/linux/platform_data/media/omap1_camera.h | 9 -
3 files changed, 217 insertions(+), 745 deletions(-)
--
2.7.3
next reply other threads:[~2016-06-16 17:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 17:21 Janusz Krzysztofik [this message]
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
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=1466097694-8660-1-git-send-email-jmkrzyszt@gmail.com \
--to=jmkrzyszt@gmail.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=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®