media: v4l2: async: Remove notifier subdevs array
All platform drivers have been converted to use v4l2_async_notifier_add_subdev(), in place of adding asd's to the notifier subdevs array. So the subdevs array can now be removed from struct v4l2_async_notifier, and remove the backward compatibility support for that array in v4l2-async.c. Signed-off-by: Steve Longerbeam <slongerbeam@gmail.com> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
This commit is contained in:

committed by
Mauro Carvalho Chehab

parent
d079f94c90
commit
66beb323e4
@@ -259,12 +259,6 @@ typedef int (*parse_endpoint_func)(struct device *dev,
|
||||
* This function may not be called on a registered notifier and may be called on
|
||||
* a notifier only once.
|
||||
*
|
||||
* Do not allocate the notifier's subdevs array, or change the notifier's
|
||||
* num_subdevs field. This is because this function uses
|
||||
* @v4l2_async_notifier_add_subdev to populate the notifier's asd_list,
|
||||
* which is in-place-of the subdevs array which must remain unallocated
|
||||
* and unused.
|
||||
*
|
||||
* The &struct v4l2_fwnode_endpoint passed to the callback function
|
||||
* @parse_endpoint is released once the function is finished. If there is a need
|
||||
* to retain that configuration, the user needs to allocate memory for it.
|
||||
@@ -316,12 +310,6 @@ int v4l2_async_notifier_parse_fwnode_endpoints(
|
||||
* This function may not be called on a registered notifier and may be called on
|
||||
* a notifier only once per port.
|
||||
*
|
||||
* Do not allocate the notifier's subdevs array, or change the notifier's
|
||||
* num_subdevs field. This is because this function uses
|
||||
* @v4l2_async_notifier_add_subdev to populate the notifier's asd_list,
|
||||
* which is in-place-of the subdevs array which must remain unallocated
|
||||
* and unused.
|
||||
*
|
||||
* The &struct v4l2_fwnode_endpoint passed to the callback function
|
||||
* @parse_endpoint is released once the function is finished. If there is a need
|
||||
* to retain that configuration, the user needs to allocate memory for it.
|
||||
|
Reference in New Issue
Block a user