From: Changhuang Liang <changhuang.liang@starfivetech.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Ming Qian <ming.qian@nxp.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Benjamin Gaignard <benjamin.gaignard@collabora.com>,
Tomi Valkeinen <tomi.valkeinen+renesas@ideasonboard.com>,
Mingjia Zhang <mingjia.zhang@mediatek.com>,
Marvin Lin <milkfafa@gmail.com>
Cc: Jack Zhu <jack.zhu@starfivetech.com>,
Changhuang Liang <changhuang.liang@starfivetech.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: [PATCH v4 10/13] staging: media: starfive: Add V4L2_CAP_IO_MC capability
Date: Tue, 2 Apr 2024 03:00:08 -0700 [thread overview]
Message-ID: <20240402100011.13480-11-changhuang.liang@starfivetech.com> (raw)
In-Reply-To: <20240402100011.13480-1-changhuang.liang@starfivetech.com>
Add V4L2_CAP_IO_MC capabality for video device. User space can enumerate
formats by mbus code.
Signed-off-by: Changhuang Liang <changhuang.liang@starfivetech.com>
---
drivers/staging/media/starfive/camss/stf-video.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/media/starfive/camss/stf-video.c b/drivers/staging/media/starfive/camss/stf-video.c
index d9e51d4e2004..4ca889a7b757 100644
--- a/drivers/staging/media/starfive/camss/stf-video.c
+++ b/drivers/staging/media/starfive/camss/stf-video.c
@@ -665,7 +665,7 @@ int stf_video_register(struct stfcamss_video *video,
}
vdev->fops = &stf_vid_fops;
- vdev->device_caps |= V4L2_CAP_STREAMING;
+ vdev->device_caps |= V4L2_CAP_STREAMING | V4L2_CAP_IO_MC;
vdev->entity.ops = &stf_media_ops;
vdev->vfl_dir = VFL_DIR_RX;
vdev->release = stf_video_release;
--
2.25.1
next prev parent reply other threads:[~2024-04-02 10:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 9:59 [PATCH v4 00/13] Add ISP 3A for StarFive Changhuang Liang
2024-04-02 9:59 ` [PATCH v4 01/13] media: starfive: Add JH7110 ISP module definitions Changhuang Liang
2024-04-02 10:00 ` [PATCH v4 02/13] media: Documentation: Add description for StarFive ISP metadata formats Changhuang Liang
2024-04-02 10:00 ` [PATCH v4 03/13] media: videodev2.h, v4l2-ioctl: Add StarFive ISP meta buffer format Changhuang Liang
2024-04-02 10:00 ` [PATCH v4 04/13] staging: media: starfive: Add a params sink pad and a scd source pad for ISP Changhuang Liang
2024-04-02 10:00 ` [PATCH v4 05/13] staging: media: starfive: Separate buffer from ISP hardware operation Changhuang Liang
2024-04-02 10:00 ` [PATCH v4 06/13] staging: media: starfive: Separate buffer be a common file Changhuang Liang
2024-04-02 10:00 ` [PATCH v4 07/13] staging: media: starfive: Separate ISP hardware from capture device Changhuang Liang
2024-04-02 10:00 ` [PATCH v4 08/13] staging: media: starfive: Add for StarFive ISP 3A SC Changhuang Liang
2024-04-02 10:00 ` [PATCH v4 09/13] staging: media: starfive: Update ISP initialise config for 3A Changhuang Liang
2024-04-02 10:00 ` Changhuang Liang [this message]
2024-04-02 10:00 ` [PATCH v4 11/13] staging: media: starfive: Add ISP params video device Changhuang Liang
2024-04-02 10:00 ` [PATCH v4 12/13] staging: media: starfive: Add ISP parameters hardware configure Changhuang Liang
2024-04-02 10:00 ` [PATCH v4 13/13] admin-guide: media: Update documents for StarFive Camera Subsystem Changhuang Liang
2024-05-16 3:22 ` 回复: [PATCH v4 00/13] Add ISP 3A for StarFive Changhuang Liang
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=20240402100011.13480-11-changhuang.liang@starfivetech.com \
--to=changhuang.liang@starfivetech.com \
--cc=benjamin.gaignard@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jack.zhu@starfivetech.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=milkfafa@gmail.com \
--cc=ming.qian@nxp.com \
--cc=mingjia.zhang@mediatek.com \
--cc=nicolas.dufresne@collabora.com \
--cc=tomi.valkeinen+renesas@ideasonboard.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 read-only IMAP folder(s) and NNTP newsgroup(s).