[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5C+gwVocek-6mvReyTbf4ZKAs2xDRmsT+pLqAQf1vVSCg@mail.gmail.com>
Date: Tue, 9 Dec 2014 19:40:40 -0200
From: Fabio Estevam <festevam@...il.com>
To: Mark Brown <broonie@...nel.org>
Cc: anthony.olech.opensource@...semi.com,
support.opensource@...semi.com,
linux-kernel <linux-kernel@...r.kernel.org>,
Olof Johansson <olof@...om.net>
Subject: Re: da9052-regulator fails to probe in linux-next
On Tue, Dec 9, 2014 at 7:37 PM, Mark Brown <broonie@...nel.org> wrote:
> On Tue, Dec 09, 2014 at 07:34:09PM -0200, Fabio Estevam wrote:
>
>> Yes, so here is a cleaner one:
>> http://arm-soc.lixom.net/bootlogs/next/next-20141104/wandboard-arm-imx_v6_v7_defconfig.html
>
>> The anatop regulators is drivers/regulator/pfuze100-regulator.c and
>> the dt description is at:
>> arch/arm/boot/dts/imx6qdl.dtsi
>
> Still not seeing any references to either pfuze100 or vdd (other than
> the external audio CODEC)...
Exactly, that's the bug :-)
If we compare it against next-20141031:
http://arm-soc.lixom.net/bootlogs/next/next-20141031/wandboard-arm-imx_v6_v7_defconfig.html
We get:
[ 0.052239] CPU identified as i.MX6Q, silicon rev 1.2
[ 0.072014] vdd1p1: 800 <--> 1375 mV at 1100 mV
[ 0.073027] vdd3p0: 2800 <--> 3150 mV at 3000 mV
[ 0.073933] vdd2p5: 2000 <--> 2750 mV at 2400 mV
[ 0.074888] vddarm: 725 <--> 1450 mV at 1150 mV
[ 0.075935] vddpu: 725 <--> 1450 mV at 1150 mV
[ 0.076897] vddsoc: 725 <--> 1450 mV at 1200 mV
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists