On Thu, May 9, 2019 at 3:02 PM Joe Hershberger <[email protected]> wrote: > > On Wed, Apr 17, 2019 at 4:02 AM Yinbo Zhu <[email protected]> wrote: > > > > From: Yinbo Zhu <[email protected]> > > > > At present the MMC subsystem maintains its own list > > of MMC devices. This cannot work with driver model > > when CONFIG_BLK is enabled, use blk_dread to > > replace previous mmc read interface, > > > > Signed-off-by: Yinbo Zhu <[email protected]> > > --- > > drivers/net/phy/cortina.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/drivers/net/phy/cortina.c b/drivers/net/phy/cortina.c > > index a04a118f90..2337c3403c 100644 > > --- a/drivers/net/phy/cortina.c > > +++ b/drivers/net/phy/cortina.c > > @@ -176,7 +176,7 @@ void cs4340_upload_firmware(struct phy_device *phydev) > > printf("MMC read: dev # %u, block # %u, count %u ...\n", > > dev, blk, cnt); > > mmc_init(mmc); > > - (void)mmc->block_dev.block_read(&mmc->block_dev, blk, cnt, > > + (void)blk_dread(mmc_get_blk_desc(mmc), blk, cnt, > > addr); > > Should this be switching on CONFIG_BLK or CONFIG_DM_MMC or something.
Any word? > > > } > > #endif > > -- > > 2.17.1 > > > > _______________________________________________ > > U-Boot mailing list > > [email protected] > > https://lists.denx.de/listinfo/u-boot _______________________________________________ U-Boot mailing list [email protected] https://lists.denx.de/listinfo/u-boot
