From: Mark Brown <broonie@opensource.wolfsonmicro.com> To: Benoit Cousson <b-cousson@ti.com> Cc: "AnilKumar, Chimata" <anilkumar@ti.com>, "a.zummo@towertech.it" <a.zummo@towertech.it>, "sameo@linux.intel.com" <sameo@linux.intel.com>, "tony@atomide.com" <tony@atomide.com>, "grant.likely@secretlab.ca" <grant.likely@secretlab.ca>, "rob.herring@calxeda.com" <rob.herring@calxeda.com>, "rtc-linux@googlegroups.com" <rtc-linux@googlegroups.com>, "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "devicetree-discuss@lists.ozlabs.org" <devicetree-discuss@lists.ozlabs.org>, Colin Foe-Parker <colin.foeparker@logicpd.com> Subject: Re: [PATCH 1/4] mfd: tps65217: Set PMIC to shutdowm on PWR_EN toggle Date: Wed, 14 Nov 2012 19:24:53 +0900 [thread overview] Message-ID: <20121114102452.GI7407@opensource.wolfsonmicro.com> (raw) In-Reply-To: <50A36DB1.3010706@ti.com> [-- Attachment #1: Type: text/plain, Size: 997 bytes --] On Wed, Nov 14, 2012 at 11:08:49AM +0100, Benoit Cousson wrote: > I was wondering that, because exposing a pin to control the whole PMIC > low power mode seems to be something that should be generic enough to be > handled by the regulator framework. Having something that's controlled by software is really not at all generic - suspending a PMIC from a GPIO is generally tied in very closely with the CPU power sequencing which means it's typically some combination of very hard coded things that we can't control or part of much wider control of sequencing. > In the current situation we do have a pwr_en pin that can be controlled > by a GPIO or whatever signal from the SoC. > That's very similar, at PMIC level, to the fixedregulator that allow a > GPIO binding to enable it. > Don't you think that should deserve a support in the fmwk? I'm not seeing a coherent description of a feature here - what exactly are you proposing that we do? When and how would this GPIO be set for example? [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 1/4] mfd: tps65217: Set PMIC to shutdowm on PWR_EN toggle Date: Wed, 14 Nov 2012 19:24:53 +0900 [thread overview] Message-ID: <20121114102452.GI7407@opensource.wolfsonmicro.com> (raw) In-Reply-To: <50A36DB1.3010706@ti.com> On Wed, Nov 14, 2012 at 11:08:49AM +0100, Benoit Cousson wrote: > I was wondering that, because exposing a pin to control the whole PMIC > low power mode seems to be something that should be generic enough to be > handled by the regulator framework. Having something that's controlled by software is really not at all generic - suspending a PMIC from a GPIO is generally tied in very closely with the CPU power sequencing which means it's typically some combination of very hard coded things that we can't control or part of much wider control of sequencing. > In the current situation we do have a pwr_en pin that can be controlled > by a GPIO or whatever signal from the SoC. > That's very similar, at PMIC level, to the fixedregulator that allow a > GPIO binding to enable it. > Don't you think that should deserve a support in the fmwk? I'm not seeing a coherent description of a feature here - what exactly are you proposing that we do? When and how would this GPIO be set for example? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20121114/c909c844/attachment.sig>
next prev parent reply other threads:[~2012-11-14 10:24 UTC|newest] Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-05 9:42 [PATCH 0/4] pm: Add power off control AnilKumar Ch 2012-11-05 9:42 ` AnilKumar Ch 2012-11-05 9:42 ` [PATCH 1/4] mfd: tps65217: Set PMIC to shutdowm on PWR_EN toggle AnilKumar Ch 2012-11-05 9:42 ` AnilKumar Ch [not found] ` <1352108549-9341-2-git-send-email-anilkumar-l0cyMroinI0@public.gmane.org> 2012-11-05 16:59 ` Benoit Cousson 2012-11-05 16:59 ` Benoit Cousson [not found] ` <5097F078.50701-l0cyMroinI0@public.gmane.org> 2012-11-06 5:13 ` AnilKumar, Chimata 2012-11-06 5:13 ` AnilKumar, Chimata 2012-11-14 2:23 ` Mark Brown 2012-11-14 2:23 ` Mark Brown [not found] ` <20121114022341.GM4415-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org> 2012-11-14 5:10 ` AnilKumar, Chimata 2012-11-14 5:10 ` AnilKumar, Chimata 2012-11-14 6:11 ` AnilKumar, Chimata 2012-11-14 6:11 ` AnilKumar, Chimata 2012-11-14 6:21 ` Mark Brown 2012-11-14 6:21 ` Mark Brown [not found] ` <20121114062117.GC7407-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org> 2012-11-14 6:49 ` AnilKumar, Chimata 2012-11-14 6:49 ` AnilKumar, Chimata 2012-11-14 7:00 ` Mark Brown 2012-11-14 7:00 ` Mark Brown [not found] ` <20121114070046.GE7407-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org> 2012-11-14 10:08 ` Benoit Cousson 2012-11-14 10:08 ` Benoit Cousson 2012-11-14 10:24 ` Mark Brown [this message] 2012-11-14 10:24 ` Mark Brown [not found] ` <20121114102452.GI7407-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org> 2012-11-16 6:16 ` AnilKumar, Chimata 2012-11-16 6:16 ` AnilKumar, Chimata 2012-11-05 9:42 ` [PATCH 2/4] rtc: OMAP: Add system pm_power_off to rtc driver AnilKumar Ch 2012-11-05 9:42 ` AnilKumar Ch [not found] ` <1352108549-9341-3-git-send-email-anilkumar-l0cyMroinI0@public.gmane.org> 2012-11-05 16:43 ` Benoit Cousson 2012-11-05 16:43 ` Benoit Cousson [not found] ` <5097ECAD.9010101-l0cyMroinI0@public.gmane.org> 2012-11-05 17:39 ` Colin FoeParker 2012-11-05 17:39 ` Colin FoeParker 2012-11-06 5:07 ` AnilKumar, Chimata 2012-11-06 5:07 ` AnilKumar, Chimata 2012-11-06 16:56 ` Benoit Cousson 2012-11-06 16:56 ` Benoit Cousson [not found] ` <50994156.4080305-l0cyMroinI0@public.gmane.org> 2012-11-12 9:47 ` AnilKumar, Chimata 2012-11-12 9:47 ` AnilKumar, Chimata 2012-11-14 5:01 ` AnilKumar, Chimata 2012-11-14 5:01 ` AnilKumar, Chimata 2012-11-14 5:21 ` Mark Brown 2012-11-14 5:21 ` Mark Brown 2012-11-14 5:50 ` AnilKumar, Chimata 2012-11-14 5:50 ` AnilKumar, Chimata 2012-11-14 6:00 ` Mark Brown 2012-11-14 6:00 ` Mark Brown 2012-11-06 5:45 ` Bedia, Vaibhav 2012-11-06 5:45 ` Bedia, Vaibhav [not found] ` <B5906170F1614E41A8A28DE3B8D121433EC04226-Er742YJ7I/eIQmiDNMet8wC/G2K4zDHf@public.gmane.org> 2012-11-12 9:47 ` AnilKumar, Chimata 2012-11-12 9:47 ` AnilKumar, Chimata 2012-11-16 6:13 ` AnilKumar, Chimata 2012-11-16 6:13 ` AnilKumar, Chimata 2012-11-16 10:47 ` AnilKumar, Chimata 2012-11-16 10:47 ` AnilKumar, Chimata 2012-11-05 9:42 ` [PATCH 3/4] ARM: dts: AM33XX: Set pmic-shutdown-controller for BeagleBone AnilKumar Ch 2012-11-05 9:42 ` AnilKumar Ch [not found] ` <1352108549-9341-1-git-send-email-anilkumar-l0cyMroinI0@public.gmane.org> 2012-11-05 9:42 ` [PATCH 4/4] ARM: dts: AM33XX: Enable system power off control in am335x-bone AnilKumar Ch 2012-11-05 9:42 ` AnilKumar Ch
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20121114102452.GI7407@opensource.wolfsonmicro.com \ --to=broonie@opensource.wolfsonmicro.com \ --cc=a.zummo@towertech.it \ --cc=anilkumar@ti.com \ --cc=b-cousson@ti.com \ --cc=colin.foeparker@logicpd.com \ --cc=devicetree-discuss@lists.ozlabs.org \ --cc=grant.likely@secretlab.ca \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=rob.herring@calxeda.com \ --cc=rtc-linux@googlegroups.com \ --cc=sameo@linux.intel.com \ --cc=tony@atomide.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.