aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/media/v4l2-core/v4l2-async.c
diff options
context:
space:
mode:
authorEzequiel Garcia <[email protected]>2021-01-18 01:52:48 +0000
committerMauro Carvalho Chehab <[email protected]>2021-02-06 07:42:14 +0000
commit3a2822bfe45c50abd9f76a8547a77a1f6a0e8c8d (patch)
treee4e461220cf02fc7db8179e355d7f5aaf7d9a796 /drivers/media/v4l2-core/v4l2-async.c
parentmedia: stm32: Use v4l2_async_notifier_add_fwnode_remote_subdev (diff)
downloadkernel-3a2822bfe45c50abd9f76a8547a77a1f6a0e8c8d.tar.gz
kernel-3a2822bfe45c50abd9f76a8547a77a1f6a0e8c8d.zip
media: exynos4-is: Use v4l2_async_notifier_add_fwnode_remote_subdev
The use of v4l2_async_notifier_add_subdev will be discouraged. Drivers are instead encouraged to use a helper such as v4l2_async_notifier_add_fwnode_remote_subdev. This fixes a misuse of the API, as v4l2_async_notifier_add_subdev should get a kmalloc'ed struct v4l2_async_subdev, removing some boilerplate code while at it. Use the appropriate helper v4l2_async_notifier_add_fwnode_remote_subdev, which handles the needed setup, instead of open-coding it. Signed-off-by: Ezequiel Garcia <[email protected]> Reviewed-by: Jacopo Mondi <[email protected]> Reviewed-by: Helen Koike <[email protected]> Signed-off-by: Sakari Ailus <[email protected]> Signed-off-by: Mauro Carvalho Chehab <[email protected]>
Diffstat (limited to 'drivers/media/v4l2-core/v4l2-async.c')
0 files changed, 0 insertions, 0 deletions