From: Nishanth Menon <nm@ti.com>
To: "Gulati, Shweta" <shweta.gulati@ti.com>
Cc: linux-omap@vger.kernel.org, Thara Gopinath <thara@ti.com>,
Vishwanath Sripathy <vishwanath.bs@ti.com>,
"Premi, Sanjeev" <premi@ti.com>
Subject: Re: [PATCH] OMAP3: PM: Adding T2 enabling of smartreflex
Date: Wed, 19 Jan 2011 14:24:06 +0200 [thread overview]
Message-ID: <4D36D7E6.9060605@ti.com> (raw)
In-Reply-To: <AANLkTinRh+4eBf_Pu8DCAMyc+9D-bMVuV8kxwL5rOsXg@mail.gmail.com>
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?
next prev parent reply other threads:[~2011-01-19 12:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 9:07 [PATCH] OMAP3: PM: Adding T2 enabling of smartreflex shweta gulati
2011-01-19 9:24 ` Nishanth Menon
[not found] ` <AANLkTinRh+4eBf_Pu8DCAMyc+9D-bMVuV8kxwL5rOsXg@mail.gmail.com>
2011-01-19 12:24 ` Nishanth Menon [this message]
2011-01-20 13:14 ` Gulati, Shweta
2011-01-19 10:29 ` Premi, Sanjeev
-- strict thread matches above, loose matches on Subject: below --
2010-12-31 8:07 Thara Gopinath
2011-01-03 15:51 ` Nishanth Menon
2011-01-05 10:46 ` Gopinath, Thara
2011-01-05 13:37 ` Nishanth Menon
2011-01-04 22:48 ` Kevin Hilman
2011-01-05 10:51 ` Gopinath, Thara
2011-01-05 17:15 ` Kevin Hilman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D36D7E6.9060605@ti.com \
--to=nm@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=premi@ti.com \
--cc=shweta.gulati@ti.com \
--cc=thara@ti.com \
--cc=vishwanath.bs@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.