mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Bjorn Andersson <bjorn.andersson@sonymobile.com>
Cc: "Bird, Tim" <Tim.Bird@sonymobile.com>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regulator: Support different config and dev of_nodes in regulator_register
Date: Fri, 6 Feb 2015 11:49:53 +0000	[thread overview]
Message-ID: <20150206114953.GT21293@sirena.org.uk> (raw)
In-Reply-To: <20150206005239.GD3218@sonymobile.com>

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

On Thu, Feb 05, 2015 at 04:52:40PM -0800, Bjorn Andersson wrote:
> On Thu 05 Feb 16:32 PST 2015, Mark Brown wrote:
> > On Thu, Feb 05, 2015 at 02:08:54PM -0800, Bjorn Andersson wrote:

> > > However this only works for the non-supply regulator properties - and
> > > this is where Tim's patch is trying to sort out.

> > No, this works completely fine for supply properties - to repeat what I
> > said in reply to the original patch the supply is a supply to the chip
> > not to an individual IP on the chip.

> It does make some sense to consider the vbus-supply being connected to
> the block, rather than directly to the vbus-switch. So it would work for
> Tim's use case.

Like I say if we do that then we don't have consistency in how we map a
schematic into a DT binding - you have to dig into the binding of each
device and figure out if the supply is viewed as being for blocks or for
the chip as a whole and we've got the potential for problems in the
binding if we figure out that a supply is actually used by other blocks
later on and don't want to break existing DTs.

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

  reply	other threads:[~2015-02-06 11:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 23:19 Tim Bird
2015-02-05  1:59 ` Mark Brown
2015-02-05 17:33   ` Tim Bird
2015-02-05 17:43     ` Mark Brown
2015-02-05 18:37       ` Tim Bird
2015-02-05 19:27         ` Mark Brown
2015-02-05 22:08           ` Bjorn Andersson
2015-02-06  0:32             ` Mark Brown
2015-02-06  0:52               ` Bjorn Andersson
2015-02-06 11:49                 ` Mark Brown [this message]
2015-02-06 19:56                   ` Tim Bird
2015-02-11 17:21                     ` Tim Bird
2015-02-12  2:32                       ` 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=20150206114953.GT21293@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Tim.Bird@sonymobile.com \
    --cc=bjorn.andersson@sonymobile.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®