From: Roger Quadros <ext-roger.quadros@nokia.com>
To: "ext Nayak, Rajendra" <rnayak@ti.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 00/10] OMAP3: SR: Fixes in Smartreflex driver
Date: Tue, 28 Apr 2009 11:32:03 +0300 [thread overview]
Message-ID: <49F6BF03.8060504@nokia.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB03051F8BEC@dbde02.ent.ti.com>
ext Nayak, Rajendra wrote:
>
>
>> -----Original Message-----
>> From: Kevin Hilman [mailto:khilman@deeprootsystems.com]
>> Sent: Saturday, April 25, 2009 4:21 AM
>> To: Roger Quadros
>> Cc: Nayak, Rajendra; linux-omap
>> Subject: Re: [PATCH 00/10] OMAP3: SR: Fixes in Smartreflex driver
>>
>> Roger Quadros <ext-roger.quadros@nokia.com> writes:
>>
>>> ext Kevin Hilman wrote:
>> [...]
>>>> Rajendra,
>>>>
>>>> This series seems to boot on SDP and Beagle but I recetly tried on
>>>> RX51 and it hangs in omap3_sr_init().
>>>>
>>>> Using Lauterbach, I tracked it to hang in sr_configure_vp() at this
>>>> PRM write to the PRM_VP1_VLIMITTO register:
>>>>
>>>> prm_write_mod_reg(PRM_VP1_VLIMITTO_VDDMAX |
>>>> PRM_VP1_VLIMITTO_VDDMIN |
>>>> PRM_VP1_VLIMITTO_TIMEOUT,
>>>> OMAP3430_GR_MOD,
>>>> OMAP3_PRM_VP1_VLIMITTO_OFFSET);
>>>>
>>>>
>>>> Should these min/max/timeout values be board specific?
>>>>
>> [...]
>>
>>> It runs on rx51 if we set CONFIG_OMAP_PM_SRF instead of
>> CONFIG_OMAP_PM_NOOP.
>>> Should Smartreflex option be dependent or independent of the
>>> CONFIG_OMAP_PM_??? setting?
>>>
>> I see the same thing on SDP as well as RX51.
>>
>> It looks like the new SR code assumes a range of OPPs, but when
>> OMAP_PM_NONE is enabled, the omap_pm_vddX_get_opp() calls always
>> return zero.
>>
>> In the mpu_opps array, the first entry is all zeros, resulting
>> in a zero VSEL which is then used to (re)program the VP.
>>
>> The SR code should probably be a bit smarter about checking for valid
>> values.
>>
>
> Kevin,
>
> I'll send in a patch to fix that.
>
> thanks,
> Rajendra
>
>>
>>
>>
I think the the X_get_opp() and X_get_freq() calls should be returning
sane values irrespective of PM layer (i.e. OMAP_PM_NOOP or OMAP_PM_NONE).
I have a patchset which does this with a little help from resource.c to get
the current OPP/frequency.
This fixes boot on RX51 for both PM_NOOP and PM_NONE with SMARTREFLEX enabled.
I just want to know if this is the right way to do. I think it would be because
Smartreflex or any other future driver will not have to worry about which PM
layer is selected.
I will send my patchset as an RFC.
regards,
-roger
next prev parent reply other threads:[~2009-04-28 8:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 12:55 [PATCH 00/10] OMAP3: SR: Fixes in Smartreflex driver Nayak, Rajendra
2009-04-17 13:35 ` Kevin Hilman
2009-04-22 20:04 ` Kevin Hilman
2009-04-24 6:46 ` Roger Quadros
2009-04-24 22:50 ` Kevin Hilman
2009-04-27 12:09 ` Nayak, Rajendra
2009-04-28 8:32 ` Roger Quadros [this message]
2009-04-25 7:41 ` Koen Kooi
2009-04-24 6:50 ` Nayak, Rajendra
2009-04-24 13:09 ` Kevin Hilman
2009-04-27 7:08 ` Jean Pihet
-- strict thread matches above, loose matches on Subject: below --
2009-04-03 16:08 Nayak, Rajendra
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=49F6BF03.8060504@nokia.com \
--to=ext-roger.quadros@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@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