redonkable
/
alistair23-linux
1
0
Fork 0
Code Releases Activity

media: v4l2-fwnode: Say it's fine to use v4l2_fwnode_endpoint_parse 

Earlier it was expected that there would be more variable size endpoint
properties and that most if not all drivers would need them. For that
reason it was expected also that v4l2_fwnode_endpoint_parse would no
longer be needed.

What actually happened that not all drivers require "link-frequencies",
the only variable size media endpoint property without a small upper
limit. Therefore drivers that do not need that information are fine using
v4l2_fwnode_endpoint_parse. So don't tell drivers to use
v4l2_fwnode_endpoint_alloc_parse in all cases.

Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Reviewed-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
zero-sugar-mainline-defconfig
Sakari Ailus 2020-09-30 16:34:43 +02:00 committed by Mauro Carvalho Chehab
parent 20936f7734
commit 3be682fac6
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
include/media/v4l2-fwnode.h
View File

@ -245,9 +245,9 @@ struct v4l2_fwnode_connector {
*
* The function does not change the V4L2 fwnode endpoint state if it fails.
*
* NOTE: This function does not parse properties the size of which is variable
* without a low fixed limit. Please use v4l2_fwnode_endpoint_alloc_parse() in
* new drivers instead.
* NOTE: This function does not parse "link-frequencies" property as its size is
* not known in advance. Please use v4l2_fwnode_endpoint_alloc_parse() if you
* need properties of variable size.
*
* Return: %0 on success or a negative error code on failure:
* %-ENOMEM on memory allocation failure