On 6 October 2016 at 16:05, Tomi Valkeinen <tomi.valkeinen@xxxxxx> wrote: > Ah I spoke too soon. Gamma table is supported for OMAP4+. OMAP3 deals > with the gamma table in different way, and that's not implemented. Ah it writes directly to the gamma table. Wouldn't omap3-style loading (which iirc is also supported in omap4+ for the lcd1 output at least) be preferable anyhow since it is frame-synchronized hence avoids tearing? It doesn't look terribly complicated either: stick the table in dma coherent memory, write the address to register and set a bit to load it? The biggest annoyance is probably the requirement to enable the graphics pipeline even if it isn't being used otherwise (and then disable it again on palette loaded irq). Of course I don't know if there's any fun details not apparent from the documentation. Matthijs -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
