From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: sunxi: Enable DM_MMC on required SoCs
Date: Mon, 8 Apr 2019 21:41:49 -0400 [thread overview]
Message-ID: <20190409014149.GG4664@bill-the-cat> (raw)
In-Reply-To: <20190408202754.18451-1-jagan@amarulasolutions.com>
On Tue, Apr 09, 2019 at 01:57:54AM +0530, Jagan Teki wrote:
> Enabling DM_MMC is forcing CONFIG_BLK=y 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.
>
> 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]
>
> So, enable DM_MMC in all places of respective SoC's instead of enabling
> them globally to Allwinner platform.
>
> Now, DM_MMC is enabled in Allwinner SoC's except A20 and R40.
>
> [1] https://lists.denx.de/pipermail/u-boot/2019-April/364057.html
>
> Reported-by: Pablo Sebastián Greco <pgreco@centosproject.org>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
Thanks for coming up with the root cause and a work around quickly!
Applied to u-boot/master, 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/20190408/c841d586/attachment.sig>
prev parent reply other threads:[~2019-04-09 1:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 20:27 [U-Boot] [PATCH] arm: sunxi: Enable DM_MMC on required SoCs Jagan Teki
2019-04-09 1:41 ` Tom Rini [this message]
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=20190409014149.GG4664@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