public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>
Subject: Re: Proposal: removal of old vb1 or custom streaming I/O drivers
Date: Wed, 10 Aug 2022 12:24:16 +0200	[thread overview]
Message-ID: <20220810122409.5303e8f9@coco.lan> (raw)
In-Reply-To: <a071cf35-3ed6-3c1b-4546-d4536f1fb6f3@xs4all.nl>

Em Wed, 10 Aug 2022 10:18:56 +0200
Hans Verkuil <hverkuil@xs4all.nl> escreveu:

> We have the following drivers still using vb1:
> 
> PCI: saa7146, bt8xx, cx18
> USB: zr364xx, tm6000
> platform: ti/davinci/vpfe_capture, nxp/fsl-viu
> staging: atomisp
> 
> And these drivers rolls their own streaming I/O implementation:
> 
> pci: meye
> usb: cpia2
> staging: stkwebcam (deprecated, to be removed by the end of the year)
> 
> I think we should bite the bullet and move all of these drivers to staging,
> mark them deprecated and delete them some time next year if nobody will
> convert them to vb2.
> 
> That includes atomisp: is that going anywhere? Unless someone does the
> hard work of converting it to vb2 I think it should be removed as well.

There have been improvements at atomisp driver. Hans de Goede has been
doing some work. As far as I understand, he's planning to get VB2 and
libcamera support for it. I'm also working on it when I have some spare
time available.

> The two drivers most likely to still be in use somewhere are bt8xx and
> cx18. If it turns out that we can't remove them (yet), then I can probably
> justify the time to convert cx18 to vb2 myself.

Yeah, bt8xx is probably still widely used, specially on analog camera
multi-port capture scenarios. Not sure about cx18 usage those days.

IMO, once we get bt8xx, atomisp (and maybe cx18) converted to VB2, it
should be OK to remove the other drivers. 

For now, we can move them to staging, adding a TODO explaining that they
should be ported to VB2 or they'll be removed.

Scheduling removal to the end of the year is probably not doable, as
the patch moving them to staging would be merged only around Oct.
We should grant at least two Kernel cycles for people to convert the
drivers - assuming that someone would do that for some driver(s).

> And for bt8xx I would probably be willing to convert it to vb2 as well,
> provided we can strip the overlay support from the driver (since, if memory
> serves, vb2 doesn't support that) and convert it to vb2. It's a big job, though.

It sounds OK on my eyes to remove overlay support from bt8xx during VB2
conversion. We should probably add a warning about such removal before
that (see below).

> One other thing we can do is to deprecate/remove video capture overlay support
> (in the sense of video capture hardware writing directly to a framebuffer).
> 
> It's supported by saa7146, bttv, saa7134 and fsl-viu. If we remove vb1
> drivers, then that would leave only saa7134 that still supports it.
> 
> Removing the API will simplify things.

It probably makes sense to add an error-level printks, printed only once,
when someone uses VIDIOC_OVERLAY ioctl, warning that this is a deprecated
feature that will be removed soon, for the drivers that still supports it.

For sure once we get rid of the VB1 drivers that use overlay, it makes
sense to also remove its support for saa7134. Maybe even before ;-)

Thanks,
Mauro

  reply	other threads:[~2022-08-10 10:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05 11:35 [ANN] Media Summit at ELCE Dublin, September 12: Draft Agenda V1 Hans Verkuil
2022-08-05 13:25 ` Laurent Pinchart
2022-08-22  8:21   ` Benjamin MUGNIER
2022-08-05 14:56 ` Hans Verkuil
2022-08-09  9:38 ` Michael Tretter
2022-08-09 10:38   ` Hans Verkuil
2022-08-09 10:18 ` Michael Olbrich
2022-08-09 10:39   ` Hans Verkuil
2022-08-09 13:01 ` Hans Verkuil
2022-08-09 13:02   ` Laurent Pinchart
2022-08-10  8:18     ` Proposal: removal of old vb1 or custom streaming I/O drivers Hans Verkuil
2022-08-10 10:24       ` Mauro Carvalho Chehab [this message]
2022-08-10 11:53         ` Laurent Pinchart
2022-08-10 14:27         ` Hans de Goede
2022-08-10 17:05           ` Mauro Carvalho Chehab
2022-08-18  1:33 ` [ANN] Media Summit at ELCE Dublin, September 12: Draft Agenda V1 Niklas Söderlund
2022-08-18  7:04   ` 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=20220810122409.5303e8f9@coco.lan \
    --to=mchehab@kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=hverkuil@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox