diff options
author | 2020-09-30 16:34:43 +0200 | |
---|---|---|
committer | 2020-11-16 10:31:13 +0100 | |
commit | 3be682fac66ca5829bb18c623c15147628a2d6f8 (patch) | |
tree | dce4cd84afbfb5ab49943bdc2b62eb7dcb2ce44b /lib/stackdepot.c | |
parent | media: v4l2-fwnode: Rework v4l2_fwnode_endpoint_parse documentation (diff) | |
download | linux-3be682fac66ca5829bb18c623c15147628a2d6f8.tar.gz linux-3be682fac66ca5829bb18c623c15147628a2d6f8.tar.bz2 linux-3be682fac66ca5829bb18c623c15147628a2d6f8.zip |
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>
Diffstat (limited to 'lib/stackdepot.c')
0 files changed, 0 insertions, 0 deletions