Quoting Peter De Schrijver (2013-04-02 02:34:26) > On Thu, Mar 28, 2013 at 09:31:27PM +0100, Thierry Reding wrote: > > The tegra_periph_reset_assert() and tegra_periph_reset_deassert() > > functions can be used by drivers to reset peripherals. In order to allow > > such drivers to be built as modules, export the functions. > > > > Note that this restores the status quo as the functions were exported > > before the move to the drivers/clk tree. > > > > I guess we should move to the 'reset framework' at some point in the future? > Yes please do. Peripheral reset stuff should not lurk in the clock code. I kind of brought this point up back in June of 2012: http://article.gmane.org/gmane.linux.ports.tegra/5346/ Back then the discussion was around removing this export from your clock driver and putting common reset code in clk.h (which is a bad idea). Now that the reset framework exists this stuff really should be migrated out of the clock framework entirely. But as long as this patch is considered an incremental change then it's OK by me. Regards, Mike > Otherwise: > > Acked-By: Peter De Schrijver <pdeschrijver@xxxxxxxxxx> > > > Cheers, > > Peter. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
