From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Mon, 8 Apr 2019 21:41:49 -0400 Subject: [U-Boot] [PATCH] arm: sunxi: Enable DM_MMC on required SoCs In-Reply-To: <20190408202754.18451-1-jagan@amarulasolutions.com> References: <20190408202754.18451-1-jagan@amarulasolutions.com> Message-ID: <20190409014149.GG4664@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: u-boot@lists.denx.de On Tue, Apr 09, 2019 at 01:57:54AM +0530, Jagan Teki wrote: > Enabling DM_MMC is forcing CONFIG_BLK=3Dy so if any board which uses > SCSI must need to enable DM_SCSI otherwise SCSI reads on that particular > target making invalid reading to the disk drive. >=20 > Allwinner platform do support SCSI on A10, A20 and R40 SoC's out of > these only A10 have DM_SCSI enabled. So enabling DM_MMC on A20, R40 > would eventually end-up with scsi disk read failures like [1] >=20 > So, enable DM_MMC in all places of respective SoC's instead of enabling > them globally to Allwinner platform. >=20 > Now, DM_MMC is enabled in Allwinner SoC's except A20 and R40. >=20 > [1] https://lists.denx.de/pipermail/u-boot/2019-April/364057.html >=20 > Reported-by: Pablo Sebasti=C3=A1n Greco > Signed-off-by: Jagan Teki Thanks for coming up with the root cause and a work around quickly! Applied to u-boot/master, thanks! --=20 Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: