Hi, On Monday 16 of December 2013 08:27:17 Vaibhav Bedia wrote: > Hi, > > On Mon, Dec 16, 2013 at 7:01 AM, Abhilash Kesavan <[email protected]> > wrote: [snip] > > + { EXYNOS5_CMU_RESET_GSCL_SYS_PWR_REG, { 0x0, 0x0, > > 0x0} }, > > + { EXYNOS5_CMU_RESET_ISP_SYS_PWR_REG, { 0x0, 0x0, > > 0x0} }, > > + { EXYNOS5_CMU_RESET_MFC_SYS_PWR_REG, { 0x0, 0x0, > > 0x0} }, > > + { EXYNOS5_CMU_RESET_G3D_SYS_PWR_REG, { 0x0, 0x0, > > 0x0} }, > > + { EXYNOS5420_CMU_RESET_DISP1_SYS_PWR_REG, { 0x0, 0x0, > > 0x0} }, > > + { EXYNOS5420_CMU_RESET_MAU_SYS_PWR_REG, { 0x0, 0x0, > > 0x0} }, > > + { EXYNOS5420_CMU_RESET_G2D_SYS_PWR_REG, { 0x0, 0x0, > > 0x0} }, > > + { EXYNOS5420_CMU_RESET_MSC_SYS_PWR_REG, { 0x0, 0x0, > > 0x0} }, > > + { EXYNOS5420_CMU_RESET_FSYS_SYS_PWR_REG, { 0x0, 0x0, > > 0x0} }, > > + { PMU_TABLE_END,}, > > +}; > > + > > Looking at a rather long list of register defines and soc_is_* checks here > makes me wonder how this is any different from the static data that the > other SoC vendors (TI) are trying very hard to move out of arch/arm...
Well, this data will eventually get moved to a PMU driver once drivers/syslib (as discussed on KS in Edinburgh) infrastructure shows up. We can't get rid of these data from kernel sources, since there is no other place where they would fit. (No, DT is not such place.) Best regards, Tomasz -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
