Quoting Murali Karicheri (2012-11-05 07:10:52) > On 11/03/2012 08:07 AM, Sekhar Nori wrote: > > On 10/25/2012 9:41 PM, Murali Karicheri wrote: > >> This is the driver for the Power Sleep Controller (PSC) hardware > >> found on DM SoCs as well Keystone SoCs (c6x). This driver borrowed > >> code from arch/arm/mach-davinci/psc.c and implemented the driver > >> as per common clock provider API. The PSC module is responsible for > >> enabling/disabling the Power Domain and Clock domain for different IPs > >> present in the SoC. The driver is configured through the clock data > >> passed to the driver through struct clk_psc_data. > >> > >> Signed-off-by: Murali Karicheri <m-kariche...@ti.com> > >> --- > >> +/** > >> + * struct clk_psc - DaVinci PSC clock driver data > >> + * > >> + * @hw: clk_hw for the psc > >> + * @psc_data: Driver specific data > >> + */ > >> +struct clk_psc { > >> + struct clk_hw hw; > >> + struct clk_psc_data *psc_data; > >> + spinlock_t *lock; > > Unused member? I don't see this being used. > > OK. Will remove.
Those locks are only used for the case where a register might contain bits for several clocks. Thus RMW operations are protected. On OMAP this isn't necessary due to a very generous register layout (typically one 32-bit reg per module) controlling clocks. Seems tha tmaybe this is not needed for PSC module either? Regards, Mike > > > > Thanks, > > Sekhar > > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/