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]
Message-ID: <CAOMZO5BPvCcx_f09Khuw8MVxrR18fnv9e1xeuJ0c_8G22AR53g@mail.gmail.com>
Date:	Mon, 24 Feb 2014 14:23:50 -0300
From:	Fabio Estevam <festevam@...il.com>
To:	Mark Brown <broonie@...nel.org>
Cc:	Markus Pargmann <mpa@...gutronix.de>,
	Sascha Hauer <kernel@...gutronix.de>,
	Liam Girdwood <lgirdwood@...il.com>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 0/2] regulator: core: Fix ops->enable/disable usage

On Sun, Feb 23, 2014 at 2:12 AM, Mark Brown <broonie@...nel.org> wrote:
> On Thu, Feb 20, 2014 at 05:36:02PM +0100, Markus Pargmann wrote:
>> Hi,
>>
>> These two patches replace all ops->enable/disable by
>> _regulator_do_disable/enable function calls. These wrappers also handle gpio
>> regulators.
>
> Applied both, thanks.

With these two patches applied I get the following error on
mx6qsabresd running today's linux-next:

vdd1p1: failed to enable
anatop_regulator regulator-1p1.2: failed to register vdd1p1
anatop_regulator: probe of regulator-1p1.2 failed with error -22
vdd3p0: failed to enable
anatop_regulator regulator-3p0.3: failed to register vdd3p0
anatop_regulator: probe of regulator-3p0.3 failed with error -22
vdd2p5: failed to enable
anatop_regulator regulator-2p5.4: failed to register vdd2p5
anatop_regulator: probe of regulator-2p5.4 failed with error -22
vddarm: 725 <--> 1450 mV at 1100 mV
vddpu: 725 <--> 1450 mV at 1100 mV
vddsoc: 725 <--> 1450 mV at 1175 mV
....

pfuze100-regulator 1-0008: Full layer: 1, Metal layer: 0
pfuze100-regulator 1-0008: FAB: 0, FIN: 0
SW1AB: failed to enable
pfuze100-regulator 1-0008: register regulatorSW1AB failed
pfuze100-regulator: probe of 1-0008 failed with error -22


Reverting these two patches the regulators probe successfully.

Any ideas?

Regards,

Fabio Estevam
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