This series adds new drivers for multiple Maxim GMSL2 and GMSL3 devices, replacing the few GMSL2 drivers already in upstream, and introducing a common framework that can be used to implement such GMSL chips, which avoids code duplication while also adding support for previously unsupported features. While the normally acceptable and polite way would be to extend the current mainline drivers, the choice was made here to add a totally new set of drivers. The current drivers support only a small subset of the possible features, and only a few devices, so the end result after extending them would in any case be essentially fully rewritten, new drivers. This series depends on these two series: * https://lore.kernel.org/lkml/20250306-fpc202-v9-0-2779af6780f6@xxxxxxxxxxx * https://lore.kernel.org/lkml/20250228151730.1874916-1-demonsingur@xxxxxxxxx The following deserializers are supported: * MAX96712 (already exists in staging) * MAX96714 (already exists) * MAX96716 (GMSL2) * MAX96724 (part of existing MAX96712 driver) * MAX9296A (GMSL2) * MAX96792A (GMSL3) The following serializers are supported: * MAX96717 (already exists) * MAX9295A (GMSL2) * MAX96793 (GMSL3) Missing features: * The current TPG implementation makes use of the V4L2_CID_TEST_PATTERN V4L2 control. With V4L2 streams support added, we would like to hook up TPG using the internal pad feature which has not been accepted upstream yet. We decided to leave TPG out for the moment and add it back after internal pads have been accepted. Known backward compatibility breakages: * No default routing. Default routing has been intentionally ommitted as the devices support quite complex routing and it would be unfeasible to provide sane defaults for multi-link deserialziers. It is expected that userspace programs would set appropritate routing. The following list enumerates new features that are supported by the common framework and their respective chip-specific drivers: * Full Streams API support. Most deserializers have support for more than one link, and more than one PHY. Streams support allows configuration of routing between these links and PHYs. * .get_frame_desc() support. Both the serializers and deserializers implement this to query and provide frame descriptor data. This is used in features explained in-depth below. * .get_mbus_config() support. The deserializers implement this to allow upstream devices to query the link frequency of its pads. * Address translation with I2C ATR for the serializers. * I2C MUX where supported by the hardware for deserializers, otherwise I2C ATR translation - some deserializers cannot do muxing since I2C communication channel masking is not available per-link, and the only other way to select links is to turn them off, causing link resets. For such cases, I2C ATR is used to change the address of the serializers at probe time. * Automatic VC remapping on the deserializers. VCs are picked so that if they were unique on the sink pad, they will end up as unique on the source pad they are routed to too, prioritizing using the same VC ID as the sink pad, to facilitate the possibility of using tunnel mode. * Automatic pixel mode / tunnel mode selection. Tunnel mode is used when VC IDs do not need to be changed and all hardware supports tunnel mode, otherwise, pixel mode is used. The serializers are automatically switched between the two by using a private API. * Automatic double mode selection. In pixel mode, double mode can be used to pack two pixels into a single data unit, optimizing bandwidth usage. The serializers are automatically set up to support the double modes determined by the deserializers using a private API. * Automatic data padding. In pixel mode, if the data being transferred uses two different BPPs, data needs to be padded. The serializers automatically set this up depending on the configured double mode settings and incoming data types. * Logging. Both the deserializers and serializers implement the V4L2 .log_status() ops to allow debugging of the internal state and important chip status registers. * PHY modes. Deserializer chips commonly have more than a single PHY. The firmware ports are parsed to determine the modes in which to configure the PHYs (2x4, 4x2, 1x4+2x2, 2x2+1x4, and variations using fewer lanes). * Serializer pinctrl. Serializers implement pinctrl to allow setting configs which would otherwise be inaccessible through GPIO: TX/RX via GMSL link, pull-up & pull-down (with strength), open-drain & push-pull, slew rate, RCLK pin selection. The drivers have been tested on the following hardware combinations, but further testing is welcome to ensure no / minimal breakage: * Raspberry Pi 5 + MAX96724 + 4xMAX96717 + 4xIMX219 * Raspberry Pi 5 + MAX96792A + 1xMAX96793 + 1xMAX96717 + 2xIMX219 * Raspberry Pi 5 + MAX96792A + 2xMAX96717 + 2xIMX219 * Renesas V4H + MAX96712 + 2xMAX96717 + 2xIMX219 Analog Devices is taking responsibility for the maintenance of these drivers and common framework, and plans to add support for new broad-market chips on top of them. Special thanks go to Tomi Valkeinen <tomi.valkeinen+renesas@xxxxxxxxxxxxxxxx> for testing the drivers, helping debug and coming up with ideas / implementations for various features. Cosmin Tanislav (24): dt-bindings: media: i2c: max96717: add myself as maintainer dt-bindings: media: i2c: max96717: reflow text dt-bindings: media: i2c: max96717: add support for I2C ATR dt-bindings: media: i2c: max96717: add support for pinctrl/pinconf dt-bindings: media: i2c: max96717: add support for MAX9295A dt-bindings: media: i2c: max96717: add support for MAX96793 dt-bindings: media: i2c: max96714: add myself as maintainer dt-bindings: media: i2c: max96714: reflow text dt-bindings: media: i2c: max96714: make i2c-gate conditional on compatible dt-bindings: media: i2c: max96714: make ports conditional on compatible dt-bindings: media: i2c: max96714: make supply conditional on compatible dt-bindings: media: i2c: max96714: add support for MAX9296A dt-bindings: media: i2c: max96714: add support for MAX96716A dt-bindings: media: i2c: max96714: add support for MAX96792A dt-bindings: media: i2c: max96712: add myself as maintainer dt-bindings: media: i2c: max96712: use pattern properties for input ports dt-bindings: media: i2c: max96712: increase number of output ports dt-bindings: media: i2c: max96712: add support for I2C MUX dt-bindings: media: i2c: max96712: add support for POC supplies media: i2c: add Maxim GMSL2/3 serializer and deserializer drivers arm64: defconfig: disable deprecated MAX96712 driver staging: media: remove MAX96712 driver media: i2c: remove MAX96717 driver media: i2c: remove MAX96714 driver .../bindings/media/i2c/maxim,max96712.yaml | 49 +- .../bindings/media/i2c/maxim,max96714.yaml | 245 +- .../media/i2c/maxim,max96717-pinctrl.yaml | 71 + .../bindings/media/i2c/maxim,max96717.yaml | 75 +- MAINTAINERS | 13 +- arch/arm64/configs/defconfig | 1 - drivers/media/i2c/Kconfig | 34 +- drivers/media/i2c/Makefile | 3 +- drivers/media/i2c/max96714.c | 1024 -------- drivers/media/i2c/max96717.c | 1103 -------- drivers/media/i2c/maxim-serdes/Kconfig | 53 + drivers/media/i2c/maxim-serdes/Makefile | 6 + drivers/media/i2c/maxim-serdes/max9296a.c | 1146 ++++++++ drivers/media/i2c/maxim-serdes/max96717.c | 1500 +++++++++++ drivers/media/i2c/maxim-serdes/max96724.c | 905 +++++++ drivers/media/i2c/maxim-serdes/max_des.c | 2321 +++++++++++++++++ drivers/media/i2c/maxim-serdes/max_des.h | 135 + drivers/media/i2c/maxim-serdes/max_ser.c | 1584 +++++++++++ drivers/media/i2c/maxim-serdes/max_ser.h | 132 + drivers/media/i2c/maxim-serdes/max_serdes.c | 302 +++ drivers/media/i2c/maxim-serdes/max_serdes.h | 88 + drivers/staging/media/Kconfig | 2 - drivers/staging/media/Makefile | 1 - drivers/staging/media/max96712/Kconfig | 14 - drivers/staging/media/max96712/Makefile | 2 - drivers/staging/media/max96712/max96712.c | 487 ---- 26 files changed, 8523 insertions(+), 2773 deletions(-) create mode 100644 Documentation/devicetree/bindings/media/i2c/maxim,max96717-pinctrl.yaml delete mode 100644 drivers/media/i2c/max96714.c delete mode 100644 drivers/media/i2c/max96717.c create mode 100644 drivers/media/i2c/maxim-serdes/Kconfig create mode 100644 drivers/media/i2c/maxim-serdes/Makefile create mode 100644 drivers/media/i2c/maxim-serdes/max9296a.c create mode 100644 drivers/media/i2c/maxim-serdes/max96717.c create mode 100644 drivers/media/i2c/maxim-serdes/max96724.c create mode 100644 drivers/media/i2c/maxim-serdes/max_des.c create mode 100644 drivers/media/i2c/maxim-serdes/max_des.h create mode 100644 drivers/media/i2c/maxim-serdes/max_ser.c create mode 100644 drivers/media/i2c/maxim-serdes/max_ser.h create mode 100644 drivers/media/i2c/maxim-serdes/max_serdes.c create mode 100644 drivers/media/i2c/maxim-serdes/max_serdes.h delete mode 100644 drivers/staging/media/max96712/Kconfig delete mode 100644 drivers/staging/media/max96712/Makefile delete mode 100644 drivers/staging/media/max96712/max96712.c -- 2.48.1
