mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Tim Bird <tim.bird@sonymobile.com>
Cc: lgirdwood@gmail.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Bjorn Andersson <Bjorn.Andersson@sonymobile.com>
Subject: Re: [PATCH] regulator: Support different config and dev of_nodes in regulator_register
Date: Thu, 5 Feb 2015 01:59:45 +0000	[thread overview]
Message-ID: <20150205015945.GQ21293@sirena.org.uk> (raw)
In-Reply-To: <54D2A91D.5090700@sonymobile.com>

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

On Wed, Feb 04, 2015 at 03:19:57PM -0800, Tim Bird wrote:

> Support calling regulator_register with a dev node and a config node
> with different of_nodes.  This is useful when a single driver
> wishes to register multiple child regulators.

> Without this you get silent failures allocating a supply
> for a regulator which is registered using the device node of the
> regulator's DT parent (but it's own DT node).

This is explicitly not supported; such bindings are invariably attempts
to encode the Linux MFD structure into the device tree (which isn't a
wonderful idea as the way we split things into subsystems can and does
change) or...

> charger@1000 {
>       compatible = "qcom,pm8941-charger";
>       reg = <0x1000 0x700>;
>       ....
>       chg_otg {
>           regulator_name = "chg_otg";
>           otg-supply = <&pm8941_mvs1>;
>           ...
>       }
> }

...this which just looks like the supply has been placed in the wrong
place, it should be in the parent node.  Supplies are always defined at
the package level, that way we can consistently define the bindings for
supplies for a device without having to completely support it and we
don't have to bind the same supply multiple times.  It should really be
possible to wire up the supplies based only on the schematics.

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

  reply	other threads:[~2015-02-05  1:59 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 [this message]
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
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=20150205015945.GQ21293@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Bjorn.Andersson@sonymobile.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim.bird@sonymobile.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

Powered by JetHome