> -----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; Nilofer, > Samreen; Taneja, Archit > Subject: [PATCH 1/3] OMAP: DSS2: Zorder enum in display.h > > From: Sumit Semwal <sumit.semwal@xxxxxx> > > Add Zorder enum in display.h > Patches 1 and 2 in the series can easily be conbined into one. Separating few line changes in header file from implementation across 2 patches isn't useful. > Signed-off-by: Sumit Semwal <sumit.semwal@xxxxxx> > Signed-off-by: Samreen <samreen@xxxxxx> > Signed-off-by: Archit Taneja <archit@xxxxxx> > --- > arch/arm/plat-omap/include/plat/display.h | 8 ++++++++ > 1 files changed, 8 insertions(+), 0 deletions(-) > > diff --git a/arch/arm/plat-omap/include/plat/display.h > b/arch/arm/plat-omap/include/plat/display.h > index d1da317..197ce8c > --- a/arch/arm/plat-omap/include/plat/display.h > +++ b/arch/arm/plat-omap/include/plat/display.h > @@ -206,6 +206,13 @@ enum omap_overlay_manager_caps { > OMAP_DSS_OVL_MGR_CAP_DISPC = 1 << 0, > }; > > +enum omap_overlay_zorder { > + OMAP_DSS_OVL_ZORDER_0 = 0x0, > + OMAP_DSS_OVL_ZORDER_1 = 0x1, > + OMAP_DSS_OVL_ZORDER_2 = 0x2, > + OMAP_DSS_OVL_ZORDER_3 = 0x3, > +}; Is "_DSS_" really needed in these emums? considering that enum itself doesn't contain "_dss_" in its name. ~sanjeev > + > /* RFBI */ > > struct rfbi_timings { > @@ -308,6 +315,7 @@ struct omap_overlay_info { > u16 out_width; /* if 0, out_width == width */ > u16 out_height; /* if 0, out_height == height */ > u8 global_alpha; > + enum omap_overlay_zorder zorder; > }; > > struct omap_overlay { > -- > 1.6.3.3 > > -- > 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
