Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp711076pxv; Thu, 15 Jul 2021 14:08:47 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx8pOP2yHW5M62VNLmD7515Uhj4Z0eY3N7lilyHoKoiAj7I5eK9Ecd07NFtSkLYtchS4dgv X-Received: by 2002:a17:906:e099:: with SMTP id gh25mr7597063ejb.346.1626383326836; Thu, 15 Jul 2021 14:08:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626383326; cv=none; d=google.com; s=arc-20160816; b=QSv+uMGO6/2P2Xmn7nV/xB4+LLqoU2pKssStPDVSBxaCdmU2JM9x1LWSXrTjBiHq8u CzlxR1HlztdZ04/xbWXd8zn+6fFJFJYYTIlcExWtBF12e037dFIp+9v8r5PhO3y+zTve 4gBolx37oqhY/eSbE04NEy5XhZ4JxkH4vwBBU3FiF+hxuTsEnrhMClBC0gN7wK3ovXdY pZGmWqlMAQzEWB5ArnzQ4XAHs2kUPPFKhiwW77cczM24q52yUexlb/RET1xDPUY7xiKf 99b/5ItwTDbePywJOTj8mlEJQ/kcBbvZeYTAj+wfhVKg4vwDvD1aJ6eYJyZXebJcJhXH 3L0A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=sm8EdcV41EQTDrWlFHPASwfiI7xQc3gkkwYBClgQQMI=; b=tNGeoyyXhE+/7Q/Vj/UjrFddE+6LXMLxisCcEYMt74Nh4lQq9X+i4yOgFKIhyY0guk g/30WISJqgLkEqU+j5e3i4naCp+UvLv/DZiWIAMxQrg40TNYKy6Ee4Ay7At+1e4pwxx1 9CgtZHakEeEkn3yn4Hlh0+gxhvcHpcg+w7Ryhk6JyCS4a4rC++S13HbAu7mdKcDAMRL9 PhqLOBdCMUxk8+ce1VKzZz8HoV9OEtV6w9b26G4YcWDisFcVDN3A72O24ME+furNobyy H84CbAwgGVWMyaU6Kv7ZfN8VcCXV+nameiHD6ZymayEdqop5A8a+nrefJP3Bz+vofdTc 7j+w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=iXHQCk2w; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d21si9278135edx.270.2021.07.15.14.08.21; Thu, 15 Jul 2021 14:08:46 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=iXHQCk2w; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S245705AbhGOTUB (ORCPT + 99 others); Thu, 15 Jul 2021 15:20:01 -0400 Received: from mail.kernel.org ([198.145.29.99]:38918 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242147AbhGOTFK (ORCPT ); Thu, 15 Jul 2021 15:05:10 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 7EF4061410; Thu, 15 Jul 2021 19:01:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1626375666; bh=IRsGpvDEnLkZB5pmpCU3pQWTY0mzb8GmeLn91RKR1EU=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=iXHQCk2wlrKh6kn8++/Xyc71O4siogeklZ+/4JTzXwq4LGYNU6a9CYSwJiynVaqKF gRUSP8W8GGaYmC22z9IXCD0ecaNhTzP9dnTKbyafu+Yw1a0eADBDhXuKPDRDQlmaT9 HNfy1JqcvVm/LIXsC9hDw9FUlwzKhb7EhO4+8ctI= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Al Cooper , Adrian Hunter , Ulf Hansson Subject: [PATCH 5.12 184/242] mmc: sdhci: Fix warning message when accessing RPMB in HS400 mode Date: Thu, 15 Jul 2021 20:39:06 +0200 Message-Id: <20210715182625.737490739@linuxfoundation.org> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210715182551.731989182@linuxfoundation.org> References: <20210715182551.731989182@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Al Cooper commit d0244847f9fc5e20df8b7483c8a4717fe0432d38 upstream. When an eMMC device is being run in HS400 mode, any access to the RPMB device will cause the error message "mmc1: Invalid UHS-I mode selected". This happens as a result of tuning being disabled before RPMB access and then re-enabled after the RPMB access is complete. When tuning is re-enabled, the system has to switch from HS400 to HS200 to do the tuning and then back to HS400. As part of sequence to switch from HS400 to HS200 the system is temporarily put into HS mode. When switching to HS mode, sdhci_get_preset_value() is called and does not have support for HS mode and prints the warning message and returns the preset for SDR12. The fix is to add support for MMC and SD HS modes to sdhci_get_preset_value(). This can be reproduced on any system running eMMC in HS400 mode (not HS400ES) by using the "mmc" utility to run the following command: "mmc rpmb read-counter /dev/mmcblk0rpmb". Signed-off-by: Al Cooper Acked-by: Adrian Hunter Fixes: 52983382c74f ("mmc: sdhci: enhance preset value function") Cc: stable@vger.kernel.org Link: https://lore.kernel.org/r/20210624163045.33651-1-alcooperx@gmail.com Signed-off-by: Ulf Hansson Signed-off-by: Greg Kroah-Hartman --- drivers/mmc/host/sdhci.c | 4 ++++ drivers/mmc/host/sdhci.h | 1 + 2 files changed, 5 insertions(+) --- a/drivers/mmc/host/sdhci.c +++ b/drivers/mmc/host/sdhci.c @@ -1812,6 +1812,10 @@ static u16 sdhci_get_preset_value(struct u16 preset = 0; switch (host->timing) { + case MMC_TIMING_MMC_HS: + case MMC_TIMING_SD_HS: + preset = sdhci_readw(host, SDHCI_PRESET_FOR_HIGH_SPEED); + break; case MMC_TIMING_UHS_SDR12: preset = sdhci_readw(host, SDHCI_PRESET_FOR_SDR12); break; --- a/drivers/mmc/host/sdhci.h +++ b/drivers/mmc/host/sdhci.h @@ -253,6 +253,7 @@ /* 60-FB reserved */ +#define SDHCI_PRESET_FOR_HIGH_SPEED 0x64 #define SDHCI_PRESET_FOR_SDR12 0x66 #define SDHCI_PRESET_FOR_SDR25 0x68 #define SDHCI_PRESET_FOR_SDR50 0x6A