On Wed, 2010-09-15 at 16:09 +0200, ext arc...@ti.com wrote: > From: Archit Taneja <arc...@ti.com> > > This is a simple approach to prevent scattered cpu_is_omapxxxx checks > in DSS2 by bringing all omap version specific DSS features/values to one > single place, initialize them and expose a set of functions to DSS2 driver > files which return the value/existance of a feature. > > This method provides the following: > -A set of functions which give the value of a feature. > -Functions which add and return the start and end bits of a register field > which varies across omaps. > -A function which checks if a DSS2 feature exists or not on the present > omap (omap_dss_has_feature) > > Whenever a new DSS feature is introduced, its value/existance is specified > for all omaps in omap_dss_feature_init(). > > This patch also fills up a minimal list of features in > omap_dss_features_init(). > The second patch in the series makes use of dss_features to remove some of the > existing omapxxxx checks.
Thanks, applied to DSS2 tree. Tomi -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
