> -----Original Message----- > From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > owner@xxxxxxxxxxxxxxx] On Behalf Of Archit Taneja > Sent: Monday, July 19, 2010 5:40 PM > To: tomi.valkeinen@xxxxxxxxx > Cc: linux-omap@xxxxxxxxxxxxxxx; Semwal, Sumit > Subject: [PATCH 0/3] OMAP: DSS2: Add Zorder Support on OMAP4 > > From: Sumit Semwal <sumit.semwal@xxxxxx> > > This patch series adds Zorder Support on OMAP4, this feature > allows deciding the visibility order of the overlays based on > the Zorder value given to a sysfs attribute of the overlay object. > > Since this feature is not supported on OMAP3 and OMAP2, the sysfs > attibutes always return Zorder as 0 and do not write to dispc registers > for non OMAP4 architectures. > > This patch series applies over the submitted series: > > https://patchwork.kernel.org/patch/112648/ > > Sumit Semwal (3): > OMAP: DSS2: Zorder enum in display.h > OMAP: DSS2: Zorder functions for DISPC > OMAP: DSS2: Zorder sysfs attributes, out of bound checks and > initialization [Hiremath, Vaibhav] Archit, Here also I think we can merge all of these patches into single patch, something like, OMAP: DSS2: Add support for Zorder feature (applicable for OMAP4 & more) OR, worst case you can split it into 2 patches, something like, OMAP: DSS2: Add support for Zorder feature (applicable for OMAP4 & more) OMAP: DSS2: Add set/enable SYFS interface for Zorder feature Thanks, Vaibhav > --- > arch/arm/plat-omap/include/plat/display.h | 8 ++++ > drivers/video/omap2/dss/dispc.c | 23 +++++++++++++ > drivers/video/omap2/dss/dss.h | 3 ++ > drivers/video/omap2/dss/manager.c | 4 ++ > drivers/video/omap2/dss/overlay.c | 51 > +++++++++++++++++++++++++++++ > 5 files changed, 89 insertions(+), 0 deletions(-) > -- > 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 -- 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
