summaryrefslogtreecommitdiff
path: root/Documentation/driver-api
diff options
context:
space:
mode:
authorLuca Ceresoli <luca@lucaceresoli.net>2020-09-21 22:21:32 +0200
committerMauro Carvalho Chehab <mchehab+huawei@kernel.org>2020-09-27 11:30:51 +0200
commitc1ebbe52bd6229c554a8e7f6a17e03a929c95999 (patch)
tree8b3d74e354fcf79cb549e269e2750ee611c02d9f /Documentation/driver-api
parent6cab05cf699062a61ae56e6c8e28f15d176ab42d (diff)
media: docs: v4l2-subdev: fix typo
Fix "Helper functions exists" -> "Helper functions exist". Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net> Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Diffstat (limited to 'Documentation/driver-api')
-rw-r--r--Documentation/driver-api/media/v4l2-subdev.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/driver-api/media/v4l2-subdev.rst b/Documentation/driver-api/media/v4l2-subdev.rst
index 9a7dddd97f5a..9ea16a8c3bde 100644
--- a/Documentation/driver-api/media/v4l2-subdev.rst
+++ b/Documentation/driver-api/media/v4l2-subdev.rst
@@ -34,7 +34,7 @@ provides host private data for that purpose that can be accessed with
From the bridge driver perspective, you load the sub-device module and somehow
obtain the :c:type:`v4l2_subdev` pointer. For i2c devices this is easy: you call
``i2c_get_clientdata()``. For other buses something similar needs to be done.
-Helper functions exists for sub-devices on an I2C bus that do most of this
+Helper functions exist for sub-devices on an I2C bus that do most of this
tricky work for you.
Each :c:type:`v4l2_subdev` contains function pointers that sub-device drivers