Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp10876726ybi; Thu, 25 Jul 2019 06:26:17 -0700 (PDT) X-Google-Smtp-Source: APXvYqyCXRT2lJjf2ZlMUa8bh/ByOpifY3IL0iiaBmzTVTCUTf1GzHZIHzAjKHgDraHKRS4ihhek X-Received: by 2002:a17:90a:258b:: with SMTP id k11mr88943486pje.110.1564061177787; Thu, 25 Jul 2019 06:26:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564061177; cv=none; d=google.com; s=arc-20160816; b=0FqDSpeaQNU3Ey6mtpPTHlu7Q2L/ppUJZ2n046TwdIOGWCgKXsF7QNy13Sy8THzmUh eniEAuH2YBC7x2PMv/b/M844TPV869yX2PAhX6rltbcicRPtjGevPJqWl0Ug38oXS79y pzRBSDIu8tiKao/3pKuABfkEaRHJboq9LlH9f+KDMK1BtZoWkPU3y+scscMoOS2easqj GuP1BA1Dbqz+5J46v840l6FDODldM7p8xqP5Y2nykG5byWcdD/wuI4Kk5yh8z3kUrFpE JY6TcyC1U6ZUqZRKfxxUdAEPIFLDIQP93oJWtD84BDuBYBMUcz2IWsOdF+cbtscNXb7A +NxA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:dkim-signature:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=re1gXkHl/1j5LvSAnMOpSkyWvMC6pMtSj9wrZeqzjMk=; b=yCFZMJZHB6wFdqL1NU6gvQ0+kcHxQHx5vZFheVM0X9gzkGVU66Pdl0f+BCzTDz+I7j KGXMioS15YNRoVIkMm7yxea/lQGPFI/j95gCW3HQvgrQQ6tv3tsfU2VwJpWIjX/guUCz 9HJEA4TWMz80vt+Wxd3G833Pkz5yInDrvxXtiiq8gAV14qcPKvSv1KNVNXenuY4aLvvF TNMPUOV8Vpg3pFkG9eVuUXLaKi2DkjqLprb3U0Cu1dhhrzSqOA6fgpRmC8LvoCzk1Rch ashyp/INcfTh2O7SL52DrJvSZz1Jop9mPLVibyq+lZNPNAbegga1pXZu+aDYHSSMj/0b y2Xw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=qecibP9F; 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 k22si22656345pfk.90.2019.07.25.06.26.02; Thu, 25 Jul 2019 06:26:17 -0700 (PDT) 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=qecibP9F; 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 S1728096AbfGYKdx (ORCPT + 99 others); Thu, 25 Jul 2019 06:33:53 -0400 Received: from hqemgate16.nvidia.com ([216.228.121.65]:3402 "EHLO hqemgate16.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726366AbfGYKdw (ORCPT ); Thu, 25 Jul 2019 06:33:52 -0400 Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqemgate16.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Thu, 25 Jul 2019 03:33:48 -0700 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate101.nvidia.com (PGP Universal service); Thu, 25 Jul 2019 03:33:51 -0700 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Thu, 25 Jul 2019 03:33:51 -0700 Received: from tbergstrom-lnx.Nvidia.com (172.20.13.39) by HQMAIL107.nvidia.com (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 25 Jul 2019 10:33:50 +0000 Received: by tbergstrom-lnx.Nvidia.com (Postfix, from userid 1000) id 947724286A; Thu, 25 Jul 2019 13:33:48 +0300 (EEST) Date: Thu, 25 Jul 2019 13:33:48 +0300 From: Peter De Schrijver To: Dmitry Osipenko CC: Sowjanya Komatineni , , , , , , , , , , , , , , , , , , , , , Subject: Re: [PATCH V6 01/21] irqchip: tegra: Do not disable COP IRQ during suspend Message-ID: <20190725103348.GN12715@pdeschrijver-desktop.Nvidia.com> References: <1563738060-30213-1-git-send-email-skomatineni@nvidia.com> <1563738060-30213-2-git-send-email-skomatineni@nvidia.com> <20190725095502.GM12715@pdeschrijver-desktop.Nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: X-NVConfidentiality: public User-Agent: Mutt/1.9.4 (2018-02-28) X-Originating-IP: [172.20.13.39] X-ClientProxiedBy: HQMAIL107.nvidia.com (172.20.187.13) To HQMAIL107.nvidia.com (172.20.187.13) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1564050829; bh=re1gXkHl/1j5LvSAnMOpSkyWvMC6pMtSj9wrZeqzjMk=; h=X-PGP-Universal:Date:From:To:CC:Subject:Message-ID:References: MIME-Version:Content-Type:Content-Disposition: Content-Transfer-Encoding:In-Reply-To:X-NVConfidentiality: User-Agent:X-Originating-IP:X-ClientProxiedBy; b=qecibP9FpTzKw1jYg93JvXFfmf40SpZf+/7GvQE2WaqKdfECmsowl8HCfZOJ61XXg Pjh0ti9TDuRfKKTQv6S7MDLjN2eNEayISwICN/gMhYxNGhdEhSRCiYZ1e/t0M1tDsV XVbB88OKNYPXcSaylXi4FIb6oEvQBocDpdXlTtZk4VzbzCO1ZDcFdowDc2zrUAlu4I gdU9OagKKPorCIYLZynYxP1gmUoZ3/NhKV6vDyY3WSHDLfzWawdaP4+z9JKA8DI913 7t12mMhlF+lgpYq2ekg2TOcOn9dDASZ7vCZ53EnZEbtO4cfWvdYqRKUqpiNBbR8hYy Zi9zNfx84qjyQ== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 25, 2019 at 01:05:13PM +0300, Dmitry Osipenko wrote: > 25.07.2019 12:55, Peter De Schrijver =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > On Mon, Jul 22, 2019 at 12:54:51PM +0300, Dmitry Osipenko wrote: > >> > >> All Tegra SoCs support SC7, hence the 'supports_sc7' and the comment > >> doesn't sound correct to me. Something like 'firmware_sc7' should suit > >> better here. > >> > >>> + writel_relaxed(~0ul, ictlr + ICTLR_COP_IER_CLR); > >> > >> Secondly, I'm also not sure why COP interrupts need to be disabled for > >> pre-T210 at all, since COP is unused. This looks to me like it was > >> cut-n-pasted from downstream kernel without a good reason and could be > >> simply removed. > >=20 > > I don't think we can rely on the fact that COP is unused. People can > > write their own code to run on COP. >=20 > 1. Not upstream - doesn't matter. >=20 The code is not part of the kernel, so obviously it's not upstream? > 2. That's not very good if something unknown is running on COP and then > kernel suddenly intervenes, don't you think so? Unless the code was written with this in mind. Peter.