Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3311548imu; Mon, 19 Nov 2018 14:01:08 -0800 (PST) X-Google-Smtp-Source: AJdET5es1fJedqcRTWWcsHza/sroBKTMD9Ca637U0eQqxboqewPMwqNZjInZqw5zv849Bnr3n15N X-Received: by 2002:a17:902:b282:: with SMTP id u2mr24478529plr.89.1542664868057; Mon, 19 Nov 2018 14:01:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542664868; cv=none; d=google.com; s=arc-20160816; b=FbOblyNAQ1YQYqRG1e9MRCrZA3yqx+AGajHZ7ClSvvvw5Ovsg7ttxaSh/69nkiMD/x sHWH6ElFohBKBSS/S+7qxoNOsaEckPM/Z7WtT3WZg3NX+jvNvlwAeydBNU0kawriS5Qy CJFutyzd6Hi7hQqMMA6xhnd47iDZ357T6c/Q4uzCaRNKg5sVyhWuoUcaTriYY2fFBY57 YvA1LPLtAVYmO1SduhIXyaHoAQdVaNREvIKOWB+X6HCYCMXETU+n2bUcl3KWb77TZOZ/ QaAYbufCEH97VOvm/308EiZEg3/4NRlA1/Df4UaC4NXKVq+wJ8sRpTjoujzw2o5HQURf njnA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:dkim-signature:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=MzBx2B/Yx+7wJ0B97M+RZbJ6wstQhmoG2oBl6Gnj+Xs=; b=f26JQCnV7GlplqxZVZ687kQaj+PSrJr7QjKul+tfZ5tYrwy9ggdnDt7lxfl9ycVMre B1Clmb+kLxWNqRf+dgdDeL5No0r9uOgC17xQsykf5+TZP2b6D4a1qwWoqaUv54PX6exf eGNTfXYtqA5MfKzQZytvzNia8FT0OuXmca70HNIL4B4Xp1W0eE8u2wmjoF9szEe/dRu+ 0QF59Yw6lgwnDqZiYDnLtmEdyvMUsMHc78VN5vFgxMSucUeN+kqu6yE45GevwLPwlxhH eEezAJqk96zQneRZi/DftUaKzvxdwY8KLDlH7dmHKmo81MQf4Ibh4vMBB+YFTYngRuaf 0lGw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=guftr7tn; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l7si8313825pfg.245.2018.11.19.14.00.52; Mon, 19 Nov 2018 14:01:08 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=guftr7tn; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731357AbeKTIZ7 (ORCPT + 99 others); Tue, 20 Nov 2018 03:25:59 -0500 Received: from hqemgate16.nvidia.com ([216.228.121.65]:1619 "EHLO hqemgate16.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730482AbeKTIZ7 (ORCPT ); Tue, 20 Nov 2018 03:25:59 -0500 Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqemgate16.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Mon, 19 Nov 2018 14:00:25 -0800 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate101.nvidia.com (PGP Universal service); Mon, 19 Nov 2018 14:00:16 -0800 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Mon, 19 Nov 2018 14:00:16 -0800 Received: from [10.26.11.92] (172.20.13.39) by HQMAIL101.nvidia.com (172.20.187.10) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 19 Nov 2018 22:00:14 +0000 Subject: Re: [PATCH v1 4/4] ARM: tegra: Clear EMC interrupts on resume from LP1 on Tegra30+ To: Dmitry Osipenko , Thierry Reding , Peter De Schrijver CC: , References: <20180830185404.7224-1-digetx@gmail.com> <20180830185404.7224-5-digetx@gmail.com> From: Jon Hunter Message-ID: <9c085248-41df-c8be-294d-6bf8b95c1085@nvidia.com> Date: Mon, 19 Nov 2018 22:00:12 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <20180830185404.7224-5-digetx@gmail.com> X-Originating-IP: [172.20.13.39] X-ClientProxiedBy: HQMAIL103.nvidia.com (172.20.187.11) To HQMAIL101.nvidia.com (172.20.187.10) Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1542664825; bh=MzBx2B/Yx+7wJ0B97M+RZbJ6wstQhmoG2oBl6Gnj+Xs=; h=X-PGP-Universal:Subject:To:CC:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:X-Originating-IP: X-ClientProxiedBy:Content-Type:Content-Language: Content-Transfer-Encoding; b=guftr7tnIea3OAUUjK7ZheVsMlex6UsJh+3ML+mysdho/wqME5P/5Mbh7MYUPK/Wk aJ2v3eeekWi3tbSFIfAaGX8vvGTnHLt6RtmOCJE7nYaCs3kjLIkH0TRmzyfqZfAhVU 7MdHTjb3aCR3GlciFdoRu8QlMEld/nQHA920gJ+iXl3NcFrZw5T6msERD2BJ/RwsJ1 2AzUJmqSWLQ8vDSjOYlSiXHLkHQGq2WYmnwqEWLvmaXlcT0dvjxK9vm+o8emRc7rol yIqazTX0kTKXMo1gemlLTUDENINvbNJFp4KrofQ6jx2t2Zr77mxxYHc2wk5GWEUafr KWzEqSAyGph3A== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 30/08/2018 19:54, Dmitry Osipenko wrote: > Two interrupts are raised on resume from LP1 on Tegra30+: first is the > clock change completed interrupt which is set after updating timing > configuration, second is DLL alarm interrupt which is set when DLL > starts re-calibration after being reset. Clear these two interrupts > in the end of exiting from the self-refresh mode for consistency, that > will also allow to not receive spurious interrupts in the EMC driver > after resume from suspend. > > Signed-off-by: Dmitry Osipenko > --- > arch/arm/mach-tegra/sleep-tegra30.S | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/arch/arm/mach-tegra/sleep-tegra30.S b/arch/arm/mach-tegra/sleep-tegra30.S > index 828f6c37afde..78c6e9fb56e7 100644 > --- a/arch/arm/mach-tegra/sleep-tegra30.S > +++ b/arch/arm/mach-tegra/sleep-tegra30.S > @@ -26,6 +26,7 @@ > #include "irammap.h" > #include "sleep.h" > > +#define EMC_INTSTATUS 0x0 > #define EMC_CFG 0xc > #define EMC_ADR_CFG 0x10 > #define EMC_TIMING_CONTROL 0x28 > @@ -44,6 +45,9 @@ > #define EMC_XM2VTTGENPADCTRL 0x310 > #define EMC_XM2VTTGENPADCTRL2 0x314 > > +#define EMC_CLKCHANGE_COMPLETE_INT (1 << 4) > +#define EMC_DLL_ALARM_INT (1 << 7) > + > #define MC_EMEM_ARB_CFG 0x90 > > #define PMC_CTRL 0x0 > @@ -539,6 +543,9 @@ zcal_done: > > emc_timing_update r1, r0 > > + mov r1, #(EMC_CLKCHANGE_COMPLETE_INT | EMC_DLL_ALARM_INT) > + str r1, [r0, #EMC_INTSTATUS] @ clear interrupts > + > /* Tegra114 had dual EMC channel, now config the other one */ > cmp r10, #TEGRA114 > bne __no_dual_emc_chanl > Where are these interrupts enabled? I did not see where they are enabled. I see that the Tegra24 EMC driver does poll these, but it did not look like they were enabled. If they are enabled, I wondering if they should be masked on entering self-refresh? Cheers Jon -- nvpublic