devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Balaji T K <balajitk@ti.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"bcousson@baylibre.com" <bcousson@baylibre.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	"cjb@laptop.org" <cjb@laptop.org>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"tony@atomide.com" <tony@atomide.com>
Subject: Re: [PATCH v7 5/7] ARM: dts: add pbias dt node
Date: Fri, 10 Jan 2014 22:30:39 +0530	[thread overview]
Message-ID: <52D02737.6060609@ti.com> (raw)
In-Reply-To: <20140110113234.GA25741@e106331-lin.cambridge.arm.com>

On Friday 10 January 2014 05:02 PM, Mark Rutland wrote:
> On Wed, Jan 08, 2014 at 02:51:46PM +0000, Balaji T K wrote:
>> On Tuesday 07 January 2014 05:53 PM, Balaji T K wrote:
>>> On Tuesday 07 January 2014 04:27 PM, Mark Rutland wrote:
>>>> On Tue, Jan 07, 2014 at 10:18:15AM +0000, Balaji T K wrote:
>>>>> On Monday 06 January 2014 11:49 PM, Mark Rutland wrote:
>>>>>> On Fri, Dec 20, 2013 at 05:35:53PM +0000, Balaji T K wrote:
>>>>>>> Add pbias regulator node as a child of system control
>>>>>>> module - syscon.
>>>>>>>
>>>>>>> Signed-off-by: Balaji T K <balajitk@ti.com>
>>>>>>> ---
>>>>>>>     arch/arm/boot/dts/dra7.dtsi     |   18 ++++++++++++++++++
>>>>>>>     arch/arm/boot/dts/omap2430.dtsi |   18 ++++++++++++++++++
>>>>>>>     arch/arm/boot/dts/omap3.dtsi    |   18 ++++++++++++++++++
>>>>>>>     arch/arm/boot/dts/omap4.dtsi    |   18 ++++++++++++++++++
>>>>>>>     arch/arm/boot/dts/omap5.dtsi    |   18 ++++++++++++++++++
>>>>>>>     5 files changed, 90 insertions(+), 0 deletions(-)
>>>>>>>
>>>>>>> diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
>>>>>>> index d0df4c4..4e68df1 100644
>>>>>>> --- a/arch/arm/boot/dts/dra7.dtsi
>>>>>>> +++ b/arch/arm/boot/dts/dra7.dtsi
>>>>>>> @@ -110,6 +110,23 @@
>>>>>>>                 ti,hwmods = "counter_32k";
>>>>>>>             };
>>>>>>>
>>>>>>> +        dra7_ctrl_general: tisyscon@4a002e00 {
>>>>>>> +            compatible = "ti,control-syscon", "syscon", "simple-bus";
>>>>>>
>>>>>> Please, don't use simple-bus like that. The components below this node
>>>>>> depend on it. It is _NOT_ a simple bus. Make the ti,control-syscon
>>>>>> driver probe it's children.
>>>>>
>>>>> Hi Mark,
>>>>>
>>>>> Actually ti,control-syscon driver does not exist, so I can remove it,
>>>>> and simple-bus is needed for child creation.
>>>>
>>>> This still shows up as a syscon node, with a reg property, and syscon is
>>>> not an extension of simple-bus.
>>>>
>>>> There are properties in the parent node that children depend on, and
>>>> that makes me wary of describing it as a simple bus. I'd expect to be
>>>> able to move child nodes out of a simple-bus if ranges provided an
>>>> idmap, and I can't do that here.
>>>>
>>> Hi Mark,
>>>
>>> Not sure if I am understanding here, can you please add more info.
>
> A node's compatible string list describes the set of devices (or rather
> descriptions of devices) with which it is compatible. The list goes from
> most specific to least specific. The idea is that an OS reads through
> the list until it finds a string it knows how to handle, then treats the
> node as that.
>
> Ignoring "ti,control-syscon", the node has both "syscon" and
> "simple-bus". Given you expect the OS to recognise "syscon", you should
> _not_ expect it to also treat the node as "simple-bus". Doing so is an
> abuse of the property and current Linux implementation details.
>
> The "syscon" binding is not a more specific version of "simple-bus".
> They imply completely different things.
>
> Either make a ti,control-syscon driver that probes the child nodes, or
> move the child nodes out and give them a phandle to the
> dra7_ctrl_general node that they can parse. I'd prefer the latter as
> relies on fewer topology details, is as easy to implement as your
> current parent node parsing, and is easier to extend in future.
>

