From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 87C9FC7618F for ; Thu, 18 Jul 2019 19:50:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4D8EE208C0 for ; Thu, 18 Jul 2019 19:50:59 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b="o7Q3/nGx" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391463AbfGRTu6 (ORCPT ); Thu, 18 Jul 2019 15:50:58 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:50896 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727687AbfGRTu6 (ORCPT ); Thu, 18 Jul 2019 15:50:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=f9NYi/JQfKwrckhrLZX09z+ipOmqXvg6F6g6rgIJULA=; b=o7Q3/nGx8gD9nw1+QVSQHD+BN0 aS19BJWloHnqgRVYcSmom4PtMuEC/oKOSQ3KSuS+O1q40bf00gKUYX3jJobXFIuZkAXz737PUgUe1 /2Gxr0z8XPBCJ4q7UfzuDy43NiHl9lMKXirYYQAmooWOQtLYZMrEvJUWR/O9LvzimYPw=; Received: from andrew by vps0.lunn.ch with local (Exim 4.89) (envelope-from ) id 1hoCQK-0002w6-Tp; Thu, 18 Jul 2019 21:50:40 +0200 Date: Thu, 18 Jul 2019 21:50:40 +0200 From: Andrew Lunn To: Felipe Balbi Cc: Richard Cochran , netdev@vger.kernel.org, Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H . Peter Anvin" , x86@kernel.org, linux-kernel@vger.kernel.org, "Christopher S . Hall" Subject: Re: [RFC PATCH 0/5] PTP: add support for Intel's TGPIO controller Message-ID: <20190718195040.GL25635@lunn.ch> References: <20190716072038.8408-1-felipe.balbi@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190716072038.8408-1-felipe.balbi@linux.intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 16, 2019 at 10:20:33AM +0300, Felipe Balbi wrote: > TGPIO is a new IP which allows for time synchronization between systems > without any other means of synchronization such as PTP or NTP. The > driver is implemented as part of the PTP framework since its features > covered most of what this controller can do. Hi Felipe Given the name TGPIO, can it also be used for plain old boring GPIO? Does there need to be some sort of mux between GPIO and TGPIO? And an interface into the generic GPIO core? Also, is this always embedded into a SoC? Or could it actually be in a discrete NIC? Thanks Andrew