Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp641118imm; Fri, 8 Jun 2018 02:51:57 -0700 (PDT) X-Google-Smtp-Source: ADUXVKL7elD9kT+A5l5qhoe9dYTI4QnX7uF6P9UCR7LW9koJ3pehgYc8S+ohZXhwKwyYd/95v/VE X-Received: by 2002:a62:8b0a:: with SMTP id j10-v6mr5347119pfe.28.1528451517387; Fri, 08 Jun 2018 02:51:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528451517; cv=none; d=google.com; s=arc-20160816; b=ZAjE8XVmBYPlBckt/0Hipt7t3ELSxuzj+W6VSOW0WtPaLIfLUPgnJi+k8OxdQO18E8 4zezqdMkkM/cpPJq0mrVqJOXac0WKof5rKiWRbPauJr3xWMTN9G78JbqWpmUzsiwragQ w3UD5MHakq7r9X4UN/2tExvHzmx/dAdszlHtuH5y6N5HyRWecOwg9s5iTbpzBdmol98L B6NQLn1O3YPdESZQR4Wq2qnI/ebY9Lgi6D5II3klmKkeMnbk0v7NNaXqsU5oNs/ItiJS wZOKJujZsROpx0aOS7oAWh5ltAgptYEOreaYuk+a7roCxT67iKzeNyyiwMBfdy/wMTBM echQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from :arc-authentication-results; bh=Dh5B6pCo6ipMNag9uLbR+alcQJxQQ68N4MZnVEGGI1g=; b=wWNgabAHrv3HblC3Q3/kJMLjzfGF18aYc9TKm4esuQ+J1ZZ1EyoVmh+tPrTjxZ4mh7 s59li4A48TrW2JVLt4y0dL0U55QTVOEcucq7AMT/O0zQfEu9tnX14ndX7Pi69XJnv+rX 3oSIgY2kjzjm7c8F++3Iyyb/3VTHUNVP7nufX8kl36vJkwDs5dUVaZNpC0njV+9zhHEi WEib9HpFveId6djl3Ks3sud6X5eLcH5BhYr584vbr7DebJezLpcCw4CxMyLbFkz2zhTx A5I0Ll09eBX1OKhAI2P27acEEMC3c59iubXjeYTnQEXO4EgpZNQ1Tt4lrxtKi2dzvpfI a7dg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x5-v6si22492032pgr.436.2018.06.08.02.51.12; Fri, 08 Jun 2018 02:51:57 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752337AbeFHJuH (ORCPT + 99 others); Fri, 8 Jun 2018 05:50:07 -0400 Received: from mga03.intel.com ([134.134.136.65]:5513 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751176AbeFHJuG (ORCPT ); Fri, 8 Jun 2018 05:50:06 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Jun 2018 02:50:05 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,490,1520924400"; d="scan'208";a="206372410" Received: from shbuild888.sh.intel.com ([10.239.146.239]) by orsmga004.jf.intel.com with ESMTP; 08 Jun 2018 02:50:04 -0700 From: Feng Tang To: linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org, Greg Kroah-Hartman , Ulf Hansson , Adrian Hunter Cc: Feng Tang Subject: [PATCH] mmc: Move the mmc driver init earlier Date: Fri, 8 Jun 2018 17:51:54 +0800 Message-Id: <20180608095154.22413-1-feng.tang@intel.com> X-Mailer: git-send-email 2.14.1 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org When doing some boot time optimization for an eMMC rootfs NUCs, we found the rootfs may spend around 100 microseconds waiting for eMMC card to be initialized, then the rootfs could be mounted. [ 1.216561] Waiting for root device /dev/mmcblk1p1... [ 1.289262] mmc1: new HS400 MMC card at address 0001 [ 1.289667] mmcblk1: mmc1:0001 R1J56L 14.7 GiB [ 1.289772] mmcblk1boot0: mmc1:0001 R1J56L partition 1 8.00 MiB [ 1.289869] mmcblk1boot1: mmc1:0001 R1J56L partition 2 8.00 MiB [ 1.289967] mmcblk1rpmb: mmc1:0001 R1J56L partition 3 4.00 MiB [ 1.292798] mmcblk1: p1 p2 p3 [ 1.300576] EXT4-fs (mmcblk1p1): couldn't mount as ext3 due to feature incompatibilities [ 1.300912] EXT4-fs (mmcblk1p1): couldn't mount as ext2 due to feature incompatibilities And this is a common problem for smartphones, tablets, embedded devices and automotive products. This patch will make the eMMC/SD card start initializing earlier, by changing its order in drivers/Makefile. On our platform, the waiting for eMMC card is almost eliminated with the patch, which is critical to boot time. Signed-off-by: Feng Tang --- drivers/Makefile | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/Makefile b/drivers/Makefile index 24cd47014657..c473afd3c688 100644 --- a/drivers/Makefile +++ b/drivers/Makefile @@ -50,6 +50,9 @@ obj-$(CONFIG_REGULATOR) += regulator/ # reset controllers early, since gpu drivers might rely on them to initialize obj-$(CONFIG_RESET_CONTROLLER) += reset/ +# put mmc early as many morden devices use emm/sd card as rootfs storage +obj-y += mmc/ + # tty/ comes before char/ so that the VT console is the boot-time # default. obj-y += tty/ @@ -128,7 +131,6 @@ obj-$(CONFIG_EISA) += eisa/ obj-$(CONFIG_PM_OPP) += opp/ obj-$(CONFIG_CPU_FREQ) += cpufreq/ obj-$(CONFIG_CPU_IDLE) += cpuidle/ -obj-y += mmc/ obj-$(CONFIG_MEMSTICK) += memstick/ obj-$(CONFIG_NEW_LEDS) += leds/ obj-$(CONFIG_INFINIBAND) += infiniband/ -- 2.14.1