From: Mark Brown <broonie@kernel.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: lee.jones@linaro.org, sameo@linux.intel.com,
patches@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mfd: core: Add the option to order destruction of MFD cells
Date: Mon, 2 Jun 2014 22:01:17 +0100 [thread overview]
Message-ID: <20140602210117.GO31751@sirena.org.uk> (raw)
In-Reply-To: <1401699704-17902-1-git-send-email-ckeepax@opensource.wolfsonmicro.com>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
On Mon, Jun 02, 2014 at 10:01:43AM +0100, Charles Keepax wrote:
> Sometimes MFD children will have interdependancies. For example an MFD
> device might contain a regulator cell and another cell which requires
> that regulator to function. Probe deferral will ensure that these
> devices probe in the correct order, however currently nothing ensures
> they are destroyed in the correct order. As such it is possible for a
> cell to be destroyed whilst another cell still expects it to exist. For
> example the cell mentioned earlier would attempt to do a regulator_put
> as part of its own tear-down but the regulator may have already been
> destroyed.
Probe deferral is supposed to handle removal too, we're supposed to be
able to walk the device list in reverse order and everything just work.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-06-02 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 9:01 Charles Keepax
2014-06-02 9:01 ` [PATCH 2/2] mfd: arizona: Destroy regulators after the other " Charles Keepax
2014-06-17 14:54 ` Lee Jones
2014-06-17 15:16 ` Charles Keepax
2014-06-02 21:01 ` Mark Brown [this message]
2014-06-03 9:49 ` [PATCH 1/2] mfd: core: Add the option to order destruction of " Charles Keepax
2014-06-03 10:35 ` 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=20140602210117.GO31751@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.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: 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
all inboxes | Powered by JetHome®