Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp663700pxv; Thu, 15 Jul 2021 12:51:05 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyOYGOEuptM5oCt2kSPjjCqAmA7HI5CH3dvZ3f50whdnde+be44pgm/WvK2zFUz+u4rhDiS X-Received: by 2002:a17:906:3acb:: with SMTP id z11mr7488093ejd.0.1626378664799; Thu, 15 Jul 2021 12:51:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626378664; cv=none; d=google.com; s=arc-20160816; b=rkHd1/QnW5kp54sI4qtEKaaLBwu2hEI6PrbRRIWaxF4EsLRCR9iQzowh1/LxBqVg3Q 2yKYlVmMyYskD/LwD4lRis5RDYjYWaBMkNoJ9RQMo0Hv7tZY04GiNOoz7gocpQ4Fvi1H bp9IeqV0HKJVj5I/2ro/ha5pu5Mo/ixitOUOOMGKpYTB/EPtrfc8BG2TABg0kGowgIR9 eSIJtXdHhg7+NYBeuaSPwSIjDp/yJ+dRt/atxVckTeBOwf3GI1G9dc58pHT6X8b1tBNJ UgNcNN9j13NkgUL52pU0cpu1I2bAT/3QoSDEgBJpG3vMNpOaEBIH4KbDSLA/ezy5ld/Z 3OTg== 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=xqykWDPV4E8/dw1Wu35yMNcP6L+qVwHtcT8hHlBhqvFi1II1miqP4m6/YY9IAafJrn phhoh16ghMixXLtvFgwp2f+vpjJ8YrbUY212zvXrQlPsMXxnpsrvtODjmqxgShq6od0Y fsKQ4TBs56UL2do6UTQNB4NOEjjHgqb20juIoqG7qRBSEN8Ql6rD+IfSDuBfMAVuzSNY 1kLRNdezUE8A0wxiKhhE5EfqWovanZ+R7pm9x16trzRqtfyGmC6QtQEa7zlxAzoitGK/ gEbmjFAKxwKEahg1YWwh9Zuo07eYY7IgSbqapXp6AGqo8qcomSueHp3dekJvKBXt5OC5 /Ybg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=ZHgJgBml; 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 c17si8576625edr.45.2021.07.15.12.50.40; Thu, 15 Jul 2021 12:51:04 -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=ZHgJgBml; 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 S1343761AbhGOTr1 (ORCPT + 99 others); Thu, 15 Jul 2021 15:47:27 -0400 Received: from mail.kernel.org ([198.145.29.99]:57698 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S244570AbhGOTQc (ORCPT ); Thu, 15 Jul 2021 15:16:32 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 10785613DB; Thu, 15 Jul 2021 19:12:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1626376353; bh=IRsGpvDEnLkZB5pmpCU3pQWTY0mzb8GmeLn91RKR1EU=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=ZHgJgBmlixw4Ndk2tt4eCazQRJT/bBvzScnh7W/NK6wrMfMg2rnomVYgbNOkIdk0x sj/eQJB9fOYbfYU25OOfRawndJS/M489CvEOwgpwrEM0AatN2I4vWVu4AcLkrSRwrx f4T8qrsrP2uw1JpKqQRThoy4ARR4Z0NEKFe7UoD4= 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.13 208/266] mmc: sdhci: Fix warning message when accessing RPMB in HS400 mode Date: Thu, 15 Jul 2021 20:39:23 +0200 Message-Id: <20210715182646.621298728@linuxfoundation.org> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210715182613.933608881@linuxfoundation.org> References: <20210715182613.933608881@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