From: Jonas Karlman <jonas@kwiboo.se> To: Lynne <dev@lynne.ee>, FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v2 1/8] avutil/hwcontext: Add hwdevice type for V4L2 Request API Date: Tue, 6 Aug 2024 18:43:06 +0200 Message-ID: <ecfc9c5a-7582-4862-9ffb-a12741d2f0f9@kwiboo.se> (raw) In-Reply-To: <faef98d8-55ab-4a6f-9683-67cdd415f81a@lynne.ee> Hi Lynne, On 2024-08-06 14:46, Lynne via ffmpeg-devel wrote: > On 06/08/2024 11:06, Jonas Karlman wrote: >> Add a hwdevice type for V4L2 Request API with transfer_data_from support >> for AV_PIX_FMT_DRM_PRIME, based on AV_HWDEVICE_TYPE_DRM. >> >> AVV4L2RequestDeviceContext.media_fd can be set by the application or a >> media device path can be supplied when hwdevice is created. When none >> is supplied it default to -1 and hwaccel will auto-detect a media device >> with a capable video device. >> >> Signed-off-by: Jonas Karlman <jonas@kwiboo.se> >> --- >> configure | 7 + >> libavutil/Makefile | 3 + >> libavutil/hwcontext.c | 4 + >> libavutil/hwcontext.h | 1 + >> libavutil/hwcontext_internal.h | 1 + >> libavutil/hwcontext_v4l2request.c | 261 ++++++++++++++++++++++++++++++ >> libavutil/hwcontext_v4l2request.h | 41 +++++ >> 7 files changed, 318 insertions(+) >> create mode 100644 libavutil/hwcontext_v4l2request.c >> create mode 100644 libavutil/hwcontext_v4l2request.h >> [snip] >> diff --git a/libavutil/hwcontext_v4l2request.h b/libavutil/hwcontext_v4l2request.h >> new file mode 100644 >> index 0000000000..0fe42f97b4 >> --- /dev/null >> +++ b/libavutil/hwcontext_v4l2request.h >> @@ -0,0 +1,41 @@ >> +/* >> + * This file is part of FFmpeg. >> + * >> + * FFmpeg is free software; you can redistribute it and/or >> + * modify it under the terms of the GNU Lesser General Public >> + * License as published by the Free Software Foundation; either >> + * version 2.1 of the License, or (at your option) any later version. >> + * >> + * FFmpeg is distributed in the hope that it will be useful, >> + * but WITHOUT ANY WARRANTY; without even the implied warranty of >> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU >> + * Lesser General Public License for more details. >> + * >> + * You should have received a copy of the GNU Lesser General Public >> + * License along with FFmpeg; if not, write to the Free Software >> + * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA >> + */ >> + >> +#ifndef AVUTIL_HWCONTEXT_V4L2REQUEST_H >> +#define AVUTIL_HWCONTEXT_V4L2REQUEST_H >> + >> +/** >> + * @file >> + * An API-specific header for AV_HWDEVICE_TYPE_V4L2REQUEST. >> + */ >> + >> +/** >> + * V4L2 Request API device details. >> + * >> + * Allocated as AVHWDeviceContext.hwctx >> + */ >> +typedef struct AVV4L2RequestDeviceContext { >> + /** >> + * File descriptor of media device. >> + * >> + * Defaults to -1 for auto-detect. >> + */ >> + int media_fd; >> +} AVV4L2RequestDeviceContext; >> + >> +#endif /* AVUTIL_HWCONTEXT_V4L2REQUEST_H */ > > Any reason you're not using hwcontext_drm.h? > The DRM hwdevice/hwcontext requires a DRM/DRI device, however V4L2 decoding does not require a DRM/DRI device at all to do decode. This became fully apparent on a Rockchip RK3588 device that at the time did not have gpu or display support in mainline, yet it had a working AV1 decoder. Using a DRM hwdevice/hwcontext required an application to supply a path to a none existing DRI device. Instead a separate new hwdevice type is introduced, for now it can be used to define a specific media device to use /dev/mediaX, in future it could be extended to support options to specify what /dev/videoX device to use for decoding. These hwaccels only want to produce AV_PIX_FMT_DRM_PRIME output buffers and does not want to be tied to any DRM/DRI device, if there is better ways to do this, please advise. Regards, Jonas _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2024-08-06 16:43 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-08-06 9:05 [FFmpeg-devel] [PATCH v2 0/8] Add V4L2 Request API hwaccels for MPEG2, H.264 and HEVC Jonas Karlman 2024-08-06 9:06 ` [FFmpeg-devel] [PATCH v2 1/8] avutil/hwcontext: Add hwdevice type for V4L2 Request API Jonas Karlman 2024-08-06 12:46 ` Lynne via ffmpeg-devel 2024-08-06 16:43 ` Jonas Karlman [this message] 2024-08-06 9:06 ` [FFmpeg-devel] [PATCH v2 2/8] avcodec: Add common V4L2 Request API code Jonas Karlman 2024-08-06 9:06 ` [FFmpeg-devel] [PATCH v2 3/8] avcodec/v4l2request: Probe for a capable media and video device Jonas Karlman 2024-08-06 9:06 ` [FFmpeg-devel] [PATCH v2 4/8] avcodec/v4l2request: Add common decode support for hwaccels Jonas Karlman 2024-08-06 9:06 ` [FFmpeg-devel] [PATCH v2 5/8] avcodec: Add V4L2 Request API mpeg2 hwaccel Jonas Karlman 2024-08-06 9:06 ` [FFmpeg-devel] [PATCH v2 6/8] avcodec/h264dec: add ref_pic_marking and pic_order_cnt bit_size to slice context Jonas Karlman 2024-08-06 9:06 ` [FFmpeg-devel] [PATCH v2 7/8] avcodec: Add V4L2 Request API h264 hwaccel Jonas Karlman 2024-08-06 9:06 ` [FFmpeg-devel] [PATCH v2 8/8] avcodec: Add V4L2 Request API hevc hwaccel Jonas Karlman
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=ecfc9c5a-7582-4862-9ffb-a12741d2f0f9@kwiboo.se \ --to=jonas@kwiboo.se \ --cc=dev@lynne.ee \ --cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git