devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
	systemd-devel@lists.freedesktop.org,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	devicetree <devicetree@vger.kernel.org>
Subject: Re: [systemd-devel] Making udev emit a signal when it is done loading modules
Date: Sat, 17 Jan 2015 14:12:48 +0000	[thread overview]
Message-ID: <20150117141248.GD6414@sirena.org.uk> (raw)
In-Reply-To: <20150117135630.GA25585@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 993 bytes --]

On Sat, Jan 17, 2015 at 05:56:30AM -0800, Greg KH wrote:
> On Sat, Jan 17, 2015 at 09:44:00AM +0100, Hans de Goede wrote:

> > If however the ahci_platform driver is a module, then as soon as
> > the kernel is ready to start init, unused regulators are turned off
> > and the disk looses its power while spinning and ends up doing an
> > emergency heads park.

> What turns off the power in this situation?  The kernel?  Or userspace?
> Don't you have control of this?

The kernel turns off the power in late_initcall because it noticed that
nothing is using the regulator, it does this because otherwise we're
just left with whatever the bootloader had which will may well be
wasting power on unused rails due to inflexible PMICs (we do similar
things for other subsystems like clocks).  This works fine for most use
cases since in embedded systems anything critical tends to end up built
in.

There is configurability to allow things to be flagged as always on so
they never get turned off.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-01-17 14:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-17  8:44 Making udev emit a signal when it is done loading modules Hans de Goede
2015-01-17 13:56 ` Greg KH
2015-01-17 14:12   ` Mark Brown [this message]
2015-01-17 14:52   ` Hans de Goede
     [not found]   ` <20150117135630.GA25585-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-01-17 15:23     ` [systemd-devel] " jonsmirl-Re5JQEeQqe8AvxtiuMwx3w
2015-01-17 16:03 ` David Herrmann
2015-01-17 16:03 ` Zbigniew Jędrzejewski-Szmek
2015-01-17 16:45   ` [systemd-devel] " Kay Sievers
2015-01-28  1:38   ` Lennart Poettering
2015-02-11  5:28     ` [systemd-devel] " Mark Brown

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=20150117141248.GD6414@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=greg@kroah.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=systemd-devel@lists.freedesktop.org \
    /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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).