From: zhenwei pi <pizhenwei@bytedance.com>
To: peter.maydell@linaro.org, richard.henderson@linaro.org,
eblake@redhat.com, pbonzini@redhat.com, berrange@redhat.com,
kraxel@redhat.com
Cc: qemu-devel@nongnu.org, zhenwei pi <pizhenwei@bytedance.com>
Subject: [PATCH v2 0/2] Introduce camera subsystem
Date: Thu, 6 Jan 2022 16:53:02 +0800 [thread overview]
Message-ID: <20220106085304.795010-1-pizhenwei@bytedance.com> (raw)
v1 -> v2:
[missing CC qemu-devel@nongnu.org, resend]
Separate v1 patch set into 2 parts:
Introduce camera subsystem (this one).
USB desc fix and UVC.
Add maintainer infomation.
v1:
1, The full picture of this patch set:
+---------+ +------------+ +---------------+
|UVC(done)| |virtio(TODO)| |other HW device|
+---------+ +------------+ +---------------+
| | |
| +------------+ |
+------------+camera(done)+-------------+
+----+-------+
|
+-----------------+---------------------+
| | |
+------+------+ +----+-----+ +------+------+
|builtin(done)| |v4l2(done)| |other drivers|
+-------------+ +----------+ +-------------+
With this patch set, We can run a desktop VM (Ex Ubuntu-2004), several camera
APPs(cheese, kamoso, guvcview and qcam) work fine.
Some works still in working:
1, hot-plug
2, compat with live migration
3, several actions defined in UVC SPEC
Zhenwei Pi (2):
camera: Introduce camera subsystem and builtin driver
camera: v4l2: Introduce v4l2 camera driver
MAINTAINERS | 7 +
camera/builtin.c | 717 ++++++++++++++++++++++++++++++++++++++++
camera/camera-int.h | 19 ++
camera/camera.c | 522 +++++++++++++++++++++++++++++
camera/meson.build | 20 ++
camera/trace-events | 28 ++
camera/trace.h | 1 +
camera/v4l2.c | 637 +++++++++++++++++++++++++++++++++++
include/camera/camera.h | 238 +++++++++++++
meson.build | 20 +-
meson_options.txt | 3 +
qapi/camera.json | 101 ++++++
qapi/meson.build | 1 +
qapi/qapi-schema.json | 1 +
qemu-options.hx | 13 +
softmmu/vl.c | 4 +
16 files changed, 2331 insertions(+), 1 deletion(-)
create mode 100644 camera/builtin.c
create mode 100644 camera/camera-int.h
create mode 100644 camera/camera.c
create mode 100644 camera/meson.build
create mode 100644 camera/trace-events
create mode 100644 camera/trace.h
create mode 100644 camera/v4l2.c
create mode 100644 include/camera/camera.h
create mode 100644 qapi/camera.json
--
2.25.1
next reply other threads:[~2022-01-06 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 8:53 zhenwei pi [this message]
2022-01-06 8:53 ` [PATCH v2 1/2] camera: Introduce camera subsystem and builtin driver zhenwei pi
2022-01-06 8:53 ` [PATCH v2 2/2] camera: v4l2: Introduce v4l2 camera driver zhenwei pi
2022-01-10 6:11 ` [PATCH v2 0/2] Introduce camera subsystem zhenwei pi
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=20220106085304.795010-1-pizhenwei@bytedance.com \
--to=pizhenwei@bytedance.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).