From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Sat, 16 Mar 2019 23:16:08 -0400 Subject: [U-Boot] mpc85xx, mpc86xx: device tree model In-Reply-To: References: <20190315160621.GA8732@bill-the-cat> Message-ID: <20190317031608.GJ8732@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Sun, Mar 17, 2019 at 03:01:32AM +0000, Prabhakar Kushwaha wrote: > > > -----Original Message----- > > From: Tom Rini > > Sent: Friday, March 15, 2019 9:36 PM > > To: Prabhakar Kushwaha > > Cc: u-boot at lists.denx.de; York Sun > > Subject: Re: mpc85xx, mpc86xx: device tree model > > > > On Fri, Mar 15, 2019 at 05:05:06AM +0000, Prabhakar Kushwaha wrote: > > > > > Hi Tom, > > > > > > I am seeing following type of build warnings for MMC. > > > > > > +===================== WARNING ====================== This board > > does > > > +not use CONFIG_DM_MMC. Please update the board to use > > CONFIG_DM_MMC > > > +before the v2019.04 release. > > > +Failure to update by the deadline may result in board removal. > > > +See doc/driver-model/MIGRATION.txt for more info. > > > > > > Considering "number" of powerpc platform are not migrated to deice > > > tree. They can not be migrated to CONFIG_DM_MMC withing v2019.04 > > > time-frame (considering rc4 is on 18th march). > > > v2019.07 looks feasible for removing all warning which includes > > > CONFIG_DM_USB, CONFIG_DM_SCSI, CONFIG_DM_PCI, > > CONFIG_DM_SPI_FLASH and > > > CONFIG_DM_MMC. > > > > > > is there any plan of removing boards which don't have CONFIG_DM_MMC > > > for v2019.04? > > > > Good question. Where exactly are we with getting more of PowerPC brought up > > to date with these requirements? > > There are only 2 platforms which are on device tree model. > > Rest (65 targets) still need to be ported. Here 13 are non-NXP and 52 NXP. > I am working internally to get staffed for porting of NXP platform. > For non-NXP , I will reaching platform owners for migration. > > It will take some time. OK. > > I've mentioned before and will say it again, > > I'm inclined to start marking stuff as 'depends on BROKEN' for a release and then > > pulling the underlying code (so in this case, non-DM code from > > drivers/mmc/mmc.c and other MMC-core) for the release following. > > Is enabling 'depends on BROKEN', still allow platform to build and use? Yes, but it'll only buy a little bit of time. Thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: