From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH v2] ARM: dts: am335x-bone-common: Add i2c2 definition Date: Mon, 12 May 2014 14:07:48 -0700 Message-ID: <20140512210747.GE5668@atomide.com> References: <1399686184-1594-1-git-send-email-mranostay@gmail.com> <20140512195050.GB5668@atomide.com> <20140512201517.GC5668@atomide.com> <20140512204213.GD5668@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Robert Nelson Cc: Tom Rini , Matt Ranostay , robh+dt@kernel.org, mark.rutland@arm.com, Russell King , "linux-omap@vger.kernel.org" , devicetree , linux kernel , Pantelis Antoniou , Matt Porter List-Id: devicetree@vger.kernel.org * Robert Nelson [140512 13:58]: > >> Either case if fine with me. As who knows when the dtc "overlay" will > >> every truly make it mainline, as the capemgr was the only real kernel > >> user of the i2c/at24 eeprom information. > > > > Sounds like we should keep it disabled though so u-boot can be used > > to toggle it while waiting for the capemgr. That's because the board > > has a header for pins, so it's not exactly limited to just the capes. > > > > Anybody working on enabling/disabling cape dtb configurations in u-boot? > > Well, > > Would Tom even approve of that in mainline u-boot? He didn't want my > "invert" the gpio to enable the usb hub on the older beagle xm A/B.. > > http://lists.denx.de/pipermail/u-boot/2014-January/172154.html > > http://lists.denx.de/pipermail/u-boot/2014-January/172274.html Right, no idea. But until we have some way to actually use the capes without conflicting dts entries, I can't merge them. Regards, Tony