linux-kernel - Re: da9052-regulator fails to probe in linux-next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 9 Dec 2014 21:47:37 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Fabio Estevam <festevam@...il.com>
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 09, 2014 at 07:40:40PM -0200, Fabio Estevam wrote:
> On Tue, Dec 9, 2014 at 7:37 PM, Mark Brown <broonie@...nel.org> wrote:

> > Still not seeing any references to either pfuze100 or vdd (other than
> > the external audio CODEC)...

> Exactly, that's the bug :-)

My point is that I'm not seeing anything complaining about those devices
or the supplies they offer so nothing there indicates to me that there's
any kind of problem.

> If we compare it against next-20141031:
> http://arm-soc.lixom.net/bootlogs/next/next-20141031/wandboard-arm-imx_v6_v7_defconfig.html

> [    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

Remember that these messages are now at debug level.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)