From: Valentin Schneider <valentin.schneider@arm.com>
To: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: catalin.marinas@arm.com, will.deacon@arm.com, arnd@arndb.de,
john.stultz@linaro.org, liwei213@huawei.com,
zhangfei.gao@linaro.org, guodong.xu@linaro.org,
Valentin Schneider <valentin.schneider@arm.com>
Subject: [PATCH 1/1] arm64: defconfig: Update UFSHCD for Hi3660 soc
Date: Fri, 7 Sep 2018 21:13:20 +0100 [thread overview]
Message-ID: <1536351200-1427-1-git-send-email-valentin.schneider@arm.com> (raw)
Commit 7ee7ef24d02d ("scsi: arm64: defconfig: enable configs for
Hisilicon ufs") enabled the Hisilicon UFS, which means that we can
flash a rootfs to the on-board flash. However, as it stands, the
kernel gets stuck on:
[ 3.360733] Waiting for root device /dev/sdd10...
That seems to be because even though we have SCSI_UFS_HISI=y,
SCSI_UFSHCD and SCSI_UFSHCD_PLATFORM are set to 'm', which means the
required drivers won't be built-in.
We need those to load the rootfs and then load the modules, so set
them as built-ins.
Signed-off-by: Valentin Schneider <valentin.schneider@arm.com>
---
arch/arm64/configs/defconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index db8d364..ab7f80a 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -193,8 +193,8 @@ CONFIG_BLK_DEV_SD=y
CONFIG_SCSI_SAS_ATA=y
CONFIG_SCSI_HISI_SAS=y
CONFIG_SCSI_HISI_SAS_PCI=y
-CONFIG_SCSI_UFSHCD=m
-CONFIG_SCSI_UFSHCD_PLATFORM=m
+CONFIG_SCSI_UFSHCD=y
+CONFIG_SCSI_UFSHCD_PLATFORM=y
CONFIG_SCSI_UFS_HISI=y
CONFIG_SCSI_UFS_QCOM=m
CONFIG_ATA=y
--
2.7.4
reply other threads:[~2018-09-07 20:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1536351200-1427-1-git-send-email-valentin.schneider@arm.com \
--to=valentin.schneider@arm.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=guodong.xu@linaro.org \
--cc=john.stultz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liwei213@huawei.com \
--cc=will.deacon@arm.com \
--cc=zhangfei.gao@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).