Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp832717yba; Wed, 24 Apr 2019 10:19:01 -0700 (PDT) X-Google-Smtp-Source: APXvYqzsqrPr5u7wlnzBhP6Z4+lAmt4YZLIv7uY7i6xd8SGQAN8hG4vI+FlGuNVcR9g26xwngf5Y X-Received: by 2002:a17:902:e110:: with SMTP id cc16mr32943420plb.147.1556126341054; Wed, 24 Apr 2019 10:19:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556126341; cv=none; d=google.com; s=arc-20160816; b=kYasdatIg9eTmqzYCwpkzntgSsPNoziuuZGZZoo993FjZzPmDbXwottFXuVDSUZjO1 iBuo1Cz9P8qA9DY3jcZ7ruzhcPsZ+ZrClVCRxEjRerOz03Ljpal/SIND7ojMpMr4a33+ U94Z59LJa21rLUHikngadmrVgP6fsFwAoIzN/NgdaaJcM6VJjxqnZUXu3wWLEAl5vofY rO/5zAP4j2bO9qi/x0hLsczZe/p9PwIFRu5uiXh/qAImt6fQIcxMw5sSYIwIqvup28bT N68hSAmE32gFTwQE+MEnizhnPYhAEdkGZEdqlKEZw0jVJl3gedAea7UDSCmYlki2D7ql auEg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=k91gGDFEKPgrrKOyEdSVknhf+eFqu86O3YACuEFqjZA=; b=QG11hkd9Q2C/qt+K56kfUriS9KKfeIh3Q5Vip5EH6kp3x78wyHS/NkdIVixuXFrnXJ MxPU7ERb9jsWpKBO73DXBj0CsbZNQdTxOF+p2ZKIH1V1cTJtLNNef2ORURHf5e79nnWK 0d18ilBkMKyHS7HcVI/CVH5EmCZbtyPwRUelA2unJBWCnV5rp/8o1bq/MaSjTm9XiNX0 vFWj5uJCgnHjm8ZG+naxF2vauoZCh5DQRP2W0rvfP+GPRP5PAs0rMKmGyAmgJXYSsFKw lpx8qufVbyPWKd9U67blnxepILfgY9TZlM6woUTlyJH5+3WGGthzbFi5S/23Hu2YUBaI 3+Tw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=gxPfEdtn; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a190si18448276pge.88.2019.04.24.10.18.45; Wed, 24 Apr 2019 10:19:01 -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; dkim=pass header.i=@kernel.org header.s=default header.b=gxPfEdtn; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388541AbfDXRRD (ORCPT + 99 others); Wed, 24 Apr 2019 13:17:03 -0400 Received: from mail.kernel.org ([198.145.29.99]:41696 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387765AbfDXRQ7 (ORCPT ); Wed, 24 Apr 2019 13:16:59 -0400 Received: from localhost (62-193-50-229.as16211.net [62.193.50.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 7010E2054F; Wed, 24 Apr 2019 17:16:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1556126218; bh=mndFGD+NbQ7efly0W+gyY3LNQA2jJx4fntKFmjcS94I=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=gxPfEdtnG5CmaZY65o7P34DawCfovots/84Vs7NmUTBgMc+nEnp0bunT6NHkLl1yM a1MsUWsHgp37wnPiKoVrr2be2AakAH7wRnrbmZ/lGD2GDg8qS9RDjgCo3ISRb+8TB6 A0Rt9wdRKSEQSWoZEiQgT4dMHPiEkx9N2fO65WHA= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Aaro Koskinen , Ulf Hansson , Sasha Levin Subject: [PATCH 4.4 032/168] mmc: omap: fix the maximum timeout setting Date: Wed, 24 Apr 2019 19:07:56 +0200 Message-Id: <20190424170925.615693331@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190424170923.452349382@linuxfoundation.org> References: <20190424170923.452349382@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [ Upstream commit a6327b5e57fdc679c842588c3be046c0b39cc127 ] When running OMAP1 kernel on QEMU, MMC access is annoyingly noisy: MMC: CTO of 0xff and 0xfe cannot be used! MMC: CTO of 0xff and 0xfe cannot be used! MMC: CTO of 0xff and 0xfe cannot be used! [ad inf.] Emulator warnings appear to be valid. The TI document SPRU680 [1] ("OMAP5910 Dual-Core Processor MultiMedia Card/Secure Data Memory Card (MMC/SD) Reference Guide") page 36 states that the maximum timeout is 253 cycles and "0xff and 0xfe cannot be used". Fix by using 0xfd as the maximum timeout. Tested using QEMU 2.5 (Siemens SX1 machine, OMAP310), and also checked on real hardware using Palm TE (OMAP310), Nokia 770 (OMAP1710) and Nokia N810 (OMAP2420) that MMC works as before. [1] http://www.ti.com/lit/ug/spru680/spru680.pdf Fixes: 730c9b7e6630f ("[MMC] Add OMAP MMC host driver") Signed-off-by: Aaro Koskinen Signed-off-by: Ulf Hansson Signed-off-by: Sasha Levin --- drivers/mmc/host/omap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/mmc/host/omap.c b/drivers/mmc/host/omap.c index 5bcf4f45f8b4..20d422558fa3 100644 --- a/drivers/mmc/host/omap.c +++ b/drivers/mmc/host/omap.c @@ -921,7 +921,7 @@ static inline void set_cmd_timeout(struct mmc_omap_host *host, struct mmc_reques reg &= ~(1 << 5); OMAP_MMC_WRITE(host, SDIO, reg); /* Set maximum timeout */ - OMAP_MMC_WRITE(host, CTO, 0xff); + OMAP_MMC_WRITE(host, CTO, 0xfd); } static inline void set_data_timeout(struct mmc_omap_host *host, struct mmc_request *req) -- 2.19.1