Hi,
Here is an attempt at supporting the MIPI-CSI2 TX block from Cadence.
This IP block is able to receive 4 video streams and stream them over
a MIPI-CSI2 link using up to 4 lanes. Those streams are basically the
interfaces to controllers generating some video signals, like a camera
or a pattern generator.
It is able to map input streams to CSI2 virtual channels and datatypes
dynamically. The streaming devices choose their virtual channels
through an additional signal that is transparent to the CSI2-TX. The
datatypes however are yet another additional input signal, and can be
mapped to any CSI2 datatypes.
Since v4l2 doesn't really allow for that setup at the moment, this
preliminary version is a rather dumb one in order to start the
discussion on how to address this properly.
Let me know what you think!
Maxime
Changes from v2:
- Use SPDX license header
- Use the lane mapping from DT
Changes from v1:
- Add a subdev notifier and start our downstream subdevice in
s_stream
- Based the decision to enable the stream or not on the link state
instead of whether a format was being set on the pad
- Put the controller back in reset when stopping the pipeline
- Clarified the enpoints number in the DT binding
- Added a default format for the pads
- Added some missing const
- Added more explicit comments
- Rebased on 4.15
Maxime Ripard (2):
dt-bindings: media: Add Cadence MIPI-CSI2 TX Device Tree bindings
v4l: cadence: Add Cadence MIPI-CSI2 TX driver
.../devicetree/bindings/media/cdns,csi2tx.txt | 98 ++++
drivers/media/platform/cadence/Kconfig | 6 +
drivers/media/platform/cadence/Makefile | 1 +
drivers/media/platform/cadence/cdns-csi2tx.c | 582 +++++++++++++++++++++
4 files changed, 687 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/cdns,csi2tx.txt
create mode 100644 drivers/media/platform/cadence/cdns-csi2tx.c
--
2.14.3
