[PATCH v3 03/23] v4l: fwnode: The CSI-2 clock is continuous if it's not non-continuous
Sakari Ailus
sakari.ailus at linux.intel.com
Wed Sep 12 21:29:22 UTC 2018
The continuous clock flag was only set if there was a clock or data lanes.
This isn't needed as such a configuration is invalid to begin with. Always
set the continuous clock flag if the non-continuous property is not found.
Signed-off-by: Sakari Ailus <sakari.ailus at linux.intel.com>
Tested-by: Steve Longerbeam <steve_longerbeam at mentor.com>
---
drivers/media/v4l2-core/v4l2-fwnode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/v4l2-core/v4l2-fwnode.c b/drivers/media/v4l2-core/v4l2-fwnode.c
index ab457cf36ba5..cf90ddb5c430 100644
--- a/drivers/media/v4l2-core/v4l2-fwnode.c
+++ b/drivers/media/v4l2-core/v4l2-fwnode.c
@@ -107,7 +107,7 @@ static int v4l2_fwnode_endpoint_parse_csi2_bus(struct fwnode_handle *fwnode,
if (fwnode_property_present(fwnode, "clock-noncontinuous")) {
flags |= V4L2_MBUS_CSI2_NONCONTINUOUS_CLOCK;
pr_debug("non-continuous clock\n");
- } else if (have_clk_lane || bus->num_data_lanes > 0) {
+ } else {
flags |= V4L2_MBUS_CSI2_CONTINUOUS_CLOCK;
}
--
2.11.0
More information about the dri-devel
mailing list