DSI host controllers these days can be ganged together to drive larger displays. Every SoC vendor supporting this is trying to add their own DT property so that the corresponding drivers can identify that they need to operate in the dual DSI mode. If we use the graph bindings, we don't really need an additional DT property in the DSI host controller to tell it that it's operating in dual-channel mode. It's something that can be inferred from the bindings itself.
The first patch adds some explanation on how to deal with peripherals that do DSI, but have a different control bus. This is something we've already started using, but didn't have properly documented anywhere.
The second patch proposes bindings for DSI hosts/peripherals that implement dual-channel DSI.
Changes in v3: - Fixed a minor typo. - Added Reviewed-by tags. - Changed from RFC to PATCH.
Changes in v2: - Incorported Rob's comments.
Archit Taneja (2): dt-bindings: mipi-dsi: Add info about peripherals with non-DSI control bus dt-bindings: mipi-dsi: Add dual-channel DSI related info
.../devicetree/bindings/display/mipi-dsi-bus.txt | 153 +++++++++++++++++++-- 1 file changed, 145 insertions(+), 8 deletions(-)