From: Steve Longerbeam <slongerbeam@gmail.com>
To: linux-media@vger.kernel.org
Cc: Steve Longerbeam <slongerbeam@gmail.com>
Subject: [PATCH v2 0/8] Switch to sync registration for IPU subdevs
Date: Sun, 28 Apr 2019 12:09:08 -0700 [thread overview]
Message-ID: <20190428190916.26567-1-slongerbeam@gmail.com> (raw)
Switch to sync registration for the IPU internal sub-devices, re-organize
modules, and a few other miscellaneous cleanups.
History:
v2:
- Added a patch that improves the pipeline upstream/downstream search
functions, which no longer require the media device.
- Add a patch to remove getting media device from v4l2_dev driver data.
Steve Longerbeam (8):
media: staging/imx: Switch to sync registration for IPU subdevs
media: staging/imx: Pass device to alloc/free_dma_buf
media: staging/imx: Move add_video_device into capture_device_register
Revert "media: imx: Set capture compose rectangle in
capture_device_set_format"
media: staging/imx: Remove capture_device_set_format
media: staging/imx: Re-organize modules
media: staging/imx: Improve pipeline searching
media: staging/imx: Don't set driver data for v4l2_dev
drivers/staging/media/imx/Makefile | 18 +-
drivers/staging/media/imx/imx-ic-common.c | 68 +--
drivers/staging/media/imx/imx-ic-prp.c | 36 +-
drivers/staging/media/imx/imx-ic-prpencvf.c | 88 ++--
drivers/staging/media/imx/imx-ic.h | 6 +-
drivers/staging/media/imx/imx-media-capture.c | 75 ++-
drivers/staging/media/imx/imx-media-csi.c | 45 +-
.../staging/media/imx/imx-media-dev-common.c | 346 +++++++++++++-
drivers/staging/media/imx/imx-media-dev.c | 449 +-----------------
drivers/staging/media/imx/imx-media-fim.c | 9 -
.../staging/media/imx/imx-media-internal-sd.c | 357 ++++++--------
drivers/staging/media/imx/imx-media-of.c | 41 +-
drivers/staging/media/imx/imx-media-utils.c | 170 +++----
drivers/staging/media/imx/imx-media-vdic.c | 84 +---
drivers/staging/media/imx/imx-media.h | 113 +++--
drivers/staging/media/imx/imx7-media-csi.c | 43 +-
16 files changed, 848 insertions(+), 1100 deletions(-)
--
2.17.1
next reply other threads:[~2019-04-28 19:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 19:09 Steve Longerbeam [this message]
2019-04-28 19:09 ` [PATCH v2 1/8] media: staging/imx: Switch to sync registration for IPU subdevs Steve Longerbeam
2019-04-30 21:56 ` Rui Miguel Silva
2019-04-30 21:59 ` Steve Longerbeam
2019-04-28 19:09 ` [PATCH v2 2/8] media: staging/imx: Pass device to alloc/free_dma_buf Steve Longerbeam
2019-04-28 19:09 ` [PATCH v2 3/8] media: staging/imx: Move add_video_device into capture_device_register Steve Longerbeam
2019-04-28 19:09 ` [PATCH v2 4/8] Revert "media: imx: Set capture compose rectangle in capture_device_set_format" Steve Longerbeam
2019-04-30 22:00 ` Rui Miguel Silva
2019-04-30 22:07 ` Steve Longerbeam
2019-04-28 19:09 ` [PATCH v2 5/8] media: staging/imx: Remove capture_device_set_format Steve Longerbeam
2019-04-28 19:09 ` [PATCH v2 6/8] media: staging/imx: Re-organize modules Steve Longerbeam
2019-04-28 19:09 ` [PATCH v2 7/8] media: staging/imx: Improve pipeline searching Steve Longerbeam
2019-04-28 19:09 ` [PATCH v2 8/8] media: staging/imx: Don't set driver data for v4l2_dev Steve Longerbeam
2019-04-30 9:19 ` [PATCH v2 0/8] Switch to sync registration for IPU subdevs Rui Miguel Silva
2019-04-30 18:38 ` Rui Miguel Silva
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=20190428190916.26567-1-slongerbeam@gmail.com \
--to=slongerbeam@gmail.com \
--cc=linux-media@vger.kernel.org \
/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).