On Mon, Jun 19, 2017 at 11:51 AM, Philippe CORNU <philippe.cornu@xxxxxx> wrote: > On 06/08/2017 05:40 PM, Rob Herring wrote: >> On Fri, Jun 02, 2017 at 04:37:11PM +0200, Philippe CORNU wrote: >>> This patch adds documentation of device tree bindings for the >>> Synopsys DesignWare MIPI DSI host DRM bridge driver. >>> >>> Signed-off-by: Philippe CORNU <philippe.cornu@xxxxxx> >>> --- >>> .../bindings/display/bridge/dw_mipi_dsi.txt | 30 ++++++++++++++++++++++ >>> 1 file changed, 30 insertions(+) >>> create mode 100644 Documentation/devicetree/bindings/display/bridge/dw_mipi_dsi.txt >>> >>> diff --git a/Documentation/devicetree/bindings/display/bridge/dw_mipi_dsi.txt b/Documentation/devicetree/bindings/display/bridge/dw_mipi_dsi.txt >>> new file mode 100644 >>> index 0000000..1d7c438 >>> --- /dev/null >>> +++ b/Documentation/devicetree/bindings/display/bridge/dw_mipi_dsi.txt >>> @@ -0,0 +1,30 @@ >>> +Synopsys DesignWare MIPI DSI host controller >>> +============================================ >>> + >>> +This document defines device tree properties for the Synopsys DesignWare MIPI >>> +DSI host controller. It doesn't constitue a device tree binding specification >>> +by itself but is meant to be referenced by platform-specific device tree >>> +bindings. >>> + >>> +When referenced from platform device tree bindings the properties defined in >>> +this document are defined as follows. The platform device tree bindings are >>> +responsible for defining whether each property is required or optional. >>> + >>> +- reg: Memory mapped base address and length of the DWC MIPI DSI >>> + registers. (mandatory) >>> + >>> +- clocks: References to all the clocks specified in the clock-names property >>> + as specified in [1]. (mandatory) >>> + >>> +- clock-names: "pclk" is peripheral clock for either AHB and APB. (mandatory) >> >> Seems strange there's not also a pixel or bit clock? Or this gets driven >> from the phy? >> > Hi Rob, > And many thanks for your comments :) > > There is a "physical" pixel clock entering into the "DSI controller IP" > but the "DSI controller driver" does not need to control (or read) it > with the dt because this clock information (the frequency) is also > available in panel timings and the drm/kms framework will propagate the > panel timings in the drm/kms "crtc/encoder/bridge&panel/connector..." > chain. Then, the DSI controller driver will compute phy parameters > according to these panel timings. > Adding a pixel clock dependency in the dt here is then not necessary as > the frequency information comes through the panel timings. Even if the Linux driver doesn't currently need to control the pixel clock it should still be defined in the binding. Bindings are what you physically have, not just what the driver needs or doesn't need. Rob _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
