Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp915598ybl; Fri, 31 Jan 2020 10:17:26 -0800 (PST) X-Google-Smtp-Source: APXvYqyDqI5Uvk8ow4gQL0bqNYDxFPflFjVmea7mBtxq177bpqz403Y4JeRAMKyp9h0Ba/t77d2R X-Received: by 2002:a9d:5885:: with SMTP id x5mr8449871otg.132.1580494646095; Fri, 31 Jan 2020 10:17:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1580494646; cv=none; d=google.com; s=arc-20160816; b=GnKvbJkCTg5hJS/DEaidGNglyaymaxoeHckCAsWpvhdRU3CyPjQfvZxLqjNVd7Iyjw lwuGT2LSl3aA3uGFlo1Ex3htrJXPqXL9gXbkv+aREOYXvMlAwL6n3qlgOztP2ELXXCLJ HZlOySQ0q9j7H+0SGtWzoPvx7BgKniP7XAYZpjRBiEhMA0EU3JqBxHMjtHbQyu0txCUX jVpZtAg6aMKIl2P/gKg8x1QDu5WB0lygvDWxg1u5ANh4YrdQQktPQsV7oj43CRF6c772 WMVc9SUOGVt6iSdRqPfTODcY2VxaOdsnW/npypN9aihn6glWu2G/luvkYVcnr6doevF0 2b0w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from; bh=2c05sJqtugt3u7DGu6vM6fYIXXjyi6tztyOtSr92C/g=; b=mMeo5ccnMaBiE2zSQaa1g5mdfu/flU/lMLRXuFfo5KrZgdL+vOmySjKnLB9n4co/SA IeoxMU/nWQAxVpib434Dc9FlsoxkKsiuEgpIrbRL4efNy2ht97IlZXkQMPQ0fQ0DW+G1 BoRGF6YqilucQ4cw9Uvz9jHjOgZ/wUsTLmX8gbM9D0Xj5iO10fFTGowmxdug+ie0gcEr ZSpwHzWBC/e8ffjmcEnbGXpMgzl0YeEimfZ5bByyysa2YrMfkiEekexESC2mczCXQEKy PfC87st97t9EeeYyXKDLOTP8v4SlWxLUhuxBf1bVNDrlCkC+NzLNpZ7kJSKO/nI9QatU 53hw== 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 e1si4790208otr.8.2020.01.31.10.17.13; Fri, 31 Jan 2020 10:17:26 -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; 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 S1726102AbgAaSPJ (ORCPT + 99 others); Fri, 31 Jan 2020 13:15:09 -0500 Received: from Galois.linutronix.de ([193.142.43.55]:56521 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725878AbgAaSPJ (ORCPT ); Fri, 31 Jan 2020 13:15:09 -0500 Received: from 51.26-246-81.adsl-static.isp.belgacom.be ([81.246.26.51] helo=nanos.tec.linutronix.de) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1ixaoh-0003Vm-I0; Fri, 31 Jan 2020 19:14:55 +0100 Received: by nanos.tec.linutronix.de (Postfix, from userid 1000) id 591E0105BDC; Fri, 31 Jan 2020 19:14:49 +0100 (CET) From: Thomas Gleixner To: christopher.s.hall@intel.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com, x86@kernel.org, jacob.e.keller@intel.com, richardcochran@gmail.com, davem@davemloft.net, sean.v.kelley@intel.com Cc: Christopher Hall Subject: Re: [Intel PMC TGPIO Driver 0/5] Add support for Intel PMC Time GPIO Driver with PHC interface changes to support additional H/W Features In-Reply-To: <20191211214852.26317-1-christopher.s.hall@intel.com> References: <20191211214852.26317-1-christopher.s.hall@intel.com> Date: Fri, 31 Jan 2020 19:14:49 +0100 Message-ID: <87eevf4hnq.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org christopher.s.hall@intel.com writes: > From: Christopher Hall > > Upcoming Intel platforms will have Time-Aware GPIO (TGPIO) hardware. > The TGPIO logic is driven by the Always Running Timer (ART) that's > related to TSC using CPUID[15H] (See Intel SDM Invariant > Time-Keeping). > > The ART frequency is not adjustable. In order, to implement output > adjustments an additional edge-timestamp API is added, as well, as > a periodic output frequency adjustment API. Togther, these implement > equivalent functionality to the existing SYS_OFFSET_* and frequency > adjustment APIs. > > The TGPIO hardware doesn't implement interrupts. For TGPIO input, the > output edge-timestamp API is re-used to implement a user-space polling > interface. For periodic input (e.g. PPS) this is fairly efficient, > requiring only a marginally faster poll rate than the input event > frequency. I really have a hard time to understand why this is implemented as part of PTP while you talk about PPS at the same time. Proper information about why this approach was chosen and what that magic device is used for would be really helpful. Thanks, tglx