From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] mpc85xx, mpc86xx: device tree model
Date: Sat, 16 Mar 2019 23:16:08 -0400 [thread overview]
Message-ID: <20190317031608.GJ8732@bill-the-cat> (raw)
In-Reply-To: <VI1PR0402MB3854AFB139B8A5761308DAD997460@VI1PR0402MB3854.eurprd04.prod.outlook.com>
On Sun, Mar 17, 2019 at 03:01:32AM +0000, Prabhakar Kushwaha wrote:
>
> > -----Original Message-----
> > From: Tom Rini <trini@konsulko.com>
> > Sent: Friday, March 15, 2019 9:36 PM
> > To: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
> > Cc: u-boot at lists.denx.de; York Sun <york.sun@nxp.com>
> > 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: <http://lists.denx.de/pipermail/u-boot/attachments/20190316/5afed98c/attachment.sig>
next prev parent reply other threads:[~2019-03-17 3:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 5:05 [U-Boot] mpc85xx, mpc86xx: device tree model Prabhakar Kushwaha
2019-03-15 16:06 ` Tom Rini
2019-03-17 3:01 ` Prabhakar Kushwaha
2019-03-17 3:16 ` Tom Rini [this message]
2019-03-18 8:59 ` Heiko Schocher
2019-03-18 14:56 ` York Sun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190317031608.GJ8732@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox