From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-omap <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Tero Kristo <t-kristo@ti.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Joel Fernandes <joelf@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Jyri Sarha <jsarha@ti.com>
Subject: Re: OMAP 4430 SDP: rather sick with recent kernels
Date: Wed, 17 Dec 2014 09:34:47 -0800 [thread overview]
Message-ID: <20141217173446.GG2950@atomide.com> (raw)
In-Reply-To: <CAGo_u6oS_xyboNZcUsQ8LFrhFhkR6yvr8r_XBj3-yTmqZnqYGA@mail.gmail.com>
* Nishanth Menon <nm@ti.com> [141217 09:35]:
> On Wed, Dec 17, 2014 at 11:23 AM, Tony Lindgren <tony@atomide.com> wrote:
> >
> >> twl: not initialized
> >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660
> >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660
> >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660
> >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660
> >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660
> >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660
> >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1410000 Vs max 1316660
> >
> > This seems to be some twl related init order issue, I'll take a
> > look at this one.
> >
> >> omap2_set_init_voltage: unable to find boot up OPP for vdd_mpu
> >> omap2_set_init_voltage: unable to set vdd_mpu
> >> omap2_set_init_voltage: unable to find boot up OPP for vdd_core
> >> omap2_set_init_voltage: unable to set vdd_core
> >> omap2_set_init_voltage: unable to find boot up OPP for vdd_iva
> >> omap2_set_init_voltage: unable to set vdd_iva
> >
> > I believe Nishanth has some plans for these?
>
>
> Not in the near future. looks like converting VC/VP into regulator and
> fit inside DT world has gone no where..
Looks like also the "twl: not initialized" error is caused by this:
omap2_common_pm_late_init
omap_voltage_late_init
omap_vc_init_channel
omap_vc_calc_vsel
twl6030_uv_to_vsel
twl_i2c_read
twl_get_regmap
Can't we fix it with pdata-quirks.c as this error is now showing up
on at least omap3 and 4?
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP 4430 SDP: rather sick with recent kernels
Date: Wed, 17 Dec 2014 09:34:47 -0800 [thread overview]
Message-ID: <20141217173446.GG2950@atomide.com> (raw)
In-Reply-To: <CAGo_u6oS_xyboNZcUsQ8LFrhFhkR6yvr8r_XBj3-yTmqZnqYGA@mail.gmail.com>
* Nishanth Menon <nm@ti.com> [141217 09:35]:
> On Wed, Dec 17, 2014 at 11:23 AM, Tony Lindgren <tony@atomide.com> wrote:
> >
> >> twl: not initialized
> >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660
> >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660
> >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660
> >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660
> >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660
> >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660
> >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1410000 Vs max 1316660
> >
> > This seems to be some twl related init order issue, I'll take a
> > look at this one.
> >
> >> omap2_set_init_voltage: unable to find boot up OPP for vdd_mpu
> >> omap2_set_init_voltage: unable to set vdd_mpu
> >> omap2_set_init_voltage: unable to find boot up OPP for vdd_core
> >> omap2_set_init_voltage: unable to set vdd_core
> >> omap2_set_init_voltage: unable to find boot up OPP for vdd_iva
> >> omap2_set_init_voltage: unable to set vdd_iva
> >
> > I believe Nishanth has some plans for these?
>
>
> Not in the near future. looks like converting VC/VP into regulator and
> fit inside DT world has gone no where..
Looks like also the "twl: not initialized" error is caused by this:
omap2_common_pm_late_init
omap_voltage_late_init
omap_vc_init_channel
omap_vc_calc_vsel
twl6030_uv_to_vsel
twl_i2c_read
twl_get_regmap
Can't we fix it with pdata-quirks.c as this error is now showing up
on at least omap3 and 4?
Regards,
Tony
next prev parent reply other threads:[~2014-12-17 17:37 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 9:52 OMAP 4430 SDP: rather sick with recent kernels Russell King - ARM Linux
2014-12-17 9:52 ` Russell King - ARM Linux
2014-12-17 17:23 ` Tony Lindgren
2014-12-17 17:23 ` Tony Lindgren
2014-12-17 17:33 ` Nishanth Menon
2014-12-17 17:33 ` Nishanth Menon
2014-12-17 17:34 ` Tony Lindgren [this message]
2014-12-17 17:34 ` Tony Lindgren
2014-12-17 18:51 ` Russell King - ARM Linux
2014-12-17 18:51 ` Russell King - ARM Linux
2014-12-17 19:09 ` Tony Lindgren
2014-12-17 19:09 ` Tony Lindgren
2014-12-17 20:44 ` Tony Lindgren
2014-12-17 20:44 ` Tony Lindgren
2014-12-17 21:08 ` Jyri Sarha
2014-12-17 21:08 ` Jyri Sarha
2014-12-18 10:16 ` Russell King - ARM Linux
2014-12-18 10:16 ` Russell King - ARM Linux
2014-12-18 11:48 ` Peter Rosin
2014-12-18 11:48 ` Peter Rosin
2014-12-18 13:12 ` Jyri Sarha
2014-12-18 13:12 ` Jyri Sarha
2014-12-18 11:49 ` Mark Brown
2014-12-18 11:49 ` Mark Brown
2014-12-31 14:00 ` Peter Ujfalusi
2014-12-31 14:00 ` Peter Ujfalusi
2014-12-31 18:52 ` Mark Brown
2014-12-31 18:52 ` Mark Brown
2014-12-18 16:41 ` Tony Lindgren
2014-12-18 16:41 ` Tony Lindgren
2014-12-31 12:59 ` Peter Ujfalusi
2014-12-31 12:59 ` Peter Ujfalusi
2015-01-14 17:51 ` Russell King - ARM Linux
2015-01-14 17:51 ` Russell King - ARM Linux
2015-01-14 19:09 ` Tony Lindgren
2015-01-14 19:09 ` Tony Lindgren
2015-01-14 22:27 ` Tony Lindgren
2015-01-14 22:27 ` Tony Lindgren
2015-01-14 23:10 ` Russell King - ARM Linux
2015-01-14 23:10 ` Russell King - ARM Linux
2015-01-15 10:48 ` Russell King - ARM Linux
2015-01-15 10:48 ` Russell King - ARM Linux
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=20141217173446.GG2950@atomide.com \
--to=tony@atomide.com \
--cc=joelf@ti.com \
--cc=jsarha@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nm@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=t-kristo@ti.com \
--cc=tomi.valkeinen@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.