public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: sameo@linux.intel.com, patches@opensource.wolfsonmicro.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] mfd: arizona: Don't use devres for DCVDD
Date: Tue, 17 Jun 2014 16:17:56 +0100	[thread overview]
Message-ID: <20140617151756.GF26741@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20140617143610.GD29841@lee--X1>

On Tue, Jun 17, 2014 at 03:36:10PM +0100, Lee Jones wrote:
> On Mon, 02 Jun 2014, Charles Keepax wrote:
> 
> > Currently the Arizona core uses a devm_regulator_get against its own
> > device node to obtain DCVDD. The Arizona core is an MFD device and DCVDD
> > is usually supplied by a child node (arizona-ldo1) of the core. As
> > devres destruction for the MFD device will run after all its children
> > have been destroyed, the regulator will be destroyed before devres
> > calls regulator_put. This causes a warning from both the destruction of
> > the child node, as the regulator is still open, and from the put of the
> > regulator as the regulator device has already been destroyed.
> > 
> > This patch handles the regulator get and put without devres to avoid
> > this issue.
> > 
> > Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> > ---
> >  drivers/mfd/arizona-core.c |    9 ++++++---
> >  1 files changed, 6 insertions(+), 3 deletions(-)
> 
> For the fear of someone coming along and undoing this work, can you
> write a nice succinct comment above regulator_get() that describes why
> you're not using managed resources as a subsequent patch please?
> 
> Patch applied though.

Good point I should have thought to do that myself, I will get a
patch out for this shortly.

Thanks,
Charles

  reply	other threads:[~2014-06-17 15:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-02  8:50 [PATCH 0/5] Arizona clean up driver removal and error paths Charles Keepax
2014-06-02  8:50 ` [PATCH 1/5] mfd: arizona: Disable PM runtime at start of driver removal Charles Keepax
2014-06-17 14:33   ` Lee Jones
2014-06-02  8:50 ` [PATCH 2/5] mfd: arizona: Disable DCVDD before we destroy the MFD Charles Keepax
2014-06-17 14:33   ` Lee Jones
2014-06-02  8:50 ` [PATCH 3/5] mfd: arizona: Don't use devres for DCVDD Charles Keepax
2014-06-17 14:36   ` Lee Jones
2014-06-17 15:17     ` Charles Keepax [this message]
2014-06-02  8:50 ` [PATCH 4/5] mfd: arizona: Use num_core_supplies in arizona_dev_exit Charles Keepax
2014-06-17 14:36   ` Lee Jones
2014-06-02  8:50 ` [PATCH 5/5] mfd: arizona: Lower ARIZONA_MAX_CORE_SUPPLIES to 2 Charles Keepax
2014-06-17 14:36   ` Lee Jones

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=20140617151756.GF26741@opensource.wolfsonmicro.com \
    --to=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