From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Fri, 2 Sep 2011 13:43:31 +0300 Subject: [PATCH 6/7] OMAP3: board-dt: Add generic board file for DT support In-Reply-To: <4E609800.9090402@ti.com> References: <1314897912-18178-1-git-send-email-b-cousson@ti.com> <1314897912-18178-7-git-send-email-b-cousson@ti.com> <20110902080944.GP3548@atomide.com> <4E609800.9090402@ti.com> Message-ID: <20110902104330.GR3548@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Cousson, Benoit [110902 11:13]: > Hi Tony, > > On 9/2/2011 10:09 AM, Tony Lindgren wrote: > >Hi, > > > >* Benoit Cousson [110901 19:52]: > >>Create an OMAP3 generic board to start the DT migration. > > > >I don't think this needs to be SoC specific, we can add multiple > >DT_MACHINE_START entries into a single file. So it should be > >just board-omap-dt.c. > > I do agree, it should not, I made that comment into the > board-omap4-dt.c, but for the moment we still have dedicated OMAP > specifics stuff at board level, like the map_io. Well map_io can also be set in DT_MACHINE_START. For most part it already is generic like omap3_map_io and omap4_map_io. So that should not stop anything. > I have an other series that make the map_io DT aware to get rid of > that, but it still not finalized. Hmm maybe take a look again? We've already sorted out quite a bit of the init stuff over past few merge windows. If there's still something blocking that, let's clear it out ASAP. > My goal was have a single DT_MACHINE_START for every OMAPs. > But, meanwhile, if you prefer one file with many board descriptors, > that's fine. Yes that's better. We should only need a separate DT_MACHINE_START for major SoC variants. Regards, Tony