From: Stephen Warren <swarren@wwwdotorg.org>
To: Jon Loeliger <jdl@jdl.com>
Cc: Rob Herring <robherring2@gmail.com>,
Michal Marek <mmarek@suse.cz>,
David Gibson <david@gibson.dropbear.id.au>,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, Stephen Warren <swarren@nvidia.com>
Subject: Re: dtc: import latest upstream dtc
Date: Tue, 09 Oct 2012 15:16:49 -0600 [thread overview]
Message-ID: <50749441.8030307@wwwdotorg.org> (raw)
In-Reply-To: <E1TIktZ-0000U4-Qh@jdl.com>
On 10/01/2012 12:39 PM, Jon Loeliger wrote:
>>
>> What more do you think needs discussion re: dtc+cpp?
>
> How not to abuse the ever-loving shit out of it? :-)
Perhaps we can just handle this through the regular patch review
process; I think it may be difficult to define and agree upon exactly
what "abuse" means ahead of time, but it's probably going to be easy
enough to recognize it when one sees it?
I imagine the most common usage will simply be a bunch of:
#define TEGRA_GPIO_PB0 32
#define TEGRA_GPIO_INT_LEVEL_LOW 8
/ {
xxx {
interrupts = <TEGRA_GPIO_PB0 TEGRA_GPIO_INT_LEVEL_LOW>;
and similarly, simple math:
something = <((FOO << XXX_SHIFT) | (BAR << YYY_SHIFT))>;
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org>
Cc: Michal Marek <mmarek-AlSwsSmVLrQ@public.gmane.org>,
Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: dtc: import latest upstream dtc
Date: Tue, 09 Oct 2012 15:16:49 -0600 [thread overview]
Message-ID: <50749441.8030307@wwwdotorg.org> (raw)
In-Reply-To: <E1TIktZ-0000U4-Qh-CYoMK+44s/E@public.gmane.org>
On 10/01/2012 12:39 PM, Jon Loeliger wrote:
>>
>> What more do you think needs discussion re: dtc+cpp?
>
> How not to abuse the ever-loving shit out of it? :-)
Perhaps we can just handle this through the regular patch review
process; I think it may be difficult to define and agree upon exactly
what "abuse" means ahead of time, but it's probably going to be easy
enough to recognize it when one sees it?
I imagine the most common usage will simply be a bunch of:
#define TEGRA_GPIO_PB0 32
#define TEGRA_GPIO_INT_LEVEL_LOW 8
/ {
xxx {
interrupts = <TEGRA_GPIO_PB0 TEGRA_GPIO_INT_LEVEL_LOW>;
and similarly, simple math:
something = <((FOO << XXX_SHIFT) | (BAR << YYY_SHIFT))>;
next prev parent reply other threads:[~2012-10-09 21:16 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 21:25 [PATCH] dtc: import latest upstream dtc Stephen Warren
2012-09-29 21:06 ` Jon Loeliger
2012-10-01 16:09 ` Rob Herring
2012-10-01 16:13 ` Stephen Warren
2012-10-01 16:13 ` Stephen Warren
2012-10-01 17:56 ` Rob Herring
2012-10-01 17:56 ` Rob Herring
2012-10-01 18:33 ` Stephen Warren
2012-10-01 18:39 ` Jon Loeliger
2012-10-01 18:39 ` Jon Loeliger
2012-10-09 21:16 ` Stephen Warren [this message]
2012-10-09 21:16 ` Stephen Warren
2012-10-09 23:20 ` Mitch Bradley
2012-10-09 23:20 ` Mitch Bradley
2012-10-10 0:04 ` Scott Wood
2012-10-10 0:04 ` Scott Wood
2012-10-10 4:43 ` Warner Losh
2012-10-10 7:24 ` David Gibson
2012-10-10 14:41 ` Warner Losh
2012-10-10 14:41 ` Warner Losh
2012-10-10 23:06 ` David Gibson
2012-10-10 15:16 ` Stephen Warren
2012-10-10 15:33 ` Rob Herring
2012-10-10 16:19 ` Stephen Warren
2012-10-10 17:18 ` Rob Herring
2012-10-10 18:42 ` Stephen Warren
2012-10-10 23:16 ` David Gibson
2012-10-10 23:16 ` David Gibson
2012-10-11 1:42 ` Mitch Bradley
2012-10-11 5:11 ` David Gibson
2012-10-11 5:11 ` David Gibson
2012-10-10 23:09 ` David Gibson
2012-10-10 23:09 ` David Gibson
2012-10-10 15:15 ` Stephen Warren
2012-10-10 15:15 ` Stephen Warren
2012-10-10 16:09 ` Scott Wood
2012-10-10 16:09 ` Scott Wood
2012-10-10 16:22 ` Stephen Warren
2012-10-10 23:18 ` David Gibson
2012-10-12 17:24 ` Stephen Warren
2012-10-13 6:24 ` David Gibson
2012-10-13 6:24 ` David Gibson
2012-10-13 13:42 ` Segher Boessenkool
2012-10-13 13:42 ` Segher Boessenkool
2012-10-14 0:16 ` David Gibson
2012-10-14 0:16 ` David Gibson
2012-10-10 17:09 ` Rob Herring
2012-10-10 18:23 ` Mitch Bradley
2012-10-10 18:23 ` Mitch Bradley
2012-10-10 18:45 ` Stephen Warren
2012-10-10 18:45 ` Stephen Warren
2012-10-10 18:56 ` Mitch Bradley
2012-10-10 18:56 ` Mitch Bradley
2012-10-11 0:14 ` David Gibson
2012-10-10 23:54 ` David Gibson
2012-10-10 18:40 ` Stephen Warren
2012-10-10 18:52 ` Mitch Bradley
2012-10-10 18:52 ` Mitch Bradley
2012-10-01 18:02 ` Jon Loeliger
2012-10-01 18:02 ` Jon Loeliger
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=50749441.8030307@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=jdl@jdl.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=robherring2@gmail.com \
--cc=swarren@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.