diff options
| -rw-r--r-- | Documentation/video4linux/v4l2-framework.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/video4linux/v4l2-framework.txt b/Documentation/video4linux/v4l2-framework.txt index ff124374e9ba..cc350624237d 100644 --- a/Documentation/video4linux/v4l2-framework.txt +++ b/Documentation/video4linux/v4l2-framework.txt | |||
| @@ -340,6 +340,12 @@ Make sure to call v4l2_device_unregister_subdev(sd) when the remove() callback | |||
| 340 | is called. This will unregister the sub-device from the bridge driver. It is | 340 | is called. This will unregister the sub-device from the bridge driver. It is |
| 341 | safe to call this even if the sub-device was never registered. | 341 | safe to call this even if the sub-device was never registered. |
| 342 | 342 | ||
| 343 | You need to do this because when the bridge driver destroys the i2c adapter | ||
| 344 | the remove() callbacks are called of the i2c devices on that adapter. | ||
| 345 | After that the corresponding v4l2_subdev structures are invalid, so they | ||
| 346 | have to be unregistered first. Calling v4l2_device_unregister_subdev(sd) | ||
| 347 | from the remove() callback ensures that this is always done correctly. | ||
| 348 | |||
| 343 | 349 | ||
| 344 | The bridge driver also has some helper functions it can use: | 350 | The bridge driver also has some helper functions it can use: |
| 345 | 351 | ||