Hello, in this v3 I have re-used as much as possible the existing infrastructure by using the v4l2-mediabus.h defined V4L2_MBUS_* flags and using the existing struct v4l2_mbus_config as argument of the new operations. I've done so in order to first port all existing users to the new operation, which is now done in this version. Most of the existing users are i2c camera drivers reporting a static media bus configuration though g_mbus_config. Porting them is performed in a single hopefully not controversial patch [2/8] Two existing users stand-out, and they've probably been developed together: pxa_camera and ov6650. Those have bee ported separately in single patches with extensive change logs as their operations semantic had to change to port them to use the new operations. Not having any of those two platforms, the changes have been compile-tested only. The only existing users of the s|g_mbus_config ops are now the soc_camera based drivers currently living in staging. The last three patches are similar to the ones posted in v2, with the exception that they have been updated to use the V4L2_MBUS_* flags as well. Will report again the use cases I'm trying to address here: ------------------------------------------------------------------------------ Quoting: https://patchwork.kernel.org/cover/10855919/ "The use case this series cover is the following one: the Gen-3 R-Car boards include an ADV748x HDMI/CVBS to CSI-2 converter connected to its CSI-2 receivers. The ADV748x chip has recently gained support for routing both HDMI and analogue video streams through its 4 lanes TXA transmitter, specifically to support the Ebisu board that has a single CSI-2 receiver, compared to all other Gen-3 board where the ADV748x TXes are connected to different CSI-2 receivers, and where analogue video is streamed out from the ADV748x single lane TXB transmitter. To properly support transmission of analogue video through TXA, the number of data lanes shall be dynamically reduced to 1, in order to comply with the MIPI CSI-2 minimum clock frequency requirements" During the discussion of the RFC, Dave reported another use case for media bus parameter negotiation on his platform: https://patchwork.kernel.org/patch/10855923/#22569149 Hyun is now using this series to configure GMSL devices. ------------------------------------------------------------------------------ Thanks j v2->v3: - Re-use v4l2_mbus_config and V4L2_MBUS_* flags - Port existing drivers - Update adv748x and rcar-csi2 patches to use V4L2_MBUS_* flags v1->v2: - Address Sakari's comment to use unsigned int in place of bools - Add two new patches to address documentation - Adjust rcar-csi2 patch as much as possible according to Niklas comments - Add Niklas's tags Jacopo Mondi (8): media: v4l2-subdv: Introduce [s|g]et_mbus_config pad ops media: i2c: Use the new get_mbus_config pad op media: i2c: ov6650: Use new [g|s]_mbus_config op media: pxa_camera: Use the new set_mbus_config op media: v4l2-subdev: Deprecate g_mbus_config video op media: i2c: adv748x: Adjust TXA data lanes number media: i2c: adv748x: Implement get_mbus_config media: rcar-csi2: Negotiate data lanes number drivers/media/i2c/adv7180.c | 7 +- drivers/media/i2c/adv748x/adv748x-core.c | 31 +++- drivers/media/i2c/adv748x/adv748x-csi2.c | 31 ++++ drivers/media/i2c/adv748x/adv748x.h | 1 + drivers/media/i2c/ml86v7667.c | 7 +- drivers/media/i2c/mt9m001.c | 7 +- drivers/media/i2c/mt9m111.c | 7 +- drivers/media/i2c/ov6650.c | 56 ++++-- drivers/media/i2c/ov9640.c | 7 +- drivers/media/i2c/tc358743.c | 7 +- drivers/media/i2c/tvp5150.c | 7 +- drivers/media/platform/pxa_camera.c | 184 +++++--------------- drivers/media/platform/rcar-vin/rcar-csi2.c | 61 ++++++- include/media/v4l2-subdev.h | 34 +++- 14 files changed, 259 insertions(+), 188 deletions(-) -- 2.26.2
