On Mon, Nov 04, 2013 at 05:15:19PM +0100, Denis Carikli wrote: > Without that fix, drivers using the fb_videomode_from_videomode > function will not be able to get certain information because > some DISPLAY_FLAGS_* have no corresponding FB_SYNC_*. Please describe how userspace knows how to set these flags. Flags such as the polarity of the hsync and vsync signals are fairly well defined based upon the display mode, but aren't things like data enable and the pixel clock edge a property of the attached LCD panel, which is something that is configured according to the panel which is attached. In other words, this information should not be passed from userspace, but should be part of the DT description about the connected panel. So should be the polarity of the line and frame pulses (iow, hsync and vsync pulses) in the case of a connected panel. Moreover, in the case of a connected LCD panel, chances are it can only support a very limited number of settings, so support for userspace changing the timings is arguably incorrect from a system point of view. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
