From: Lee Jones <lee.jones@linaro.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: sameo@linux.intel.com, patches@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] mfd: arizona: Destroy regulators after the other MFD cells
Date: Tue, 17 Jun 2014 15:54:20 +0100 [thread overview]
Message-ID: <20140617145420.GH29841@lee--X1> (raw)
In-Reply-To: <1401699704-17902-2-git-send-email-ckeepax@opensource.wolfsonmicro.com>
On Mon, 02 Jun 2014, Charles Keepax wrote:
> Several of the cells depend on the regulators provided by the
> arizona-micsupp and arizona-ldo1 cells. As such use the new remove_level
> feature of the MFD core to ensure the regulators are destroyed after all
> the other cells.
>
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---
> drivers/mfd/arizona-core.c | 20 ++++++++++++++++----
> 1 files changed, 16 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/mfd/arizona-core.c b/drivers/mfd/arizona-core.c
> index 51c0110..76248bc 100644
> --- a/drivers/mfd/arizona-core.c
> +++ b/drivers/mfd/arizona-core.c
> @@ -570,7 +570,10 @@ static inline int arizona_of_get_core_pdata(struct arizona *arizona)
> #endif
>
> static const struct mfd_cell early_devs[] = {
> - { .name = "arizona-ldo1" },
> + {
> + .name = "arizona-ldo1",
> + .remove_level = 1,
> + },
> };
Not keen on this approach at all.
+1 for the new reverse-probe-helpers.
[...]
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-06-17 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 9:01 [PATCH 1/2] mfd: core: Add the option to order destruction of MFD cells 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 [this message]
2014-06-17 15:16 ` Charles Keepax
2014-06-02 21:01 ` [PATCH 1/2] mfd: core: Add the option to order destruction of " Mark Brown
2014-06-03 9:49 ` 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=20140617145420.GH29841@lee--X1 \
--to=lee.jones@linaro.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--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