From: Jarkko Nikula <jhnikula@gmail.com>
To: "Gulati, Shweta" <shweta.gulati@ti.com>
Cc: linux-omap@vger.kernel.org, Thara Gopinath <thara@ti.com>,
Nishanth Menon <nm@ti.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V4] OMAP3: PM: Set/clear T2 bit for Smartreflex on TWL
Date: Wed, 16 Feb 2011 14:31:12 +0200 [thread overview]
Message-ID: <20110216143112.6f756a94.jhnikula@gmail.com> (raw)
In-Reply-To: <AANLkTiniGdh2_=eFjSaLsQ4VVG1Eh0F=0Tex-KNKspBf@mail.gmail.com>
On Wed, 16 Feb 2011 17:24:30 +0530
"Gulati, Shweta" <shweta.gulati@ti.com> wrote:
> > Note proof of concept patch only. I omitted the comments and don't do
> > explicit SR disable and I'd clean up the error paths in twl4030_power_init
> > a bit before this (e.g. printing error codes). Not sure either is the
> > twl4030-power.c right place for this or core.
> You missed commit log which says that "T2 bit is required to enable I2C_SR
> path of voltage control" it is not at all enabling SR, voltage scale
> APIs VPforceupdate/ VCbypass
> needs this path to be enabled.
> And calling APIs twl_i2c_read/write in driver codebase does n't ensure correct
> ordering of flag changes and twl_read/write.
Ah, yeah. I forgot to comment that I tried shortly also to run this
enable code from workqueue ~60 s after bootup and indeed SR didn't work
if those autocomp sysfs nodes were set before setting the TWL SR bit and
I believe same holds for voltage scaling too as you say.
What I'm thinking is there actually need for some higher level
control for these that quarantees the right order independently from
when each module are initialized.
--
Jarkko
next prev parent reply other threads:[~2011-02-16 12:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 7:58 [PATCH V4] OMAP3: PM: Set/clear T2 bit for Smartreflex on TWL Shweta Gulati
2011-02-15 15:16 ` Jarkko Nikula
2011-02-15 15:29 ` Jarkko Nikula
2011-02-16 5:52 ` Gulati, Shweta
2011-02-16 11:45 ` Jarkko Nikula
2011-02-16 11:54 ` Gulati, Shweta
2011-02-16 12:31 ` Jarkko Nikula [this message]
2011-02-16 12:47 ` Gulati, Shweta
2011-02-15 16:30 ` Vishwanath Sripathy
2011-02-16 5:44 ` Gulati, Shweta
2011-03-03 0:31 ` Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2011-02-04 5:47 Shweta Gulati
2011-02-12 10:40 ` Menon, Nishanth
2011-02-14 22:24 ` Kevin Hilman
2011-02-15 3:18 ` Nishanth Menon
2011-02-14 22:24 ` Kevin Hilman
2011-02-14 22:26 ` Kevin Hilman
2011-02-14 22:30 ` 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=20110216143112.6f756a94.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=shweta.gulati@ti.com \
--cc=thara@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox