Gulati, Shweta wrote, on 01/19/2011 02:10 PM:
>I cant see how disable_sr is usable, further as discussed in
http://marc.info/?l=linux->omap&m=129424774929498&w=2
<http://marc.info/?l=linux-omap&m=129424774929498&w=2> we decided to
introduce api *if needed*. does any one need it?
There might be some OMAP3xxx chips where for DVFS VMODE or VSEL
method is used, for those boards this disable API could be called
from Board File, to make sure the sequence of execution of
late_init_call of twl_init from omap2_common_pm_late_init does not
hamper clearing of this bit I would add a global variable to keep track
if Resetting is required or not, will submit V2 with changes.
Apologies, but a Dumb question:
late_initcall(omap2_common_pm_late_init)
board files(arch/arm/include/asm/mach/arch.h machine_desc) tend to have
the following hooks:
void (*fixup)(struct machine_desc *,
struct tag *, char **,
struct meminfo *);
void (*reserve)(void);/* reserve mem blocks */
void (*map_io)(void);/* IO mapping function */
void (*init_early)(void);
void (*init_irq)(void);
struct sys_timer *timer; /* system tick timer */
void (*init_machine (void);
void (*handle_irq)(struct pt_regs *);
So if i wanted to disable the SR setting, where should I do it?
--
Regards,
Nishanth Menon
PS: could you please fix your mailer when replying on l-o for
netetiquette reasons?
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
