linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: t-kristo@ti.com
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCHv8 2/5] omap3: voltage: fix channel configuration
Date: Mon, 12 Dec 2011 07:02:16 -0800	[thread overview]
Message-ID: <87d3btg7ev.fsf@ti.com> (raw)
In-Reply-To: <1323682464.31914.3.camel@sokoban> (Tero Kristo's message of "Mon, 12 Dec 2011 11:34:24 +0200")

Tero Kristo <t-kristo@ti.com> writes:

> On Fri, 2011-12-09 at 16:21 -0800, Kevin Hilman wrote:
>> Tero Kristo <t-kristo@ti.com> writes:
>> 
>> > OMAP3 uses the default settings for VDD1 channel, otherwise the settings will
>> > overlap with VDD2 and attempting to modify VDD1 voltage will actually change
>> > VDD2 voltage.
>> >
>> > Signed-off-by: Tero Kristo <t-kristo@ti.com>
>> > ---
>> >  arch/arm/mach-omap2/vc3xxx_data.c |    1 +
>> >  2 files changed, 5 insertions(+), 1 deletions(-)
>> >
>> > diff --git a/arch/arm/mach-omap2/vc3xxx_data.c b/arch/arm/mach-omap2/vc3xxx_data.c
>> > index cfe348e..0136ad5 100644
>> > --- a/arch/arm/mach-omap2/vc3xxx_data.c
>> > +++ b/arch/arm/mach-omap2/vc3xxx_data.c
>> > @@ -46,6 +46,7 @@ static struct omap_vc_common omap3_vc_common = {
>> >  };
>> >  
>> >  struct omap_vc_channel omap3_vc_mpu = {
>> > +	.flags = OMAP_VC_CHANNEL_DEFAULT,
>> >  	.common = &omap3_vc_common,
>> >  	.smps_sa_reg	 = OMAP3_PRM_VC_SMPS_SA_OFFSET,
>> >  	.smps_volra_reg	 = OMAP3_PRM_VC_SMPS_VOL_RA_OFFSET,
>> 
>> Looking more at the flow diagram you mentioned in the OMAP3 TRM, I don't
>> think this is right for OMAP3.
>> 
>> Setting the USE_DEFAULTS flags means that VDD1 will only ever be able to
>> use [slave address | voltage reg | command reg] zero.  While this is
>> quite likely in most scenarios, the HW doesn't limit this like it does
>> on OMAP4.
>> 
>> On OMAP3, it's very possible to configure VDD1 to use 
>> [slave address | voltage reg | command reg] one if you want (even though
>> I'm not sure why you would.)
>> 
>> In any case, my point is that setting the USE_DEFAULTS flag forces an
>> OMAP4 restriction onto OMAP3 which the hardware doesn't have.
>> 
>
> Well, the voltage control does not work at all if this is not done. I am
> not sure what is the root cause for this, as I don't have currently
> oscilloscope available so that I could take a look at the bus traffic.
> The voltage rail behavior is incorrect unless this change is in, this is
> easily seen by measuring the voltage levels and trying to change the
> voltages by sw.

Yeah, I understand why it's broken now and the question is only whether
to make the same "default channel" restriction exist for OMAP3 as exists
for OMAP4.  For now, I'm OK with this restriction, so this patch is
fine.

Kevin

  reply	other threads:[~2011-12-12 15:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-09 15:29 [PATCHv8 0/5] SMPS regulator driver Tero Kristo
2011-12-09 15:29 ` [PATCHv8 1/5] TEMP: OMAP3: beagle rev-c4: enable OPP6 Tero Kristo
2011-12-09 15:29 ` [PATCHv8 2/5] omap3: voltage: fix channel configuration Tero Kristo
2011-12-10  0:21   ` Kevin Hilman
2011-12-12  9:34     ` Tero Kristo
2011-12-12 15:02       ` Kevin Hilman [this message]
2011-12-09 15:29 ` [PATCHv8 3/5] omap3: add common twl configurations for vdd1 and vdd2 Tero Kristo
2011-12-09 15:29 ` [PATCHv8 4/5] twl4030: add support for external voltage get/set Tero Kristo
2011-12-19  8:33   ` Samuel Ortiz
2011-12-19  9:56     ` Girdwood, Liam
2011-12-20  0:31       ` Mark Brown
     [not found]         ` <87hb04wesx.fsf@ti.com>
2012-01-10  8:05           ` Tero Kristo
2012-01-10  1:11   ` Kevin Hilman
2012-01-10  3:30     ` Mark Brown
2012-01-10 15:19       ` Kevin Hilman
2012-01-10 19:10         ` Mark Brown
2012-02-14 12:47           ` Tero Kristo
2012-02-14 19:16             ` Kevin Hilman
2012-02-15  8:38               ` Tero Kristo
2011-12-09 15:29 ` [PATCHv8 5/5] omap3: twl: add external controllers for core voltage regulators Tero Kristo

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=87d3btg7ev.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=t-kristo@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;
as well as URLs for NNTP newsgroup(s).