linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Linux PM mailing list <linux-pm@vger.kernel.org>
Subject: Re: cpufreq-dt error: failed to init cpufreq table: -61
Date: Tue, 6 Oct 2015 11:10:52 -0500	[thread overview]
Message-ID: <87a8rw2d0z.fsf@saruman.tx.rr.com> (raw)
In-Reply-To: <87zizw2fyv.fsf@saruman.tx.rr.com>

[-- Attachment #1: Type: text/plain, Size: 1918 bytes --]

Felipe Balbi <balbi@ti.com> writes:

> Belisko Marek <marek.belisko@gmail.com> writes:
>
>> Hi,
>>
>> On Tue, Oct 6, 2015 at 4:03 PM, Belisko Marek <marek.belisko@gmail.com> wrote:
>>> Hi Felipe,
>>>
>>> On Tue, Oct 6, 2015 at 4:00 PM, Felipe Balbi <balbi@ti.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> Belisko Marek <marek.belisko@gmail.com> writes:
>>>>> Hi Tony,
>>>>>
>>>>> I'm using custom am33xx board where mpu voltage can be changed through
>>>>> gpio regulator on 4.1 (latest stable) kernel. I defined gpio-regulator
>>>>> node and also operating-points to DT. Gpio regulator seems to be
>>>>> working fine but during probing cpufreq-dt I get error:
>>>>> failed to init cpufreq table: -61
>>>>>
>>>>> I did small investigation and seem that dev_pm_opp_init_cpufreq_table
>>>>> fails at first condition dev_pm_opp_get_opp_count <= 0 and this is
>>>>> because opp_list is empty. So it seems that any opp for am33xx aren't
>>>>> defined if I'm getting it right. I did look to mach-omap2/opp3xxx_data
>>>>> but there is nothing am33xx specific. It is known problem or exist
>>>>> some patches around to fix that? Many thanks.
>>>>
>>>> OPP initialization is not in mainline yet, there are some out-of-tree
>>>> patches which TI has been working on. If you want to use them, have a
>>>> look at TI's vendor kernel at [1]
>>> Thanks for link. One thing which is still not puzzled before I use 3.9
>>> kernel and it was working fine
>>> it's stops working when bumped to 4.1.
>>
>> Sorry information was incorrect. On 3.9 kernel we did use tps, pmic
>> now we have only gpio regulator so this is the difference.
>
> okay, if it's only a regulator how can you set different voltages ?
                       ^^^^^^^^^
                       GPIO, rather


> Seems like you won't be able to do anything more than enable/disable a
> voltage rail.
>
> -- 
> balbi

-- 
balbi

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

  reply	other threads:[~2015-10-06 16:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06 13:25 cpufreq-dt error: failed to init cpufreq table: -61 Belisko Marek
2015-10-06 14:00 ` Felipe Balbi
2015-10-06 14:03   ` Belisko Marek
2015-10-06 14:16     ` Belisko Marek
2015-10-06 15:07       ` Felipe Balbi
2015-10-06 16:10         ` Felipe Balbi [this message]
2015-10-06 18:57         ` Belisko Marek

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=87a8rw2d0z.fsf@saruman.tx.rr.com \
    --to=balbi@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=marek.belisko@gmail.com \
    --cc=tony@atomide.com \
    --cc=viresh.kumar@linaro.org \
    /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).