linux-kernel - Re: [PATCH] PCAP regulator driver (for 2.6.32).

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: <20090625233723.GA13150@sirena.org.uk>
Date:	Fri, 26 Jun 2009 00:37:24 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Daniel Ribeiro <drwyrm@...il.com>
Cc:	Liam Girdwood <lrg@...mlogic.co.uk>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	openezx-devel <openezx-devel@...ts.openezx.org>,
	Samuel Ortiz <sameo@...ux.intel.com>
Subject: Re: [PATCH] PCAP regulator driver (for 2.6.32).

On Thu, Jun 25, 2009 at 05:29:53PM -0300, Daniel Ribeiro wrote:

> +	/*
> +	 * The regulator framework doesn't like regulators which default
> +	 * to ON at boot time, so we just disable it here (when it is safe).
> +	 */
> +	if (pdev->id == VAUX2 || pdev->id == VAUX3)
> +		pcap_regulator_disable(rdev);

No need to do this - the regulator framework is perfectly happy with
regulators that are enabled at boot time and turning regulators that are
actively being used off is likely to cause issues.  Regulator drivers
should just leave everything as they find it and leave it up to the core
and machine drivers to make any changes.

Other than that this looks good; I'm assuming the PCAP core has a
sensible way of getting the platform data to the devices.
--
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/