[U-Boot] [RFC for-v2019.01 1/4] dm: MIGRATION: Add migration plan for DM_MMC

[Tom Rini]

On Mon, Nov 26, 2018 at 09:09:50AM -0600, Adam Ford wrote:
> On Sun, Nov 25, 2018 at 12:19 PM Tom Rini <trini at konsulko.com> wrote:
> >
> > Given that at this point the MMC subsystem itself has been migrated
> > along with a number of subsystem drivers, formalize a deadline for
> > migration.
> >
> > Cc: Simon Glass <sjg at chromium.org>
> > Cc: Jaehoon Chung <jh80.chung at samsung.com>
> > Signed-off-by: Tom Rini <trini at konsulko.com>
> 
> Out of curiosity, the series of patches are forcing various block
> devices to comply with CONFIG_BLK by a certain deadline.  What about
> the more fundamental CONIFG_DM requirement?  I know the CONFIG_BLK
> implies CONFIG_DM is enabled, but if people don't have block devices
> for some reason, there might be a few devices missed, so a warning
> indicating CONFIG_DM isn't enabled might also be useful.

So, yes, we have not yet set a deadline on basic DM conversion.  I
haven't yet, and there's a few arches that haven't started and I'm
talking with privately to see where things stand there.

>   My other concern about SPL devices where disabling DM in SPL saves
> space, or in some cases is required to fit.

Yes, what to do when switching to platform data isn't enough is an open
question and I'm of a few minds still on if we should:
- Allow some drivers to retain non-DM for SPL-only.
- Declare that "TPL" is where the truly small and board/SoC/etc specific
  drivers need to reside.
- Something else.

As there's pros and cons to both of those approaches.

-- 
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/20181126/755c9f8a/attachment.sig>