From: Tom Rini <trini@ti.com>
To: Javier Martinez Canillas <javier@dowhile0.org>
Cc: Robert Nelson <robertcnelson@gmail.com>,
Tony Lindgren <tony@atomide.com>,
Matt Ranostay <mranostay@gmail.com>,
robh+dt@kernel.org, Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@arm.linux.org.uk>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
linux kernel <linux-kernel@vger.kernel.org>,
Pantelis Antoniou <pantelis.antoniou@gmail.com>,
Matt Porter <matt.porter@linaro.org>
Subject: Re: [PATCH v2] ARM: dts: am335x-bone-common: Add i2c2 definition
Date: Tue, 13 May 2014 10:13:30 -0400 [thread overview]
Message-ID: <5372288A.5010403@ti.com> (raw)
In-Reply-To: <CABxcv=nq9XvyN0aPOBFDm0UyoaW-Htyy0tyP3YhYaDnDUo3a5w@mail.gmail.com>
On 05/13/2014 10:06 AM, Javier Martinez Canillas wrote:
> Agreed. I think that until the device tree overlay and the cape
> manager find their way into mainline we should treat capes as if they
> were expansion boards attached to a Computer-on-Module. That is, a
> static based board which its own DTS including the BB{B,W} as an dtsi
> and not something that can be added on runtime.
Sometimes nothing exposes just how big a problem something is (and how
much we need the solution to it) like actually showing the output.
Someone could also start posting the profileN device trees for the
am335x GP EVMs too.
--
Tom
next prev parent reply other threads:[~2014-05-13 14:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 1:43 [PATCH v2] ARM: dts: am335x-bone-common: Add i2c2 definition Matt Ranostay
2014-05-12 19:50 ` Tony Lindgren
2014-05-12 19:59 ` Robert Nelson
[not found] ` <CAOCHtYiYwx_bEsyqkbUTTAbhBYESzvfBOOYeVuFXPS1dDy0ZKA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-12 20:15 ` Tony Lindgren
[not found] ` <20140512201517.GC5668-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2014-05-12 20:27 ` Robert Nelson
[not found] ` <CAOCHtYg6XpF0Gbo4iFqsFvP=QSivQQvCzov8UfxeLXMzrRYEWw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-12 20:42 ` Tony Lindgren
2014-05-12 20:57 ` Robert Nelson
2014-05-12 21:07 ` Tony Lindgren
2014-05-13 12:53 ` Tom Rini
2014-05-13 14:06 ` Javier Martinez Canillas
2014-05-13 14:13 ` Tom Rini [this message]
[not found] ` <CABxcv=nq9XvyN0aPOBFDm0UyoaW-Htyy0tyP3YhYaDnDUo3a5w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-13 14:22 ` Matt Porter
2014-05-13 14:39 ` Javier Martinez Canillas
2014-05-13 17:07 ` Pantelis Antoniou
2014-05-13 17:51 ` Javier Martinez Canillas
2014-05-13 20:24 ` John Syn
2014-05-14 3:39 ` Pantelis Antoniou
[not found] ` <2A5F30DB-EF92-4CFC-BA3C-4ECAE36FD4FF-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-05-14 5:44 ` John Syn
[not found] ` <CF9849B0.24764%john3909-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-05-14 7:12 ` Javier Martinez Canillas
[not found] ` <CABxcv=mWqENSzODJYAJRgDYNy46X6WkQ+0e4NSDt8qE-ob1KuQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-14 3:24 ` Pantelis Antoniou
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=5372288A.5010403@ti.com \
--to=trini@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=javier@dowhile0.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=matt.porter@linaro.org \
--cc=mranostay@gmail.com \
--cc=pantelis.antoniou@gmail.com \
--cc=robertcnelson@gmail.com \
--cc=robh+dt@kernel.org \
--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).