From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Mitch Bradley <wmb@firmworks.com>
Cc: Rob Herring <robherring2@gmail.com>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
devicetree-discuss@lists.ozlabs.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rob Herring <rob.herring@calxeda.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Laxman Dewangan <ldewangan@nvidia.com>
Subject: Re: [PATCH 2/2] ARM: dt: tegra: cardhu: register core regulator tps65911
Date: Sun, 3 Jun 2012 19:37:53 +0100 [thread overview]
Message-ID: <20120603183753.GA26676@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FCB8CA9.40602@firmworks.com>
[-- Attachment #1: Type: text/plain, Size: 471 bytes --]
On Sun, Jun 03, 2012 at 06:11:21AM -1000, Mitch Bradley wrote:
> >What device tree seems to need rather badly is a way of representing
> >key/value pairs -
> Perhaps ironically, the fundamental device tree construct - the
> "property" - is a key/value pair.
Yeah, I know - the problem is when the value is itself a node, at least
as far as I can tell. It's also frustrating that nodes have this user
bit of identifying text that we can't seem to use for some reason.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-03 18:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 13:05 [PATCH 1/2] ARM: tegra: config: enable TPS65910 drivers Laxman Dewangan
2012-05-22 13:05 ` [PATCH 2/2] ARM: dt: tegra: cardhu: register core regulator tps65911 Laxman Dewangan
2012-05-22 16:40 ` Stephen Warren
2012-05-22 17:09 ` Laxman Dewangan
2012-05-22 17:19 ` Stephen Warren
2012-05-22 17:56 ` Laxman Dewangan
2012-05-22 18:27 ` Stephen Warren
2012-05-22 18:42 ` Laxman Dewangan
2012-06-01 19:23 ` Stephen Warren
2012-06-01 20:40 ` Mark Brown
2012-06-01 20:44 ` Stephen Warren
2012-06-01 21:04 ` Mark Brown
2012-06-02 21:19 ` Olof Johansson
2012-06-03 2:45 ` Rob Herring
2012-06-03 12:05 ` Mark Brown
[not found] ` <4FCB8CA9.40602@firmworks.com>
2012-06-03 18:37 ` Mark Brown [this message]
2012-06-03 11:55 ` Mark Brown
2012-06-08 19:22 ` Laxman Dewangan
2012-06-09 3:06 ` Mark Brown
2012-06-09 4:24 ` Stephen Warren
2012-06-11 2:57 ` Mark Brown
2012-06-11 15:56 ` Stephen Warren
2012-06-11 16:20 ` 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=20120603183753.GA26676@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rob.herring@calxeda.com \
--cc=robherring2@gmail.com \
--cc=wmb@firmworks.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