linux-kernel - Re: [PATCH] regulator: core: allow enabling without enable op

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] [day] [month] [year] [list]

Message-ID: <CAK9yfHx-gMzJb=OgaMXQ3esKx1n0fFA-+nNMcLrF5e6ajd+n7w@mail.gmail.com>
Date:	Tue, 25 Feb 2014 15:13:59 +0530
From:	Sachin Kamat <sachin.kamat@...aro.org>
To:	Alexandre Courbot <acourbot@...dia.com>
Cc:	Mark Brown <broonie@...aro.org>,
	Liam Girdwood <lgirdwood@...il.com>,
	Markus Pargmann <mpa@...gutronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Alexandre Courbot <gnurou@...il.com>
Subject: Re: [PATCH] regulator: core: allow enabling without enable op

On 25 February 2014 12:27, Alexandre Courbot <acourbot@...dia.com> wrote:
> Commit 14c32a3ce6676265d7a27ea64a4d406e6dbad111 replaced direct uses of
> ops->enable by calls to _regulator_do_enable. This prevents a fixed
> regulators without a GPIO from being probed, since the former code
> checked the existence of ops->enable and continued if it did not exist,
> while _regulator_do_enable return -EINVAL in that case.
>
> This patch fixes this by allowing _regulator_do_enable to go through
> without error if ops->enable is not defined, similarly to what
> _regulator_do_disable already does.
>
> Signed-off-by: Alexandre Courbot <acourbot@...dia.com>

This patch fixes the fixed regulator registration failure on Exynos5420 board.

Tested-by: Sachin Kamat <sachin.kamat@...aro.org>

-- 
With warm regards,
Sachin
--
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/