devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: Wei Ni <wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH RESEND] ARM: tegra: set regulator full constraints
Date: Wed, 13 Nov 2013 20:49:23 +0000	[thread overview]
Message-ID: <20131113204923.GG878@sirena.org.uk> (raw)
In-Reply-To: <5283DD52.5050903-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>

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

On Wed, Nov 13, 2013 at 01:13:06PM -0700, Stephen Warren wrote:
> On 11/13/2013 12:07 PM, Mark Brown wrote:

> > This isn't really regulator specific - it's something that applies
> > in general to things implementing deferred probing - so we ought to
> > have a generic "we know if devices can appear later or not" flag
> > that subsystems can check.

> I guess I misunderstand then, since given that modules exist, wouldn't
> that flag always be true?

No, with DT you can say that if there is no DT binding configuring a
given thing (clock, regulator, GPIO or whatever) then no amount of
module loading will ever cause it to appear - this is what the flag in
question controls.

> IIUC, the issue being discussed here isn't about deferred probe at
> all. You always must defer probe if an object is specified as existing
> yet the provider isn't available yet. The issue here is when a
> regulator isn't specified as existing, yet something asks for that
> regulator, should the regulator subsystem automatically provide a
> dummy regulator instead, rather than erroring out.

No, it's a deferred probing thing - one of the effects here is that
we're choosing between deferring waiting for the resource we know is
bound to appear and substituting a dummy for something we know exists
physically and we know can never be provided by software.

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

  parent reply	other threads:[~2013-11-13 20:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1383203126-3243-1-git-send-email-wni@nvidia.com>
     [not found] ` <20131031162029.GF2493@sirena.org.uk>
     [not found]   ` <527737C5.5080901@nvidia.com>
     [not found]     ` <20131104161828.GK2493@sirena.org.uk>
     [not found]       ` <5278B4CB.9050305@nvidia.com>
     [not found]         ` <20131106085100.GB11602@sirena.org.uk>
     [not found]           ` <20131106085100.GB11602-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-06 10:39             ` [PATCH RESEND] ARM: tegra: set regulator full constraints Wei Ni
     [not found]               ` <527A1C47.6050405-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-11-06 11:01                 ` Mark Brown
     [not found]                   ` <20131106110154.GG11602-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-12  5:52                     ` Wei Ni
     [not found]                       ` <5281C228.3000404-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-11-12 18:20                         ` Stephen Warren
     [not found]                           ` <5282717C.3050502-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-11-13 10:12                             ` Wei Ni
2013-11-13 12:23                             ` Mark Brown
     [not found]                               ` <20131113122329.GC878-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-13 17:29                                 ` Stephen Warren
     [not found]                                   ` <5283B6E3.9070206-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-11-13 19:07                                     ` Mark Brown
     [not found]                                       ` <20131113190745.GD878-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-13 20:13                                         ` Stephen Warren
     [not found]                                           ` <5283DD52.5050903-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-11-13 20:49                                             ` Mark Brown [this message]
     [not found]                                               ` <20131113204923.GG878-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-13 21:59                                                 ` Stephen Warren
     [not found]                                                   ` <5283F625.403-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-11-13 22:29                                                     ` Mark Brown
     [not found]                                                       ` <20131113222953.GA26614-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-13 23:41                                                         ` Stephen Warren
     [not found]                                                           ` <52840E23.5080105-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-11-14 11:36                                                             ` 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=20131113204923.GG878@sirena.org.uk \
    --to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
    --cc=wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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).