devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Schocher <hs-ynQEQJNshbs@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Liam Girdwood <lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] regulator, dt: add dt support for tps6502x regulator
Date: Thu, 22 Oct 2015 06:51:49 +0200	[thread overview]
Message-ID: <56286B65.1010209@denx.de> (raw)
In-Reply-To: <20151021161732.GO32054-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>

Hello Mark,

Am 21.10.2015 um 18:17 schrieb Mark Brown:
> On Wed, Oct 21, 2015 at 02:52:51PM +0200, Heiko Schocher wrote:
>> Am 21.10.2015 um 14:19 schrieb Mark Brown:
>>> On Mon, Oct 19, 2015 at 08:27:13AM +0200, Heiko Schocher wrote:
>
>>> If this file is needed there is something broken, if this file is not
>>> needed then it is just noise since everything in it needs to be
>>> overridden by users anyway.  Either way please remove it.
>
>> Uh, I thought to do it like:
>
>> arch/arm/boot/dts/tps65217.dtsi
>
>> but, okay, removed.
>
> That too is broken and should be removed :(

Ok, I have a board which uses this regulator ... can you give me a hint,
how to remove it correctly?

I would do:

move from arch/arm/boot/dts/tps65217.dtsi into board dts

&tps {
+	compatible = "ti,tps65217";
	[...]

and the reg and "regulator-compatible" into the corresponding
nodes ...

                 dcdc1_reg: regulator@0 {
+                        reg = <0>;
+                        regulator-compatible = "dcdc1";

Thanks!

bye,
Heiko
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2015-10-22  4:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-19  7:14 [PATCH] regulator, dt: add dt support for tps6502x regulator kbuild test robot
     [not found] ` <1445236033-27747-1-git-send-email-hs-ynQEQJNshbs@public.gmane.org>
2015-10-19  7:14   ` [RFC PATCH] regulator, dt: tps6502x_parse_dt_data() can be static kbuild test robot
2015-10-21 12:19   ` [PATCH] regulator, dt: add dt support for tps6502x regulator Mark Brown
     [not found]     ` <20151021121925.GC8232-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-10-21 12:52       ` Heiko Schocher
2015-10-21 16:17         ` Mark Brown
     [not found]           ` <20151021161732.GO32054-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-10-22  4:51             ` Heiko Schocher [this message]
2015-10-22 12:28               ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2015-10-19  6:27 Heiko Schocher

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=56286B65.1010209@denx.de \
    --to=hs-ynqeqjnshbs@public.gmane.org \
    --cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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).