linux-kernel - Re: [PATCH] mfd: tps6586x: add api to power off tps6586x

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: <20110823154056.GB26317@sirena.org.uk>
Date:	Tue, 23 Aug 2011 16:40:56 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Haojian Zhuang <haojian.zhuang@...il.com>
Cc:	Wei Ni <wni@...dia.com>, Samuel Ortiz <sameo@...ux.intel.com>,
	"mike@...pulab.co.il" <mike@...pulab.co.il>,
	Nitin Kumbhar <nkumbhar@...dia.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mfd: tps6586x: add api to power off tps6586x

On Mon, Aug 22, 2011 at 01:06:02PM +0800, Haojian Zhuang wrote:

> Maybe we can add a LDO mapping in regulator driver. Since power-off
> function is always
> customized in board file. We can disable this regulator while
> power_off() is called. So even
> multiple PMICs is installed in one system, we only handle the real one
> to shutdown the
> whole system.

Some (ST?) platform had an issue like that.  What they did IIRC is
define a regulator consumer driver which is hooked up as normal then had
that driver implemented a power_off() which used regulator_disable() to do
the honours.  Perhaps this could be made more generic somehow?  Though
it may have been part of their cpufreq driver or something - I can't
remember the detail right now.
--
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/