summaryrefslogtreecommitdiff
path: root/linux/Documentation/video4linux/v4l2-framework.txt
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab@redhat.com>2009-03-14 12:28:45 +0100
committerMauro Carvalho Chehab <mchehab@redhat.com>2009-03-14 12:28:45 +0100
commit48beb6bb3e66daddf4c339f5c02710a060d3a0be (patch)
tree6af556d0d546f47fd7bd64db2daafb5b2b6e74ea /linux/Documentation/video4linux/v4l2-framework.txt
parent0f2ea07a22d87dcff3529fd787f8b41ed665bb28 (diff)
downloadmediapointer-dvb-s2-48beb6bb3e66daddf4c339f5c02710a060d3a0be.tar.gz
mediapointer-dvb-s2-48beb6bb3e66daddf4c339f5c02710a060d3a0be.tar.bz2
v4l2-device: add v4l2_device_disconnect
From: Hans Verkuil <hverkuil@xs4all.nl> Call v4l2_device_disconnect when the parent of a hotpluggable device disconnects. This ensures that you do not have a pointer to a device that is no longer present. Priority: normal Signed-off-by: Hans Verkuil <hverkuil@xs4all.nl> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'linux/Documentation/video4linux/v4l2-framework.txt')
-rw-r--r--linux/Documentation/video4linux/v4l2-framework.txt11
1 files changed, 11 insertions, 0 deletions
diff --git a/linux/Documentation/video4linux/v4l2-framework.txt b/linux/Documentation/video4linux/v4l2-framework.txt
index 4207590b2..a31177390 100644
--- a/linux/Documentation/video4linux/v4l2-framework.txt
+++ b/linux/Documentation/video4linux/v4l2-framework.txt
@@ -105,6 +105,17 @@ You unregister with:
Unregistering will also automatically unregister all subdevs from the device.
+If you have a hotpluggable device (e.g. a USB device), then when a disconnect
+happens the parent device becomes invalid. Since v4l2_device has a pointer to
+that parent device it has to be cleared as well to mark that the parent is
+gone. To do this call:
+
+ v4l2_device_disconnect(struct v4l2_device *v4l2_dev);
+
+This does *not* unregister the subdevs, so you still need to call the
+v4l2_device_unregister() function for that. If your driver is not hotpluggable,
+then there is no need to call v4l2_device_disconnect().
+
Sometimes you need to iterate over all devices registered by a specific
driver. This is usually the case if multiple device drivers use the same
hardware. E.g. the ivtvfb driver is a framebuffer driver that uses the ivtv