Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp3404651ybn; Fri, 27 Sep 2019 06:01:10 -0700 (PDT) X-Google-Smtp-Source: APXvYqzE/YfIOLxZ+Y5ew8FHTOe47uQRpckN2ksOsYbmclpNfmKmtZUg0v6PBFDCReI0VzqmuOCW X-Received: by 2002:aa7:c1d4:: with SMTP id d20mr4289341edp.223.1569589269833; Fri, 27 Sep 2019 06:01:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569589269; cv=none; d=google.com; s=arc-20160816; b=kcNbto51mKqxbexbAUl7Mm/7WpQyngvFDdzzyqUFf8bQoGxGS81QJbvpuDgKQEu0WE HOCCuVkXJU8qsCs2UfyjsmJPnNaN1CDXVgX2Q4ZyBj9fyhglLp9Jm12FmXUAM+aP80sH sNg2Db2l+nNgZbbFCl6cewwzV5H+mezXWs6XgrrKbvnQ9AI2yFKUlusf/GMkJ6Qr/hW+ +/E0ak7Xvdd4sO4sptDfr8Ks3Jyp4VT7KuVXIZzLcyIDP6HDkGaq/3rIAk6l59LFtkX/ M+dYgIxVOjDSz75xyluPJMu9q1AXEsOx5zVgTXsoSLQtEE1QY+iG+CRhNq9Dgau8N3SM jA+w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=YaM78ZoFEBST7WODprd3LtxfgU1sHoHCzAVx6hajaEI=; b=L512NWyaaz68iMN50mA29pd3wPiXaZc2/KGVbB4BBEgh9Pr6crdG6CAdmMlch3UTbV gKaTqxApOVRUAx0itcaf/1DygSxnS0qxlICDe/HqWD4AQwdtDL3r1CT/1wgicDKey9B2 OFYuLA3DovO0pgYrsR15kgBbYx/EAtcHUz7Lxtkm562Het/STeOYjqwfeOHI6S/YxxgG 9KHUgECnfXIMtxWJV46UnOUe5fNvnCN7C1aZPkBUhFAsOsdddg1uKXNeOremcBLCV9Aq bBaeU2+lebyLE2mmo9Rfjx/D2tmmFJgqM32cfi5ltFjDrdkKXP+MDghdlOCcAk/dyewM ekbg== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g5si1528906edb.324.2019.09.27.06.00.44; Fri, 27 Sep 2019 06:01:09 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727403AbfI0M7R (ORCPT + 99 others); Fri, 27 Sep 2019 08:59:17 -0400 Received: from foss.arm.com ([217.140.110.172]:51844 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725890AbfI0M7Q (ORCPT ); Fri, 27 Sep 2019 08:59:16 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 49A751000; Fri, 27 Sep 2019 05:59:16 -0700 (PDT) Received: from bogus (e107155-lin.cambridge.arm.com [10.1.196.42]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 10C053F67D; Fri, 27 Sep 2019 05:59:14 -0700 (PDT) Date: Fri, 27 Sep 2019 13:59:12 +0100 From: Sudeep Holla To: Benjamin GAIGNARD Cc: Marc Zyngier , Alexandre TORGUE , "robh+dt@kernel.org" , "mark.rutland@arm.com" , "devicetree@vger.kernel.org" , "linux-stm32@st-md-mailman.stormreply.com" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] ARM: dts: stm32: Enable high resolution timer Message-ID: <20190927125912.GB8704@bogus> References: <20190927084819.645-1-benjamin.gaignard@st.com> <341949c8-7864-5d65-2797-988022724a4c@st.com> <69af57d1-13a9-9e35-78f2-4a0d17bdaf6d@st.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <69af57d1-13a9-9e35-78f2-4a0d17bdaf6d@st.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Sep 27, 2019 at 12:44:55PM +0000, Benjamin GAIGNARD wrote: [...] > > Even in low-power modes this timer is always powered and clocked so it > is working fine. > Is that tested ? I see only cpu_{on,off} available on this platform with PSCI v0.1. Did you add cpu_suspend, idle-states and then gave it a spin ? Or do you have some other idle driver with which this is tested ? Also I don't understand how "always-on" is linked to hrtimer. Always on timers are just selected to be broadcast timer without sacrificing(simply keeping) a cpu to be always active for broadcast purposes. -- Regards, Sudeep