From: Nishanth Menon <nm@ti.com>
To: "Premi, Sanjeev" <premi@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [RFC 1/3] omap: voltage: Allow custom vp_init() implementation
Date: Thu, 24 Feb 2011 06:41:27 +0530 [thread overview]
Message-ID: <4D65B03F.304@ti.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB593024BE49223@dbde02.ent.ti.com>
Premi, Sanjeev wrote, on 02/24/2011 02:15 AM:
>> -----Original Message-----
>> From: Menon, Nishanth
>> Sent: Thursday, February 24, 2011 12:06 AM
>> To: Premi, Sanjeev
>> Cc: linux-omap@vger.kernel.org
>> Subject: Re: [RFC 1/3] omap: voltage: Allow custom vp_init()
>> implementation
>>
>> On Wed, Feb 23, 2011 at 23:28, Sanjeev Premi<premi@ti.com> wrote:
>>> Current implementation expects AVS to be available
>>> on the processor - by default. May not be true.
>>>
>>> This patch allows the vp_init() to be implemented
>>> per processor (or family) - same as vc_init().
>>
>> I believe Voltage Processor != Smart reflex AVS. Smart reflex AVS
>> module talks to VP talks to VC talks over I2C_SR to PMIC.
>> absence of AVS does'nt imply VP,VC dont exist or the potential to hook
>> up a PMIC over I2C_SR. no?
>
> [sp] But their role is limited to AVS only. If there is/was no AVS
> what would they be doing? Delta value written via SW on I2C would
> still get TWL working.
I dont think so. with SR, the prominence is higher, but normal voltage
setting, + additional FSMs hooked to VC, VP make it's existance
independent of AVS - mebbe this detail is just a technical nuance..
>
> And if you look into the omap_vdd_info you'd see what I meant.
data structure wise, yeah I think we'd have to evolve a bit, Pauls'
voltage.c cleanup series is one of the tiny steps we have to take.
do feel free to propose any improvements and we can discuss in the ML.
[..]
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2011-02-24 1:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 17:58 [RFC 0/3] Support TPS65023 with AM35xx Sanjeev Premi
2011-02-23 17:58 ` [RFC 1/3] omap: voltage: Allow custom vp_init() implementation Sanjeev Premi
2011-02-23 18:36 ` Menon, Nishanth
2011-02-23 20:45 ` Premi, Sanjeev
2011-02-24 1:11 ` Nishanth Menon [this message]
2011-02-23 17:58 ` [RFC 2/3] am35xx: voltage: Add basic initialization Sanjeev Premi
2011-02-23 18:40 ` Menon, Nishanth
2011-02-23 17:58 ` [RFC 3/3] am35xx: pm: Hook-up with TPS65023 Sanjeev Premi
2011-02-23 18:43 ` Menon, Nishanth
2011-02-24 13:20 ` Premi, Sanjeev
2011-02-24 10:04 ` Vishwanath Sripathy
2011-03-07 15:20 ` Premi, Sanjeev
2011-03-07 16:31 ` Vishwanath Sripathy
2011-03-08 12:26 ` Premi, Sanjeev
2011-03-08 12:45 ` Vishwanath Sripathy
2011-03-08 13:25 ` Premi, Sanjeev
2011-03-08 12:46 ` Nishanth Menon
2011-03-08 13:18 ` Premi, Sanjeev
2011-03-08 13:27 ` Menon, Nishanth
2011-03-08 13:37 ` Premi, Sanjeev
2011-03-08 16:08 ` 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=4D65B03F.304@ti.com \
--to=nm@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=premi@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.