Thanks Mark,
phandle to syscon is fine for me.


  reply	other threads:[~2014-01-10 17:00 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20 17:35 [PATCH v7 0/7] mmc: omap_hsmmc: pbias dt and cleanup Balaji T K
2013-12-20 17:35 ` [PATCH v7 1/7] mmc: omap_hsmmc: use devm_regulator API Balaji T K
2013-12-20 18:38   ` Tony Lindgren
2013-12-20 17:35 ` [PATCH v7 2/7] mmc: omap_hsmmc: handle vcc and vcc_aux independently Balaji T K
2013-12-20 18:40   ` Tony Lindgren
2013-12-20 17:35 ` [PATCH v7 3/7] regulator: add pbias regulator support Balaji T K
2013-12-20 23:39   ` Tony Lindgren
2013-12-24 16:11     ` Balaji T K
2014-01-06 18:16   ` Mark Rutland
2014-01-07 10:09     ` Balaji T K
2013-12-20 17:35 ` [PATCH v7 4/7] mmc: omap_hsmmc: adapt hsmmc to use pbias regulator Balaji T K
2013-12-20 18:15   ` Michael Trimarchi
2013-12-23 13:42     ` Balaji T K
2013-12-20 17:35 ` [PATCH v7 5/7] ARM: dts: add pbias dt node Balaji T K
2013-12-21  0:32   ` Tony Lindgren
2014-01-06 18:19   ` Mark Rutland
2014-01-07 10:18     ` Balaji T K
2014-01-07 10:57       ` Mark Rutland
2014-01-07 12:23         ` Balaji T K
2014-01-08 14:51           ` Balaji T K
2014-01-10 11:32             ` Mark Rutland
2014-01-10 17:00               ` Balaji T K [this message]
2013-12-20 17:35 ` [PATCH v7 6/7] ARM: OMAP: enable SYSCON and REGULATOR_PBIAS in omap2plus_defconfig Balaji T K
2013-12-21  0:33   ` Tony Lindgren
2013-12-20 17:35 ` [PATCH v7 7/7] mmc: omap_hsmmc: remove pbias workaround Balaji T K
2013-12-21  0:33   ` Tony Lindgren
2014-01-09 14:50 ` [PATCH v8 0/7] mmc: omap_hsmmc: pbias dt and cleanup Balaji T K
2014-01-09 14:50   ` [PATCH v8 1/7] mmc: omap_hsmmc: use devm_regulator API Balaji T K
2014-01-09 15:18     ` Felipe Balbi
2014-01-10 15:55       ` Balaji T K
2014-01-10 15:58         ` Felipe Balbi
2014-01-09 14:50   ` [PATCH v8 2/7] mmc: omap_hsmmc: handle vcc and vcc_aux independently Balaji T K
2014-01-09 14:50   ` [PATCH v8 3/7] regulator: add pbias regulator support Balaji T K
2014-01-09 17:27     ` Mark Brown
2014-01-09 14:50   ` [PATCH v8 4/7] mmc: omap_hsmmc: adapt hsmmc to use pbias regulator Balaji T K
2014-01-09 14:51   ` [PATCH v8 5/7] ARM: dts: add pbias dt node Balaji T K
2014-01-09 14:51   ` [PATCH v8 6/7] ARM: OMAP: enable SYSCON and REGULATOR_PBIAS in omap2plus_defconfig Balaji T K
2014-01-09 14:51   ` [PATCH v8 7/7] mmc: omap_hsmmc: remove pbias workaround Balaji T K
2014-01-10 17:30   ` [PATCH v9 0/7] mmc: omap_hsmmc: pbias dt and cleanup Balaji T K
2014-01-10 17:30     ` [PATCH v9 1/7] mmc: omap_hsmmc: use devm_regulator API Balaji T K
2014-01-10 17:30     ` [PATCH v9 2/7] mmc: omap_hsmmc: handle vcc and vcc_aux independently Balaji T K
2014-01-10 17:30     ` [PATCH v9 3/7] regulator: add pbias regulator support Balaji T K
2014-01-10 17:30     ` [PATCH v9 4/7] mmc: omap_hsmmc: adapt hsmmc to use pbias regulator Balaji T K
2014-01-10 18:21       ` Michael Trimarchi
2014-01-13 13:29         ` Balaji T K
2014-01-10 17:30     ` [PATCH v9 5/7] ARM: dts: add pbias dt node Balaji T K
2014-01-10 17:30     ` [PATCH v9 6/7] ARM: OMAP: enable SYSCON and REGULATOR_PBIAS in omap2plus_defconfig Balaji T K
2014-01-10 17:30     ` [PATCH v9 7/7] mmc: omap_hsmmc: remove pbias workaround Balaji T K
2014-01-13 15:36   ` [PATCH v10 0/7] mmc: omap_hsmmc: pbias dt and cleanup Balaji T K
2014-01-13 15:36     ` [PATCH v10 1/7] mmc: omap_hsmmc: use devm_regulator API Balaji T K
2014-01-13 15:36     ` [PATCH v10 2/7] mmc: omap_hsmmc: handle vcc and vcc_aux independently Balaji T K
2014-01-13 15:36     ` [PATCH v10 3/7] regulator: add pbias regulator support Balaji T K
2014-01-13 15:36     ` [PATCH v10 4/7] mmc: omap_hsmmc: adapt hsmmc to use pbias regulator Balaji T K
2014-01-13 15:36     ` [PATCH v10 5/7] ARM: dts: add pbias dt node Balaji T K
2014-01-15 15:09       ` Balaji T K
2014-01-13 15:36     ` [PATCH v10 6/7] ARM: OMAP: enable SYSCON and REGULATOR_PBIAS in omap2plus_defconfig Balaji T K
2014-01-13 15:36     ` [PATCH v10 7/7] mmc: omap_hsmmc: remove pbias workaround Balaji T K
2014-02-04  8:32     ` [PATCH v10 0/7] mmc: omap_hsmmc: pbias dt and cleanup Balaji T K
2014-02-19 14:56     ` [PATCH RESEND " Balaji T K
2014-02-19 14:56       ` [PATCH RESEND v11 1/7] mmc: omap_hsmmc: use devm_regulator API Balaji T K
2014-02-19 14:56       ` [PATCH RESEND v11 2/7] mmc: omap_hsmmc: handle vcc and vcc_aux independently Balaji T K
2014-02-19 14:56       ` [PATCH RESEND v11 3/7] regulator: add pbias regulator support Balaji T K
2014-02-19 14:56       ` [PATCH RESEND v11 4/7] mmc: omap_hsmmc: adapt hsmmc to use pbias regulator Balaji T K
2014-02-19 14:56       ` [PATCH RESEND v11 5/7] ARM: dts: add pbias dt node Balaji T K
2014-02-19 14:56       ` [PATCH RESEND v11 6/7] ARM: OMAP: enable SYSCON and REGULATOR_PBIAS in omap2plus_defconfig Balaji T K
2014-02-26 17:01         ` Tony Lindgren
2014-03-03 14:33           ` Balaji T K
2014-02-19 14:56       ` [PATCH RESEND v11 7/7] mmc: omap_hsmmc: remove pbias workaround Balaji T K
2014-02-26  8:51       ` [PATCH RESEND v10 0/7] mmc: omap_hsmmc: pbias dt and cleanup Stefan Roese
2014-02-26 14:04       ` Florian Vaussard
2014-02-26 14:43         ` Balaji T K

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=52D02737.6060609@ti.com \
    --to=balajitk@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=broonie@kernel.org \
    --cc=cjb@laptop.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).