From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Subject: Re: [PATCH v2] ARM: dts: am335x-bone-common: Add i2c2 definition Date: Tue, 13 May 2014 10:13:30 -0400 Message-ID: <5372288A.5010403@ti.com> References: <1399686184-1594-1-git-send-email-mranostay@gmail.com> <20140512195050.GB5668@atomide.com> <20140512201517.GC5668@atomide.com> <20140512204213.GD5668@atomide.com> <537215D3.70306@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Javier Martinez Canillas Cc: Robert Nelson , Tony Lindgren , Matt Ranostay , robh+dt@kernel.org, Mark Rutland , Russell King , "linux-omap@vger.kernel.org" , devicetree , linux kernel , Pantelis Antoniou , Matt Porter List-Id: devicetree@vger.kernel.org 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