Message ID | 20240207011520.3128382-1-jm@ti.com |
---|---|
Headers |
Return-Path: <linux-kernel+bounces-55779-ouuuleilei=gmail.com@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:7301:168b:b0:106:860b:bbdd with SMTP id ma11csp1929255dyb; Tue, 6 Feb 2024 17:16:09 -0800 (PST) X-Google-Smtp-Source: AGHT+IHUPAwcQmVIgTeIHlOYcp5848efu0AFioC0LUz2cR4QQQAg8CprRj3FVcYx8komKjxQEPcK X-Received: by 2002:a05:6808:189c:b0:3bf:e9d3:f405 with SMTP id bi28-20020a056808189c00b003bfe9d3f405mr498504oib.36.1707268569347; Tue, 06 Feb 2024 17:16:09 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1707268569; cv=pass; d=google.com; s=arc-20160816; b=Vnl6QjnmnjyUAU1uchEpdnneOZTz7I9GYdC2qjAv559z1pP80wNoLaFHnkFex9Trch dJM6lsEVsc+8u+4rVOICZkZdfaYV9CGrtJSc2dqhiJYkQnfkY50Y+F59PupYVcR2i+n6 Gc9zNfSOEarLCc10OqOXbwRRcu5qATTu9tG+o35XDD1PPSEME87vh0H9+2GqjuvDzVlU /DsqNaauLqXzJFDPVI3iCFfLypHJq6eXGlMPZkbUDnUNbSnvXT+WDg2oEQYFJe3z+dKE xQLy8rglXI6/aIlhihlR/zjJ0DWtuX6SvklT0tnXOblEv1fGFZKxX7aYSuPSd2NVJmVP woTA== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:message-id:date:subject:cc:to :from:dkim-signature; bh=nLwkfNDASkjCG3CEoS36quV/YANOd685QNozGD7eIdE=; fh=nA7OabaabLns86tc90lm+4PDblolJH4zn6vf6lBy5d0=; b=h2VzTDIPxyrZBcNZc4boLKKHQn0xmNNxjCB6WP4XC4N3mXnuDjX4FSKGhQIaCtcie7 ptSYc0sQ3+/3umZ+qHH9VP15P42O7RP//y0Iza6Ldn0ZGfU26j50mzZ6ykisrKNfEFPs t+1qqCf1uPZLFBHEIkhVnAw6XrM8g4U2/rRo6jHyiDAhlIWOHSlV5BGiFRDGeOo5B4vy adrL0VCTdsOoLpCl7lHfyHdRYTY/B1xdNGTR28SFHm5BIGt7d8XU0VD4HKdEWDQdGZrs Tf8FTJ/ANnJxcN+MeshwW6dMJdryibT8RKoAAauIt+EDDfiyIxL0aSLduozurPfNRfki fjuQ==; dara=google.com ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=gQVmsxkr; arc=pass (i=1 spf=pass spfdomain=ti.com dkim=pass dkdomain=ti.com dmarc=pass fromdomain=ti.com); spf=pass (google.com: domain of linux-kernel+bounces-55779-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-55779-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com X-Forwarded-Encrypted: i=2; AJvYcCVAtGwCeezaYrc6gP+lOQW6ACySyxCp1pM5G7bULd0nxn18CwxwZ5RFk+JhtAOadu5yS8X0+NjChTB1AcOsDPNsKAnsWg== Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [2604:1380:45d1:ec00::1]) by mx.google.com with ESMTPS id a19-20020ac85b93000000b0042c0b76d096si171427qta.158.2024.02.06.17.16.09 for <ouuuleilei@gmail.com> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 06 Feb 2024 17:16:09 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-55779-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=gQVmsxkr; arc=pass (i=1 spf=pass spfdomain=ti.com dkim=pass dkdomain=ti.com dmarc=pass fromdomain=ti.com); spf=pass (google.com: domain of linux-kernel+bounces-55779-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-55779-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ny.mirrors.kernel.org (Postfix) with ESMTPS id 242A91C23F6B for <ouuuleilei@gmail.com>; Wed, 7 Feb 2024 01:16:09 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id AED66FBE9; Wed, 7 Feb 2024 01:15:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b="gQVmsxkr" Received: from fllv0015.ext.ti.com (fllv0015.ext.ti.com [198.47.19.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4E5A88F48; Wed, 7 Feb 2024 01:15:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.47.19.141 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707268525; cv=none; b=meeP72FErvplYMxxzRXV1Tjs3F+X2QPz9eO9yj34PdtKB4qrOEmEW467hI6cgiw7ihokxd4Ea01K6Fvlj26mVK4WTeaVaNIXTxKjhbWx47pcCuYb2ji+qDkjFfA3dCiKLVqkn5tptLFx2vSNQrXXnIXHnzq+ya3LUwAhciiG0bw= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707268525; c=relaxed/simple; bh=jb0WADSs8jzHMDJOumcCK5xjY92G5/BQFltArPqFDCU=; h=From:To:CC:Subject:Date:Message-ID:MIME-Version:Content-Type; b=fu4oPRNDUUrLbe4FvrWKW5ZWtXfF1XPmPFaDiBeo/bPmCLmsMiZD2HcJe9FwxA6nPjG8QVIe8UwA+te28nQX0/a0Zvg3iAmjE1g8UVqsDR3v6UzHRLQtSWKv4Oxk9sDPhBvlQmP+0jTBP1LXe+ApLZGsZaj78wqHGUoumlGVVpE= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=ti.com; spf=pass smtp.mailfrom=ti.com; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b=gQVmsxkr; arc=none smtp.client-ip=198.47.19.141 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=ti.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=ti.com Received: from fllv0034.itg.ti.com ([10.64.40.246]) by fllv0015.ext.ti.com (8.15.2/8.15.2) with ESMTP id 4171FKgD053885; Tue, 6 Feb 2024 19:15:20 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1707268520; bh=nLwkfNDASkjCG3CEoS36quV/YANOd685QNozGD7eIdE=; h=From:To:CC:Subject:Date; b=gQVmsxkrPJ0jn9/Va0hRfHlV1T23hZ+X+gKQt/EIQzZ+l5wRzRb6aET49EFfpX6Lr Mk9iteoZ06coQdt22XvkgANmyIsJlSdJufVLqWy6QPIHzY0pXd7uC2rrN6vZ+fTcrC 52F7+Yq1pYi1pE2AcbqzbaRyuIiZEZkFXxHx1CNE= Received: from DFLE100.ent.ti.com (dfle100.ent.ti.com [10.64.6.21]) by fllv0034.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 4171FKA8109412 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 6 Feb 2024 19:15:20 -0600 Received: from DFLE115.ent.ti.com (10.64.6.36) by DFLE100.ent.ti.com (10.64.6.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23; Tue, 6 Feb 2024 19:15:20 -0600 Received: from lelvsmtp5.itg.ti.com (10.180.75.250) by DFLE115.ent.ti.com (10.64.6.36) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23 via Frontend Transport; Tue, 6 Feb 2024 19:15:20 -0600 Received: from judy-hp.dhcp.ti.com (judy-hp.dhcp.ti.com [128.247.81.105]) by lelvsmtp5.itg.ti.com (8.15.2/8.15.2) with ESMTP id 4171FKMo122103; Tue, 6 Feb 2024 19:15:20 -0600 From: Judith Mendez <jm@ti.com> To: Ulf Hansson <ulf.hansson@linaro.org> CC: Adrian Hunter <adrian.hunter@intel.com>, <linux-mmc@vger.kernel.org>, <linux-kernel@vger.kernel.org> Subject: [PATCH v2 0/7] Add tuning algorithm for delay chain Date: Tue, 6 Feb 2024 19:15:13 -0600 Message-ID: <20240207011520.3128382-1-jm@ti.com> X-Mailer: git-send-email 2.43.0 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: <linux-kernel.vger.kernel.org> List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org> List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1790200847513382346 X-GMAIL-MSGID: 1790200847513382346 |
Series |
Add tuning algorithm for delay chain
|
|
Message
Judith Mendez
Feb. 7, 2024, 1:15 a.m. UTC
This patch series introduces a new tuning algorithm for mmc. The new algorithm should be used when delay chain is enabled. The ITAPDLY is selected from the largest passing window and the buffer is not viewed as a circular buffer. The new tuning algorithm is implemented as per the paper published here [0] and has been tested on the following platforms: AM62x SK, AM62A SK, AM62p SK, AM64x SK, and AM64x EVM. The series also includes a few fixes in the sdhci_am654 driver on OTAPDLYEN/ITAPDLYEN and ITAPDELSEL. Changelog: v1->v2: - Remove unnecessary indentations and if/else in sdhci_am654_calculate_itap - Optimize sdhci_am654_calculate_itap() - Call sdhci_am654_write_itapdly() in sdhci_am654_set_clock() instead of sdhci_am654_setup_dll() - Change otap_del_sel[], itap_del_sel[], and itap_del_ena[] to type u32 - Revert unnecessary reformating in sdhci_am654_set_clock() and sdhci_j721e_4bit_set_clock() Judith Mendez (7): mmc: sdhci_am654: Add tuning algorithm for delay chain mmc: sdhci_am654: Write ITAPDLY for DDR52 timing mmc: sdhci_am654: Add missing OTAP/ITAP enable mmc: sdhci_am654: Fix itapdly/otapdly array type mmc: sdhci_am654: Update comments in sdhci_am654_set_clock mmc: sdhci_am654: Add ITAPDLYSEL in sdhci_j721e_4bit_set_clock mmc: sdhci_am654: Fix ITAPDLY for HS400 timing drivers/mmc/host/sdhci_am654.c | 176 ++++++++++++++++++++++++++------- 1 file changed, 138 insertions(+), 38 deletions(-) base-commit: 40d83f40c44ba8aa79cba409ace619db3a7f86f2
Comments
On Tue, Feb 06, 2024 at 07:15:13PM -0600, Judith Mendez wrote: > This patch series introduces a new tuning algorithm for > mmc. The new algorithm should be used when delay chain is > enabled. The ITAPDLY is selected from the largest passing > window and the buffer is not viewed as a circular buffer. > The new tuning algorithm is implemented as per the paper > published here [0] and has been tested on the following Where is this `[0]`? > platforms: AM62x SK, AM62A SK, AM62p SK, AM64x SK, and AM64x > EVM. In the other patches you link some document, but I was not able to find anything related to AM62, can you provide some reference on this specific SOC? Francesco
Hi Francesco, On 2/11/24 10:02 AM, Francesco Dolcini wrote: > On Tue, Feb 06, 2024 at 07:15:13PM -0600, Judith Mendez wrote: >> This patch series introduces a new tuning algorithm for >> mmc. The new algorithm should be used when delay chain is >> enabled. The ITAPDLY is selected from the largest passing >> window and the buffer is not viewed as a circular buffer. >> The new tuning algorithm is implemented as per the paper >> published here [0] and has been tested on the following > > Where is this `[0]`? I must have missed linking the ref doc here, will add in next iteration, thanks. > >> platforms: AM62x SK, AM62A SK, AM62p SK, AM64x SK, and AM64x >> EVM. > > In the other patches you link some document, but I was not able to find > anything related to AM62, can you provide some reference on this > specific SOC? This patch series fixes issues that affect all Sitara SoCs, not only AM62x. However, I could use AM62x for reference, no problem. > > Francesco > ~ Judith
Hi Judith, On Mon, Feb 12, 2024 at 10:33:35AM -0600, Judith Mendez wrote: > Hi Francesco, > > On 2/11/24 10:02 AM, Francesco Dolcini wrote: > > On Tue, Feb 06, 2024 at 07:15:13PM -0600, Judith Mendez wrote: > > > This patch series introduces a new tuning algorithm for > > > mmc. The new algorithm should be used when delay chain is > > > enabled. The ITAPDLY is selected from the largest passing > > > window and the buffer is not viewed as a circular buffer. > > > The new tuning algorithm is implemented as per the paper > > > published here [0] and has been tested on the following > > > > Where is this `[0]`? > > I must have missed linking the ref doc here, will add in next > iteration, thanks. > > > > > > platforms: AM62x SK, AM62A SK, AM62p SK, AM64x SK, and AM64x > > > EVM. > > > > In the other patches you link some document, but I was not able to find > > anything related to AM62, can you provide some reference on this > > specific SOC? > > This patch series fixes issues that affect all Sitara SoCs, not only > AM62x. However, I could use AM62x for reference, no problem. I am really looking for documentation here that is related to the AM62 because I was not able to find anything and this is a topic of interest for me. Can you share something? Francesco
Hi Francesco, On 2/12/24 11:32 AM, Francesco Dolcini wrote: > Hi Judith, > > On Mon, Feb 12, 2024 at 10:33:35AM -0600, Judith Mendez wrote: >> Hi Francesco, >> >> On 2/11/24 10:02 AM, Francesco Dolcini wrote: >>> On Tue, Feb 06, 2024 at 07:15:13PM -0600, Judith Mendez wrote: >>>> This patch series introduces a new tuning algorithm for >>>> mmc. The new algorithm should be used when delay chain is >>>> enabled. The ITAPDLY is selected from the largest passing >>>> window and the buffer is not viewed as a circular buffer. >>>> The new tuning algorithm is implemented as per the paper >>>> published here [0] and has been tested on the following >>> >>> Where is this `[0]`? >> >> I must have missed linking the ref doc here, will add in next >> iteration, thanks. >> >>> >>>> platforms: AM62x SK, AM62A SK, AM62p SK, AM64x SK, and AM64x >>>> EVM. >>> >>> In the other patches you link some document, but I was not able to find >>> anything related to AM62, can you provide some reference on this >>> specific SOC? >> >> This patch series fixes issues that affect all Sitara SoCs, not only >> AM62x. However, I could use AM62x for reference, no problem. > > I am really looking for documentation here that is related to the AM62 > because I was not able to find anything and this is a topic of interest > for me. > The AM62x device datasheet: https://www.ti.com/lit/ds/symlink/am625.pdf, reference Table 7-79 for MMC0 and Table 7-97 for MMC1. TRM, reference section 12.4.5 for MMCSD and section 12.4.5.5.2.3.2 Tuning Sequence that we currently implement in the sdhci_am654 driver. Section 14.8.4.6 for MMCSD registers, SS_CFG_PHY_CTRL_1, SS_CFG_PHY_CTRL_5, and SS_CFG_PHY_CTRL_5 are usually of higher interest. Tuning algorithm, reference: https://www.ti.com/lit/an/spract9/spract9.pdf which is applicable for AM62x, DLL is not applicable for AM62x, so the tuning algorithm should not consider the buffer as a circular buffer. ~ Judith > Can you share something? > > Francesco >