From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Wed, 17 Sep 2014 08:08:18 -0700 Subject: [PATCH] arm: omap2: n8x0: move i2c devices to DT In-Reply-To: <20140917150205.GB6903@saruman.home> References: <1410899500-21323-1-git-send-email-balbi@ti.com> <20140916203337.GI19010@saruman.home> <20140917145131.GB7987@atomide.com> <20140917150205.GB6903@saruman.home> Message-ID: <20140917150818.GB14505@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Felipe Balbi [140917 08:03]: > On Wed, Sep 17, 2014 at 07:51:32AM -0700, Tony Lindgren wrote: > > * Felipe Balbi [140916 13:34]: > > > On Tue, Sep 16, 2014 at 03:31:40PM -0500, Felipe Balbi wrote: > > > > By moving i2c devices to DT we can clean up > > > > i2c_board_info and fix a problem with moving > > > > INTC to irq domain where IRQs can be renumbered > > > > on each boot. > > > > > > > > Cc: Aaro Koskinen > > > > Signed-off-by: Felipe Balbi > > > > > > note that this only causes problem for N8x0 because it boots in kinda of > > > a hybrid way, where it uses DT but not all peripherals are created > > > through DT. > > > > Thanks applying this into omap-for-v3.18/intc-v2. > > it might be better to apply this on your DT branch and merge DT before > intc-v2, that might avoid a bisection problem. Yes it would have been nice to have this as a patch before preparing for intc-v2, but I did not have my n8x0 booting reliably because of xhci vs ehci issues on my PC and did not notice it early enough. I've already sent a pull request for the first part of intc-v2, so best to keep the related changes together in this case. Regards, Tony