public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Liam Girdwood <lgirdwood@gmail.com>,
	Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: [PATCH] regulator: Lookup unresolved parent supplies before regulators cleanup
Date: Mon, 21 Mar 2016 09:44:55 -0300	[thread overview]
Message-ID: <56EFECC7.9030709@osg.samsung.com> (raw)
In-Reply-To: <20160321123752.GR2566@sirena.org.uk>

Hello Mark,

On 03/21/2016 09:37 AM, Mark Brown wrote:
> On Mon, Mar 21, 2016 at 09:13:55AM -0300, Javier Martinez Canillas wrote:
>> On 03/21/2016 08:11 AM, Mark Brown wrote:
>>> On Sun, Mar 20, 2016 at 11:39:46PM -0300, Javier Martinez Canillas wrote:
> 
>>>> This patch makes the unresolved parent supplies to be looked up before the
>>>> regulators late cleanup, so those with a child marked as always on will be
>>>> enabled regardless if a driver attempted to get the child regulator or not.
> 
>>> This doesn't make much sense to me as a fix - it feels like we're doing
>>> a fragile hack.  Surely it's better to do this as we register the
>>> devices, that way we're also protected against any similar issues with
> 
>> Sorry, not sure if I understood correctly. You mean to do it when the
>> drivers register the regulators, so at regulator_register() ?
> 
>> That's basically what was done before Bjorn's patch but that doesn't
>> handle the case of out of order registration when having circular
>> dependencies between regulators.
> 
> We used to look for the parent at registration time, we didn't look for
> the children.  What you're trying to do here is look for the children;
> we can do that at registration time.
>

Oh, now I understand what you meant. I thought you said to lookup the
parents at registration time, not the childrens. Great, I'll take a
look and give a try to your suggestion.

Thanks a lot for your help.

Best regards,
-- 
Javier Martinez Canillas
Open Source Group
Samsung Research America

      reply	other threads:[~2016-03-21 12:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21  2:39 [PATCH] regulator: Lookup unresolved parent supplies before regulators cleanup Javier Martinez Canillas
2016-03-21 11:11 ` Mark Brown
2016-03-21 12:13   ` Javier Martinez Canillas
2016-03-21 12:25     ` Javier Martinez Canillas
2016-03-21 12:37     ` Mark Brown
2016-03-21 12:44       ` Javier Martinez Canillas [this message]

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=56EFECC7.9030709@osg.samsung.com \
    --to=javier@osg.samsung.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.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