Received: by 2002:a05:6a10:6006:0:0:0:0 with SMTP id w6csp1040071pxa; Fri, 28 Aug 2020 01:47:19 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx3LVckFAxZ+fFSbQ9Vcp6+dsNym9dD137pFcsO2cmpPZJtP+JmSjGe/S45rNJ1JqSNvZLE X-Received: by 2002:a17:906:d206:: with SMTP id w6mr738685ejz.428.1598604439471; Fri, 28 Aug 2020 01:47:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1598604439; cv=none; d=google.com; s=arc-20160816; b=UUpLYBuP0H7LfZ6elcxzfcCbB4CHK2wZjL1sk+8eZAQMsgRSP0LyJKb8l0LY1qJLbI ixMzkJY/4oxfKE82aimTDUYpDtEoG8qBQgLb5ETx6vd84rau+6v8K1r8snDq8V0rwHvX FnFqOXYRjzV11vYc6B+Kvunl7m8XhLEgfitmDpKFffxudTkk2vjtN/cHkO/stsmY3BxR PDilHPkLvHRIXAyhZZV4PgF0xkJcUi2f3l1VumIU6O0avvPkG3fQJYEuWAzD0T5So3NV VlLRS2+DFqaXPZ9o6J6iUCMdDO8r0kMMXJPNxtAn1M0ZgXzkwI03cIIbUQYUpRXMPf7h 2bYg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=i68K1oVW//N2+LJY/Znt9A9GXSvc2knY+uF5OLZlW3E=; b=0yWDXGm9s3x1cBTHD/IkScVp3KnV3/vL9/xnuY9bb/VnObjw3UKvEHG6DMMbb/Cn3D RVClE0IqAXnO4N8WIUx6ucJgvDgbvTmVrQ01UqvqQGu8z6aeuC4R+xWK1je5lmfsoM+3 keuqY+Rq7UbOergjZ0zzKj6PLOrmMdBwWIwZjB7/bNFlqfwZcZdB2C9jGvYiHruNe9rn MLMT+FaJ/TfwIjFbCQIDqyPmLnVm+O3HT7SwmTvqNLnT6nFgfdcid+Q78DFfRYQKOtCw xHBXCdqrxmDSdYj4vwwrC52bwR+DWCNlgb+CubqXWMKH+h/8P+0uJPbzx93xNS8pe6Fb wMZg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=T11C7mph; 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=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id q25si175398edt.60.2020.08.28.01.46.56; Fri, 28 Aug 2020 01:47:19 -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=@linaro.org header.s=google header.b=T11C7mph; 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=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728751AbgH1Ipe (ORCPT + 99 others); Fri, 28 Aug 2020 04:45:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58692 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728742AbgH1Iov (ORCPT ); Fri, 28 Aug 2020 04:44:51 -0400 Received: from mail-vk1-xa43.google.com (mail-vk1-xa43.google.com [IPv6:2607:f8b0:4864:20::a43]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7C0FDC061236 for ; Fri, 28 Aug 2020 01:44:51 -0700 (PDT) Received: by mail-vk1-xa43.google.com with SMTP id k1so80149vkb.7 for ; Fri, 28 Aug 2020 01:44:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=i68K1oVW//N2+LJY/Znt9A9GXSvc2knY+uF5OLZlW3E=; b=T11C7mphpjdwy94FR3QiUCw/s5gZrgGyEYLzUcAk2VBMcgtTsIiASblHRXVOWjTR8f fSKqXBAkgf1x0Aawx9GdU41IiybGpPpfdoZ24viRcWevKccV7/LcywLkUf39qPSUIgHM gs3BKu6/VuSar3C7KsUUdC7YkhhrLIOQuBKubp2UruUbOs/EryrB50B+emHFGs2JTcpL VnPJw8ECgwjn62NENrOKdNdJnG69PlgCedXkB67QgRMqh5EHp/8AIAUYzOyGUVsoAk4o QKcK/gsJaQdig0KI4JuE1N5YPUHbqVZcGeOdMXpK93TV0Xm1DzaetY5de3wKBWnGDfMQ EuFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=i68K1oVW//N2+LJY/Znt9A9GXSvc2knY+uF5OLZlW3E=; b=dvHnuqBYYZQDebQSMCxygmE3Uu7xgiVy6so6MAS8so/A9CTNavamELV1S4+dY0/9nh mtvFgPSdKfBHA2objcfAyOqAXFsaHz/31LTZX7nzIKs3BHFzYn5LQ+QesN3Q4oLTY+vn Btsc//EXBJFvgl/ffqopbkyFexxz/Dqs4eu6DlZxafoHSoO3fAUYrWaWx2wvsBP3MeNf DE6oXfBUzZ/6yPif8A+7IT+WjIW1E3U+EL4BdnTMI30QAXSWUwFpxL0iDs3UA+4R0EMZ ZOPYJejGCy6UzMNz5ysVHHJI5CrnnKgHkL0u2nzTap3qpbVJayRO5CQDm5XgCT6pLY1N lyPg== X-Gm-Message-State: AOAM531DU/rsnDvU9zCaGlkse2wKSb0vXphH2eVq7Sddmlm7gxOPjliV r8E/v+CsVv5So36wi1FPIdvdJc7IQwgtO3OxY5sgXg== X-Received: by 2002:a1f:2a48:: with SMTP id q69mr199169vkq.69.1598604290613; Fri, 28 Aug 2020 01:44:50 -0700 (PDT) MIME-Version: 1.0 References: <1598548861-32373-1-git-send-email-skomatineni@nvidia.com> In-Reply-To: <1598548861-32373-1-git-send-email-skomatineni@nvidia.com> From: Ulf Hansson Date: Fri, 28 Aug 2020 10:44:12 +0200 Message-ID: Subject: Re: [PATCH v7 0/7] Fix timeout clock used by hardware data timeout To: Sowjanya Komatineni Cc: Adrian Hunter , Thierry Reding , Jon Hunter , Rob Herring , linux-tegra , Linux Kernel Mailing List , "linux-mmc@vger.kernel.org" , DTML , "# 4.0+" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 27 Aug 2020 at 19:21, Sowjanya Komatineni wrote: > > Tegra210/Tegra186/Tegra194 has incorrectly enabled > SDHCI_QUIRK_DATA_TIMEOUT_USES_SDCLK from the beginning of their support. > > Tegra210 and later SDMMC hardware default uses sdmmc_legacy_tm (TMCLK) > all the time for hardware data timeout instead of SDCLK and this TMCLK > need to be kept enabled by Tegra sdmmc driver. > > This series includes patches to fix this for Tegra210/Tegra186/Tegra194. > > These patches need to be manually backported to 4.19. > > Will send patches for 4.19 backport separately. > > Delta between patch versions: > [v7]: v7 has below change > - v6 has implementation for retrieving tmclk irrespective of > clocks order. But based in internal discussion with Thierry > this is not required as typically order specified in DT > bindings is the order validator want to see in DT. > > [v6]: v5 is sent out mistakenly with incorrect patches. > v6 includes proper patches addressing v4 feedback > - updated dt-binding doc to be more clear > - updated Tegra sdhci driver to retrieve sdhci and tmclk clocks > based on no. of clocks in sdhci device node as old device trees > do not use sdhci clock name and this allows proper clock retrival > irrespective of sdhci and tmclk clocks order in device tree. > - Added separate quirk for identifying SoC's supporting separate > timeout clock to be more clear. > > [v5]: Include below changes based on v4 feedback > - updated dt-binding doc to be more clear > - updated Tegra sdhci driver to retrieve sdhci and tmclk clocks > based on no. of clocks in sdhci device node as old device trees > do not use sdhci clock name and this allows proper clock retrival > irrespective of sdhci and tmclk clocks order in device tree. > - Added separate quirk for identifying SoC's supporting separate > timeout clock to be more clear. > > [v4]: Include additional dt-binding patch > > [v3]: Same as v2 with fixes tag > > [v2]: Includes minor fix > - Patch-0006: parentheses around operand of '!' > > Sowjanya Komatineni (7): > sdhci: tegra: Remove SDHCI_QUIRK_DATA_TIMEOUT_USES_SDCLK for Tegra210 > sdhci: tegra: Remove SDHCI_QUIRK_DATA_TIMEOUT_USES_SDCLK for Tegra186 > dt-bindings: mmc: tegra: Add tmclk for Tegra210 and later > arm64: tegra: Add missing timeout clock to Tegra210 SDMMC > arm64: tegra: Add missing timeout clock to Tegra186 SDMMC nodes > arm64: tegra: Add missing timeout clock to Tegra194 SDMMC nodes > sdhci: tegra: Add missing TMCLK for data timeout > > .../bindings/mmc/nvidia,tegra20-sdhci.txt | 32 +++++++++++-- > arch/arm64/boot/dts/nvidia/tegra186.dtsi | 20 ++++---- > arch/arm64/boot/dts/nvidia/tegra194.dtsi | 15 +++--- > arch/arm64/boot/dts/nvidia/tegra210.dtsi | 20 ++++---- > drivers/mmc/host/sdhci-tegra.c | 55 ++++++++++++++++++++-- > 5 files changed, 113 insertions(+), 29 deletions(-) > > -- > 2.7.4 > Applied for fixes, thanks! Kind regards Uffe