diff options
author | Hans Verkuil <hverkuil@xs4all.nl> | 2010-04-06 11:44:39 -0300 |
---|---|---|
committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2010-05-19 12:57:09 -0300 |
commit | dd1ad942ac0b1bb7f72f9f3d822ec937aa07dc4d (patch) | |
tree | 7a02aa76d5b1b4c04f7d6493b0516577dfe31d57 /Documentation | |
parent | 626e2acfdce76b5a6a1daa4bc8ef556d507f5941 (diff) | |
download | linux-dd1ad942ac0b1bb7f72f9f3d822ec937aa07dc4d.tar.gz linux-dd1ad942ac0b1bb7f72f9f3d822ec937aa07dc4d.tar.xz |
V4L/DVB: v4l2-framework.txt: fix incorrect statement
After unregister_device all fileops are blocked, except for ioctls.
So it is not just the open that is blocked, others are as well.
Signed-off-by: Hans Verkuil <hverkuil@xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/video4linux/v4l2-framework.txt | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/Documentation/video4linux/v4l2-framework.txt b/Documentation/video4linux/v4l2-framework.txt index 5155700c206b..5b9205a17ae7 100644 --- a/Documentation/video4linux/v4l2-framework.txt +++ b/Documentation/video4linux/v4l2-framework.txt @@ -545,12 +545,11 @@ unregister them: This will remove the device nodes from sysfs (causing udev to remove them from /dev). -After video_unregister_device() returns no new opens can be done. - -However, in the case of USB devices some application might still have one -of these device nodes open. You should block all new accesses to read, -write, poll, etc. except possibly for certain ioctl operations like -queueing buffers. +After video_unregister_device() returns no new opens can be done. However, +in the case of USB devices some application might still have one of these +device nodes open. So after the unregister all file operations will return +an error as well, except for the ioctl and unlocked_ioctl file operations: +those will still be passed on since some buffer ioctls may still be needed. When the last user of the video device node exits, then the vdev->release() callback is called and you can do the final cleanup there. |