From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: linux-media@vger.kernel.org
Subject: [RFC PATCH 0/9] Remove destructive video overlay and clipping
Date: Wed, 1 Mar 2023 12:18:41 +0100 [thread overview]
Message-ID: <20230301111850.607515-1-hverkuil-cisco@xs4all.nl> (raw)
Destructive video overlay support relies on userspace passing the address of
the framebuffer to the driver with VIDIOC_S_FBUF. The PCI driver can then DMA
the captured frame straight into the framebuffer. This was useful 20 years ago,
but today not so much.
Typically userspace would get the address from the /dev/fbX device using the
FBIOGET_FSCREENINFO ioctl.
But drm_fb_helper.c sets the smem_start field explicitly to 0 unless:
1) CONFIG_DRM_FBDEV_LEAK_PHYS_SMEM is set, and
2) CONFIG_EXPERT is set, and
3) set the drm_kms_helper module parameter drm_leak_fbdev_smem to 1.
Effectively destructive overlay support is dead today.
This patch series removes it from the remaining drivers.
As a result the support for clipping using clipping rectangles or
a bitmap can now also be removed.
Regards,
Hans
Hans Verkuil (9):
saa7146: drop overlay support
saa7134: drop overlay support
bttv: drop overlay support
vivid: drop overlay support
vivid: drop bitmap and clipping output overlay support
v4l2-core: drop v4l2_window clipping and bitmap support
videodev.h: drop V4L2_FBUF_CAP_LIST/BITMAP_CLIPPING
v4l2-core: zero field base in struct v4l2_framebuffer
Documentation: userspace-api: media: drop clipping, destructive
overlays
.../userspace-api/media/v4l/dev-overlay.rst | 10 +-
.../userspace-api/media/v4l/vidioc-g-fbuf.rst | 52 +--
drivers/media/common/saa7146/saa7146_fops.c | 22 -
drivers/media/common/saa7146/saa7146_hlp.c | 296 ------------
drivers/media/common/saa7146/saa7146_video.c | 326 +------------
drivers/media/pci/bt8xx/Kconfig | 2 +-
drivers/media/pci/bt8xx/btcx-risc.c | 153 ------
drivers/media/pci/bt8xx/bttv-cards.c | 15 -
drivers/media/pci/bt8xx/bttv-driver.c | 436 +-----------------
drivers/media/pci/bt8xx/bttv-risc.c | 131 ------
drivers/media/pci/bt8xx/bttvp.h | 28 +-
drivers/media/pci/saa7134/saa7134-cards.c | 1 -
drivers/media/pci/saa7134/saa7134-core.c | 32 --
drivers/media/pci/saa7134/saa7134-video.c | 411 +----------------
drivers/media/pci/saa7134/saa7134.h | 13 -
drivers/media/test-drivers/vivid/vivid-core.c | 49 +-
drivers/media/test-drivers/vivid/vivid-core.h | 19 -
.../test-drivers/vivid/vivid-kthread-cap.c | 131 +-----
.../media/test-drivers/vivid/vivid-vid-cap.c | 272 -----------
.../media/test-drivers/vivid/vivid-vid-cap.h | 3 -
.../media/test-drivers/vivid/vivid-vid-out.c | 74 ---
drivers/media/v4l2-core/v4l2-compat-ioctl32.c | 83 +---
drivers/media/v4l2-core/v4l2-ioctl.c | 77 +---
drivers/staging/media/av7110/av7110_v4l.c | 17 +-
include/media/drv-intf/saa7146_vv.h | 21 -
include/uapi/linux/videodev2.h | 2 +
26 files changed, 90 insertions(+), 2586 deletions(-)
--
2.39.1
next reply other threads:[~2023-03-01 11:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 11:18 Hans Verkuil [this message]
2023-03-01 11:18 ` [RFC PATCH 1/9] saa7146: drop overlay support Hans Verkuil
2023-03-01 11:18 ` [RFC PATCH 2/9] saa7134: " Hans Verkuil
2023-03-01 11:18 ` [RFC PATCH 3/9] bttv: " Hans Verkuil
2023-03-01 11:18 ` [RFC PATCH 4/9] vivid: " Hans Verkuil
2023-03-01 11:18 ` [RFC PATCH 5/9] vivid: drop bitmap and clipping output " Hans Verkuil
2023-03-01 11:18 ` [RFC PATCH 6/9] v4l2-core: drop v4l2_window clipping and bitmap support Hans Verkuil
2023-03-01 11:18 ` [RFC PATCH 7/9] videodev.h: drop V4L2_FBUF_CAP_LIST/BITMAP_CLIPPING Hans Verkuil
2023-03-01 11:18 ` [RFC PATCH 8/9] v4l2-core: zero field base in struct v4l2_framebuffer Hans Verkuil
2023-03-01 13:40 ` kernel test robot
2023-03-01 11:18 ` [RFC PATCH 9/9] Documentation: userspace-api: media: drop clipping, destructive overlays 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=20230301111850.607515-1-hverkuil-cisco@xs4all.nl \
--to=hverkuil-cisco@xs4all.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.