Received: by 2002:a05:6a10:6d10:0:0:0:0 with SMTP id gq16csp927378pxb; Fri, 22 Apr 2022 14:32:19 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwQm27ypC6ODdjE29vrVDOsrudYV6aiGCnr0Q/tCEmyUr3VD7jprwnufq2XkEMfh4t+n911 X-Received: by 2002:a05:6a00:190a:b0:4fa:e4e9:7126 with SMTP id y10-20020a056a00190a00b004fae4e97126mr6781981pfi.65.1650663139045; Fri, 22 Apr 2022 14:32:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1650663139; cv=none; d=google.com; s=arc-20160816; b=Pw5qyngC1OP+lDoLnTWbKC3HbymNlVGnpzCYLR93e8At79gDChLhHqBnMwZN78241F 0ljVp69e6vtxQi7QlXWWc9OO3gmruFVSKmYnbnl6llV/3U87CNQ1XczRnmwwHzbf+oRx lu1nF0Ov7fR47vLCd6Z25AmzkScMCOrs/BV7p6g71NiZNA9c9Iq4eoobdeC8uog0NIK8 wpC14ino8gtS+pPt5/jFGxHBMKvYI/mqjFoKHCcwOjTGSgloDgN9gO/IYshodlGPvWpu 7liCZOkQv6RzuHfVmCyTT4+TdXuosjTz6zcNQj9beQH3T7z7JO34S4Y8U73uvL8HIECF y0JQ== 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 :message-id:date:subject:cc:to:from:dkim-signature; bh=+6isM9rPgnmUdLXF2PlckUisnk3OJXyXTwV1qms8h1g=; b=M/RNOn3tdwmMhnr4141e9Neyg3YGN7Cxm15M2dGuvyNHhXmJBMIC6+mmhNnK66eOXG DgWj8smknl/yn9LhM+gvHisp79XwS0/h4BK34OTRftd5tB9UxNNzRw8ev3q+IrydMYjv 6/ufylpuEnmwO5MqvnsGGuBeNG2EyHYH6qcnkffVXc4KDueGySGTcp3hpqiAz34Wvj0a 9lHEifzgvdHR4lXsok4D2Czu0V051zk4pyAubrmiAu2zrOAmSWRU8IiR88MaKzfMvsaH GVMbuZObQ/tonvDrBAamTMO6xhNwyIiSpuCIRURZgNhTTpl1KFzim5Rq72VhSkpLoXkp gVtA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=JkjgNHqR; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id u13-20020a17090341cd00b00153b2d1644asi1705425ple.82.2022.04.22.14.32.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Apr 2022 14:32:19 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=JkjgNHqR; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id CDA8F1F7D65; Fri, 22 Apr 2022 12:39:35 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1442934AbiDVA0c (ORCPT + 99 others); Thu, 21 Apr 2022 20:26:32 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39696 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237771AbiDVA0a (ORCPT ); Thu, 21 Apr 2022 20:26:30 -0400 Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 06C8B4968F for ; Thu, 21 Apr 2022 17:23:39 -0700 (PDT) Received: by mail-pf1-x42e.google.com with SMTP id p8so6448346pfh.8 for ; Thu, 21 Apr 2022 17:23:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=+6isM9rPgnmUdLXF2PlckUisnk3OJXyXTwV1qms8h1g=; b=JkjgNHqRJy5KbgBIvYEyVrAQfuO80ZGbKWjGP0AAoCINZl3bLn8bhvXCOJDpJlBEg8 NxDF/tX5kFkyv2So8OCMnsp6byZmGV0iLZyjfq2lySItBZdUFok0gz4ls+HHzO9x4G+V HbJ1JqlETnEvoxCJLE4CudRot06gz5NBzz6Zo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=+6isM9rPgnmUdLXF2PlckUisnk3OJXyXTwV1qms8h1g=; b=cjkDcMArFjwY3zKBRUHjB/DHtoovOrtFPkdrevcZmHyE583K77w2IXTNiiV91Sxsna 7TKeIadRHnRFJWU29NMHy/qnwWiUAL88DoBLxfsWif7YDOsFXqiUEZjhuuuusM7HGBCK DrkITR+2K6kKBHKrBe/zlf2TIIZ9PSgf7OtGH15rwQOOjbNBahDTJyUNyv0JTUuEdcL/ NJ3l7Ne4osWJQi+E8p6Zu23bWfVMvpcECTfWVD/n3qwkzxRDJ7tHsIFzEvza5rUvQryf zyBwTOEycEs72/RMuFUDwu6H/tPfLeZ7lo1UUZ9Y/70tobIC3iydsBLyWZJB+Ncwp2hZ FA5Q== X-Gm-Message-State: AOAM53053DkXfAY2zrDMVsHKdsXh3MIaCuohenSrEy6yzhJUWVwW/wmt 7nVBdOAak6iU96s0ELnQ0ef13A== X-Received: by 2002:a05:6a02:116:b0:39c:c779:b480 with SMTP id bg22-20020a056a02011600b0039cc779b480mr1655951pgb.311.1650587018436; Thu, 21 Apr 2022 17:23:38 -0700 (PDT) Received: from localhost ([2620:15c:202:201:e283:652b:fb2e:829f]) by smtp.gmail.com with UTF8SMTPSA id k198-20020a633dcf000000b003aa9116ba17sm294393pga.35.2022.04.21.17.23.37 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 21 Apr 2022 17:23:37 -0700 (PDT) From: Brian Norris To: Ulf Hansson Cc: Shawn Lin , linux-mmc@vger.kernel.org, Douglas Anderson , Luca Weiss , linux-kernel@vger.kernel.org, Heiner Kallweit , Adrian Hunter , Brian Norris Subject: [PATCH v2] mmc: core: Don't set HS200 clock rate prematurely Date: Thu, 21 Apr 2022 17:23:18 -0700 Message-Id: <20220422002318.3587413-1-briannorris@chromium.org> X-Mailer: git-send-email 2.36.0.rc2.479.g8af0fa9b8e-goog MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RDNS_NONE,SPF_HELO_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Commit 1c7ec586fe55 ("mmc: core: Set HS clock speed before sending HS CMD13") fixes problems with certain eMMC, but introduced new ones with others: qcom-msm8974-fairphone-fp2: [ 1.868608] mmc0: SDHCI controller on f9824900.sdhci [f9824900.sdhci] using ADMA 64-bit [ 1.925220] mmc0: mmc_select_hs200 failed, error -110 [ 1.925285] mmc0: error -110 whilst initialising MMC card It appears we've overshot the acceptable clock rate here; while JESD84 suggests that we can bump to 52 MHz before switching (CMD6) to HS400, it does *not* say we can switch to 200 MHz before switching to HS200 (see page 45 / table 28). Use the HS bounds (typically 52 MHz) instead of the HS200 bounds (which are only applicable after we successfully switch). Link: https://lore.kernel.org/lkml/11962455.O9o76ZdvQC@g550jk/ Fixes: 1c7ec586fe55 ("mmc: core: Set HS clock speed before sending HS CMD13") Reported-by: Luca Weiss Signed-off-by: Brian Norris --- Apologies for the quick resend; I fumbled the commit/send, even though I had already updated the comments... Changes in v2: * Updated comments drivers/mmc/core/mmc.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/drivers/mmc/core/mmc.c b/drivers/mmc/core/mmc.c index 9ab915b5737a..82ca62c8669c 100644 --- a/drivers/mmc/core/mmc.c +++ b/drivers/mmc/core/mmc.c @@ -1485,13 +1485,15 @@ static int mmc_select_hs200(struct mmc_card *card) goto err; /* - * Bump to HS200 timing and frequency. Some cards don't - * handle SEND_STATUS reliably at the initial frequency. + * Bump to HS timing and frequency. Some cards don't handle + * SEND_STATUS reliably at the initial frequency. + * NB: We can't move to full (HS200) speeds until after we've + * successfully switched over. */ old_timing = host->ios.timing; old_clock = host->ios.clock; mmc_set_timing(host, MMC_TIMING_MMC_HS200); - mmc_set_bus_speed(card); + mmc_set_clock(card->host, card->ext_csd.hs_max_dtr); /* * For HS200, CRC errors are not a reliable way to know the -- 2.36.0.rc2.479.g8af0fa9b8e-goog