On Thu, Jun 23, 2016 at 9:13 AM, Archit Taneja <architt@xxxxxxxxxxxxxx> wrote: > The DSI host and PHY driver currently expects the DT bindings to provide > custom properties "qcom,dsi-host-index" and "qcom,dsi-phy-index" so that > the driver can identify which DSI instance it is. > > The binding isn't acceptable, but the driver still needs to figure out > what its instance id. This is now done by storing the mmio starting > addresses for each DSI instance in every SoC version in the driver. The > driver then identifies the index number by trying to match the stored > address with comparing the resource start address we get from DT. I looked a bit more at this. It seems at least one reason you need to know which DSI instance is which is when ganging the instances together and needing to define the clock master. You could define a property for the clock master for example. Rob _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
