Message ID | 20240207011520.3128382-3-jm@ti.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel+bounces-55784-ouuuleilei=gmail.com@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:7301:168b:b0:106:860b:bbdd with SMTP id ma11csp1929739dyb; Tue, 6 Feb 2024 17:17:26 -0800 (PST) X-Google-Smtp-Source: AGHT+IF88rt8trn6kvEqa4hSpIInKDJM1IycRQIplG2NRlweU8aiPE7NgRqmv26rzEI/YaMJHBwN X-Received: by 2002:ae9:c118:0:b0:785:86e0:c3fc with SMTP id z24-20020ae9c118000000b0078586e0c3fcmr4753594qki.5.1707268646037; Tue, 06 Feb 2024 17:17:26 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1707268646; cv=pass; d=google.com; s=arc-20160816; b=tEgXGCbqUhsE0QB6rywF9b4oQUQPEvuA0sTsmYSjY3RVzEcOAZBKTd8UC6gny5puzE hbyKKTvuIdejgmb6n2sTnD49dUBpxKQNhrCuT11dKUVzkv1G/tmeIKfPsLHRTYPvUGvx DBU30abVytRkKZxg45YuK2imyQYudeuz0ZUhQ23k6OX6o+jn2mm1p7W+cB77kPysWfVu Uuxehkp3+kpSatbENgvfb3AG2C9dv7nNnwVPILYe1s8Ppx6fhdAPj+M55F0RMb15Oykr LWzlGhukn57eyumTqAnaWvsHAKLhHb/+FwPfSTDW170xH8xw4nle4/Lk303LBsP1r0yt 6aQQ== 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:references:in-reply-to:message-id :date:subject:cc:to:from:dkim-signature; bh=ixLIn8/4MEod1tNhTGI8xmWaSLqcdeGvGzPBaoWSn1w=; fh=O2gflyduimQTVhdQecHwihnMH1RWWX5xrMmkMMLJp64=; b=cHyFxpElQmn4c2dqkODetD/ZzmPxduiQBVyNZN78u1/5BiICFL4iLJSsMRU41AOQ2e UDHVyqSnXh7zOWwUEcIORyZIeNA3EiQ49LramPpGiKj3fbZcIEG5swj1P5fDG/JTc/P8 X0PAEEZyqL0tB0Y1E8FyK8MrsrazCgCgMMltUJIJwc8cuG1MX5E8EJvwo9iRwHf73F9B 4sEyu8x2+BHfZJcwiPFHcyMSmVze3jVNMAfXaruodKsLEA2uca/840BLaN1B/HGuUf7K T1uqaC1M2gqe/GNzq6QJnsh1N6pKoKVfYdx3e2VCVLc1bMKTFZFTslVhCep9Po1Z6WSt slvg==; dara=google.com ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=qREzwEmJ; 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-55784-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-55784-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com X-Forwarded-Encrypted: i=2; AJvYcCXRYW0flwn/e40D1zRsySsPGTnHbkL2PxAYJmW4edI8bOJ7jAqnqbHbuzmRoho2OPM1lBUunBOqJaYi3tCPsdbfdEGVEA== Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [2604:1380:45d1:ec00::1]) by mx.google.com with ESMTPS id h21-20020a05620a21d500b00783edb7414bsi147301qka.149.2024.02.06.17.17.25 for <ouuuleilei@gmail.com> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 06 Feb 2024 17:17:26 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-55784-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=qREzwEmJ; 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-55784-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-55784-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 D06241C2398E for <ouuuleilei@gmail.com>; Wed, 7 Feb 2024 01:17:25 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id F1AF01CD3B; Wed, 7 Feb 2024 01:15:32 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b="qREzwEmJ" Received: from fllv0016.ext.ti.com (fllv0016.ext.ti.com [198.47.19.142]) (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 B542910A0D; Wed, 7 Feb 2024 01:15:28 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.47.19.142 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707268530; cv=none; b=hEy6mKYgFWhO061l+l1x+J/fiBbWj7FZ+hUiiIwdat6u3eflf1tWQPKBE/eBGOuc6AI3w7YnXvvh5y2QlXvCKrwwgo0U5RzjFW7OsvMW5cKvc/ZcRPaCNb30Zo1R6oHyzg47uGlBn5zhTScdrVKWCN6j0b7cHdzENzgJvXBVD84= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707268530; c=relaxed/simple; bh=H5Q3ZZyiKSJvEbGy2GJNYOLC//I8vimE87KP0CslkM8=; h=From:To:CC:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=ZNPwpjO9JxWWf19fh+SZrareuJUAbCsu9qAR6YDwAfUceIYtm9rVJULVIPodeQOES2ByYZ/+WF7dpULDg1oyc57qvCLpiescjU3JO2IlWLOhLTRcpT6OlTFf3vSXDZ2/++VhEgWOnJH9ZfTaIPDP1OZMvzCocctlarT/lpGbS5A= 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=qREzwEmJ; arc=none smtp.client-ip=198.47.19.142 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 lelv0266.itg.ti.com ([10.180.67.225]) by fllv0016.ext.ti.com (8.15.2/8.15.2) with ESMTP id 4171FKq9101969; 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=ixLIn8/4MEod1tNhTGI8xmWaSLqcdeGvGzPBaoWSn1w=; h=From:To:CC:Subject:Date:In-Reply-To:References; b=qREzwEmJFsvpIAPNtDJSF+wj00IjO9lqjeeR8aasrWD/i0eSuBbe+ZD0v30Lbjtn/ M9eeWLbL36v3zV2V5ZM2eSlPMGgNOmcd6CbrWEUifx2+G8VtnVmjL8c9vraXwaYEYa ++yFg9uO4cIEdUhkkVA8ZXaxMQPhbKfFK/S22CGs= Received: from DFLE106.ent.ti.com (dfle106.ent.ti.com [10.64.6.27]) by lelv0266.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 4171FKuS114472 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 6 Feb 2024 19:15:20 -0600 Received: from DFLE106.ent.ti.com (10.64.6.27) by DFLE106.ent.ti.com (10.64.6.27) 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 DFLE106.ent.ti.com (10.64.6.27) 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 4171FKMq122103; 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 2/7] mmc: sdhci_am654: Write ITAPDLY for DDR52 timing Date: Tue, 6 Feb 2024 19:15:15 -0600 Message-ID: <20240207011520.3128382-3-jm@ti.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20240207011520.3128382-1-jm@ti.com> References: <20240207011520.3128382-1-jm@ti.com> 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: 1790200927686945180 X-GMAIL-MSGID: 1790200927686945180 |
Series |
Add tuning algorithm for delay chain
|
|
Commit Message
Judith Mendez
Feb. 7, 2024, 1:15 a.m. UTC
For DDR52 timing, DLL is enabled but tuning is not carried
out, therefore the ITAPDLY value in PHY CTRL 4 register is
not correct. Fix this by writing ITAPDLY after enabling DLL.
Fixes: a161c45f2979 ("mmc: sdhci_am654: Enable DLL only for some speed modes")
Signed-off-by: Judith Mendez <jm@ti.com>
---
Changelog:
v1->v2:
- Call sdhci_am654_write_itapdly() in sdhci_am654_set_clock()
instead of sdhci_am654_setup_dll()
---
drivers/mmc/host/sdhci_am654.c | 1 +
1 file changed, 1 insertion(+)
Comments
On 2/6/24 7:15 PM, Judith Mendez wrote: > For DDR52 timing, DLL is enabled but tuning is not carried > out, therefore the ITAPDLY value in PHY CTRL 4 register is > not correct. Fix this by writing ITAPDLY after enabling DLL. > > Fixes: a161c45f2979 ("mmc: sdhci_am654: Enable DLL only for some speed modes") > Signed-off-by: Judith Mendez <jm@ti.com> > --- > Changelog: > v1->v2: > - Call sdhci_am654_write_itapdly() in sdhci_am654_set_clock() > instead of sdhci_am654_setup_dll() > --- > drivers/mmc/host/sdhci_am654.c | 1 + > 1 file changed, 1 insertion(+) See how much easier this patch is this way :) Reviewed-by: Andrew Davis <afd@ti.com> > > diff --git a/drivers/mmc/host/sdhci_am654.c b/drivers/mmc/host/sdhci_am654.c > index 2c66a965c225..b50db5d4a452 100644 > --- a/drivers/mmc/host/sdhci_am654.c > +++ b/drivers/mmc/host/sdhci_am654.c > @@ -299,6 +299,7 @@ static void sdhci_am654_set_clock(struct sdhci_host *host, unsigned int clock) > > if (timing > MMC_TIMING_UHS_SDR25 && clock >= CLOCK_TOO_SLOW_HZ) { > sdhci_am654_setup_dll(host, clock); > + sdhci_am654_write_itapdly(sdhci_am654, sdhci_am654->itap_del_sel[timing]); > sdhci_am654->dll_enable = true; > } else { > sdhci_am654_setup_delay_chain(sdhci_am654, timing);
Hi Andrew, On 2/12/24 11:13 AM, Andrew Davis wrote: > On 2/6/24 7:15 PM, Judith Mendez wrote: >> For DDR52 timing, DLL is enabled but tuning is not carried >> out, therefore the ITAPDLY value in PHY CTRL 4 register is >> not correct. Fix this by writing ITAPDLY after enabling DLL. >> >> Fixes: a161c45f2979 ("mmc: sdhci_am654: Enable DLL only for some speed >> modes") >> Signed-off-by: Judith Mendez <jm@ti.com> >> --- >> Changelog: >> v1->v2: >> - Call sdhci_am654_write_itapdly() in sdhci_am654_set_clock() >> instead of sdhci_am654_setup_dll() >> --- >> drivers/mmc/host/sdhci_am654.c | 1 + >> 1 file changed, 1 insertion(+) > > See how much easier this patch is this way :) Thanks for your review. :D It does look simpler. > > Reviewed-by: Andrew Davis <afd@ti.com> > >> >> diff --git a/drivers/mmc/host/sdhci_am654.c >> b/drivers/mmc/host/sdhci_am654.c >> index 2c66a965c225..b50db5d4a452 100644 >> --- a/drivers/mmc/host/sdhci_am654.c >> +++ b/drivers/mmc/host/sdhci_am654.c >> @@ -299,6 +299,7 @@ static void sdhci_am654_set_clock(struct >> sdhci_host *host, unsigned int clock) >> if (timing > MMC_TIMING_UHS_SDR25 && clock >= CLOCK_TOO_SLOW_HZ) { >> sdhci_am654_setup_dll(host, clock); >> + sdhci_am654_write_itapdly(sdhci_am654, >> sdhci_am654->itap_del_sel[timing]); >> sdhci_am654->dll_enable = true; >> } else { >> sdhci_am654_setup_delay_chain(sdhci_am654, timing);
On 7/02/24 03:15, Judith Mendez wrote: > For DDR52 timing, DLL is enabled but tuning is not carried > out, therefore the ITAPDLY value in PHY CTRL 4 register is > not correct. Fix this by writing ITAPDLY after enabling DLL. > > Fixes: a161c45f2979 ("mmc: sdhci_am654: Enable DLL only for some speed modes") Note that the Fixes tags make a different ordering than the patch order i.e. Patch Fixes in version 1 13ebeae68ac9 v5.10-rc1 2 a161c45f2979 v5.7-rc1 3 8ee5fc0e0b3b v5.7-rc1 4 8ee5fc0e0b3b v5.7-rc1 4 a0a62497f6aa v5.10-rc1 5 fe52e2fbc6ef v5.9-rc1 6 1accbced1c32 v5.3-rc1 7 a161c45f2979 v5.7-rc1 That might make backporting these patches more challenging. > Signed-off-by: Judith Mendez <jm@ti.com> > --- > Changelog: > v1->v2: > - Call sdhci_am654_write_itapdly() in sdhci_am654_set_clock() > instead of sdhci_am654_setup_dll() > --- > drivers/mmc/host/sdhci_am654.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/mmc/host/sdhci_am654.c b/drivers/mmc/host/sdhci_am654.c > index 2c66a965c225..b50db5d4a452 100644 > --- a/drivers/mmc/host/sdhci_am654.c > +++ b/drivers/mmc/host/sdhci_am654.c > @@ -299,6 +299,7 @@ static void sdhci_am654_set_clock(struct sdhci_host *host, unsigned int clock) > > if (timing > MMC_TIMING_UHS_SDR25 && clock >= CLOCK_TOO_SLOW_HZ) { > sdhci_am654_setup_dll(host, clock); > + sdhci_am654_write_itapdly(sdhci_am654, sdhci_am654->itap_del_sel[timing]); > sdhci_am654->dll_enable = true; > } else { > sdhci_am654_setup_delay_chain(sdhci_am654, timing);
Hi Adrian, On 2/16/24 11:09 AM, Adrian Hunter wrote: > On 7/02/24 03:15, Judith Mendez wrote: >> For DDR52 timing, DLL is enabled but tuning is not carried >> out, therefore the ITAPDLY value in PHY CTRL 4 register is >> not correct. Fix this by writing ITAPDLY after enabling DLL. >> >> Fixes: a161c45f2979 ("mmc: sdhci_am654: Enable DLL only for some speed modes") > > Note that the Fixes tags make a different ordering > than the patch order i.e. > > Patch Fixes in version > 1 13ebeae68ac9 v5.10-rc1 > 2 a161c45f2979 v5.7-rc1 > 3 8ee5fc0e0b3b v5.7-rc1 > 4 8ee5fc0e0b3b v5.7-rc1 > 4 a0a62497f6aa v5.10-rc1 > 5 fe52e2fbc6ef v5.9-rc1 > 6 1accbced1c32 v5.3-rc1 > 7 a161c45f2979 v5.7-rc1 > > That might make backporting these patches more challenging. Are you suggesting to remove the fixes tag here? > >> Signed-off-by: Judith Mendez <jm@ti.com> >> --- >> Changelog: >> v1->v2: >> - Call sdhci_am654_write_itapdly() in sdhci_am654_set_clock() >> instead of sdhci_am654_setup_dll() >> --- >> drivers/mmc/host/sdhci_am654.c | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/drivers/mmc/host/sdhci_am654.c b/drivers/mmc/host/sdhci_am654.c >> index 2c66a965c225..b50db5d4a452 100644 >> --- a/drivers/mmc/host/sdhci_am654.c >> +++ b/drivers/mmc/host/sdhci_am654.c >> @@ -299,6 +299,7 @@ static void sdhci_am654_set_clock(struct sdhci_host *host, unsigned int clock) >> >> if (timing > MMC_TIMING_UHS_SDR25 && clock >= CLOCK_TOO_SLOW_HZ) { >> sdhci_am654_setup_dll(host, clock); >> + sdhci_am654_write_itapdly(sdhci_am654, sdhci_am654->itap_del_sel[timing]); >> sdhci_am654->dll_enable = true; >> } else { >> sdhci_am654_setup_delay_chain(sdhci_am654, timing); > ~ Judith
On 20/02/24 23:05, Judith Mendez wrote: > Hi Adrian, > > On 2/16/24 11:09 AM, Adrian Hunter wrote: >> On 7/02/24 03:15, Judith Mendez wrote: >>> For DDR52 timing, DLL is enabled but tuning is not carried >>> out, therefore the ITAPDLY value in PHY CTRL 4 register is >>> not correct. Fix this by writing ITAPDLY after enabling DLL. >>> >>> Fixes: a161c45f2979 ("mmc: sdhci_am654: Enable DLL only for some speed modes") >> >> Note that the Fixes tags make a different ordering >> than the patch order i.e. >> >> Patch Fixes in version >> 1 13ebeae68ac9 v5.10-rc1 >> 2 a161c45f2979 v5.7-rc1 >> 3 8ee5fc0e0b3b v5.7-rc1 >> 4 8ee5fc0e0b3b v5.7-rc1 >> 4 a0a62497f6aa v5.10-rc1 >> 5 fe52e2fbc6ef v5.9-rc1 >> 6 1accbced1c32 v5.3-rc1 >> 7 a161c45f2979 v5.7-rc1 >> >> That might make backporting these patches more challenging. > > Are you suggesting to remove the fixes tag here? No, it is just something to think about if you intend to backport these patches to older kernels. > >> >>> Signed-off-by: Judith Mendez <jm@ti.com> >>> --- >>> Changelog: >>> v1->v2: >>> - Call sdhci_am654_write_itapdly() in sdhci_am654_set_clock() >>> instead of sdhci_am654_setup_dll() >>> --- >>> drivers/mmc/host/sdhci_am654.c | 1 + >>> 1 file changed, 1 insertion(+) >>> >>> diff --git a/drivers/mmc/host/sdhci_am654.c b/drivers/mmc/host/sdhci_am654.c >>> index 2c66a965c225..b50db5d4a452 100644 >>> --- a/drivers/mmc/host/sdhci_am654.c >>> +++ b/drivers/mmc/host/sdhci_am654.c >>> @@ -299,6 +299,7 @@ static void sdhci_am654_set_clock(struct sdhci_host *host, unsigned int clock) >>> if (timing > MMC_TIMING_UHS_SDR25 && clock >= CLOCK_TOO_SLOW_HZ) { >>> sdhci_am654_setup_dll(host, clock); >>> + sdhci_am654_write_itapdly(sdhci_am654, sdhci_am654->itap_del_sel[timing]); >>> sdhci_am654->dll_enable = true; >>> } else { >>> sdhci_am654_setup_delay_chain(sdhci_am654, timing); >> > > ~ Judith
Hi Adrian, On 2/28/24 7:21 AM, Adrian Hunter wrote: > On 20/02/24 23:05, Judith Mendez wrote: >> Hi Adrian, >> >> On 2/16/24 11:09 AM, Adrian Hunter wrote: >>> On 7/02/24 03:15, Judith Mendez wrote: >>>> For DDR52 timing, DLL is enabled but tuning is not carried >>>> out, therefore the ITAPDLY value in PHY CTRL 4 register is >>>> not correct. Fix this by writing ITAPDLY after enabling DLL. >>>> >>>> Fixes: a161c45f2979 ("mmc: sdhci_am654: Enable DLL only for some speed modes") >>> >>> Note that the Fixes tags make a different ordering >>> than the patch order i.e. >>> >>> Patch Fixes in version >>> 1 13ebeae68ac9 v5.10-rc1 >>> 2 a161c45f2979 v5.7-rc1 >>> 3 8ee5fc0e0b3b v5.7-rc1 >>> 4 8ee5fc0e0b3b v5.7-rc1 >>> 4 a0a62497f6aa v5.10-rc1 >>> 5 fe52e2fbc6ef v5.9-rc1 >>> 6 1accbced1c32 v5.3-rc1 >>> 7 a161c45f2979 v5.7-rc1 >>> >>> That might make backporting these patches more challenging. >> >> Are you suggesting to remove the fixes tag here? > > No, it is just something to think about if you intend to > backport these patches to older kernels. Thanks, Ill keep this in mind for v3. > >> >>> >>>> Signed-off-by: Judith Mendez <jm@ti.com> >>>> --- >>>> Changelog: >>>> v1->v2: >>>> - Call sdhci_am654_write_itapdly() in sdhci_am654_set_clock() >>>> instead of sdhci_am654_setup_dll() >>>> --- >>>> drivers/mmc/host/sdhci_am654.c | 1 + >>>> 1 file changed, 1 insertion(+) >>>> >>>> diff --git a/drivers/mmc/host/sdhci_am654.c b/drivers/mmc/host/sdhci_am654.c >>>> index 2c66a965c225..b50db5d4a452 100644 >>>> --- a/drivers/mmc/host/sdhci_am654.c >>>> +++ b/drivers/mmc/host/sdhci_am654.c >>>> @@ -299,6 +299,7 @@ static void sdhci_am654_set_clock(struct sdhci_host *host, unsigned int clock) >>>> if (timing > MMC_TIMING_UHS_SDR25 && clock >= CLOCK_TOO_SLOW_HZ) { >>>> sdhci_am654_setup_dll(host, clock); >>>> + sdhci_am654_write_itapdly(sdhci_am654, sdhci_am654->itap_del_sel[timing]); >>>> sdhci_am654->dll_enable = true; >>>> } else { >>>> sdhci_am654_setup_delay_chain(sdhci_am654, timing); >>> >> >> ~ Judith >
diff --git a/drivers/mmc/host/sdhci_am654.c b/drivers/mmc/host/sdhci_am654.c index 2c66a965c225..b50db5d4a452 100644 --- a/drivers/mmc/host/sdhci_am654.c +++ b/drivers/mmc/host/sdhci_am654.c @@ -299,6 +299,7 @@ static void sdhci_am654_set_clock(struct sdhci_host *host, unsigned int clock) if (timing > MMC_TIMING_UHS_SDR25 && clock >= CLOCK_TOO_SLOW_HZ) { sdhci_am654_setup_dll(host, clock); + sdhci_am654_write_itapdly(sdhci_am654, sdhci_am654->itap_del_sel[timing]); sdhci_am654->dll_enable = true; } else { sdhci_am654_setup_delay_chain(sdhci_am654, timing);