> -----Original Message----- > From: [email protected] [mailto:linux-omap- > [email protected]] On Behalf Of Kevin Hilman > Sent: Thursday, August 26, 2010 4:42 AM > To: Gopinath, Thara > Cc: [email protected]; [email protected]; Sripathy, Vishwanath; > Sawant, Anand; Cousson, Benoit > Subject: Re: [PATCH 08/10] OMAP4: Smartreflex framework extensions > > Thara Gopinath <[email protected]> writes: > > > This patch extends the smartreflex framework to support > > OMAP4. The changes are minor like compiling smartreflex Kconfig > > option for OMAP4 also, and a couple of OMAP4 checks in > > the smartreflex framework. > > > > The change in sr_device.c where new logic has to be introduced > > for reading the efuse registers are due to two reasons. > > a. Currently in mainline OMAP4 control base offset is actually > > from the mux/padconf module start. Hence a omap_ctrl_read will > > not read from the correct offset for the efuse registers. > > This is currently being fixed through modfications in the > > control layer but till that is finalised, we will have to do > > a ioremap of the general control module base and do a > > __raw_read to retrieve the efuse values. > > Is this the series posted by Santosh? > > [PATCH 0/4] omap4: Control module series > Yep. This series should address the SR control module issue
Regards, Santosh -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
