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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id EEF0FC433EF for ; Fri, 17 Jun 2022 07:22:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233816AbiFQHWW (ORCPT ); Fri, 17 Jun 2022 03:22:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34284 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1380607AbiFQHWT (ORCPT ); Fri, 17 Jun 2022 03:22:19 -0400 Received: from www381.your-server.de (www381.your-server.de [78.46.137.84]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 974FECD for ; Fri, 17 Jun 2022 00:22:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=metafoo.de; s=default2002; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From: References:Cc:To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID; bh=MdsJci63yjz7iu4X0ztALnZ7jW/aMf9CpapWaosDvZM=; b=X7BGxWcnOsIT4YWCtkewzZcKV7 aZYg+/tEzoricuNkIbBcEFCl4jiYBU97q92lxIyCUfGkduERzyr/D3FqaAhRz52vmrNgFREaZB8qC 0qq3MIHuGefjY1jnnSauaHHgQJG2ZYLGp4AL0E22EyvHEqYI2pFWFiJ+7zh5P8MyebivzF1xOAZHY BqShPnzSY0u6nrU2UhkHR6cTHJixo6AkoExr+hYk8fnUVTJMzXQI2+Mnv7I04oa/Cr7E5b50C+ki+ YfWGVjwP508lXBN1WtNmNLagem6pesJBKdgxqXSFxMnJC6WIrjJwfMFkIr5f0xM7BSCcDzw0uFE5Y c7jgkn7A==; Received: from sslproxy05.your-server.de ([78.46.172.2]) by www381.your-server.de with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from ) id 1o26J0-0004lt-CS; Fri, 17 Jun 2022 09:22:10 +0200 Received: from [2001:a61:2a7f:a201:9e5c:8eff:fe01:8578] by sslproxy05.your-server.de with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o26J0-00030f-4y; Fri, 17 Jun 2022 09:22:10 +0200 Message-ID: <44170bf8-5777-e30b-b74d-a6835b1937e2@metafoo.de> Date: Fri, 17 Jun 2022 09:22:09 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: Intel Timed-IO driver in IIO/Counter subsystem Content-Language: en-US To: "N, Pandith" , "linux-iio@vger.kernel.org" Cc: "vilhelm.gray@gmail.com" , "jic23@kernel.org" , "Shevchenko, Andriy" , "Hall, Christopher S" , "Sangannavar, Mallikarjunappa" , "D, Lakshmi Sowjanya" , "T R, Thejesh Reddy" References: From: Lars-Peter Clausen In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-Sender: lars@metafoo.de X-Virus-Scanned: Clear (ClamAV 0.103.6/26574/Thu Jun 16 10:06:40 2022) Precedence: bulk List-ID: X-Mailing-List: linux-iio@vger.kernel.org On 6/17/22 08:37, N, Pandith wrote: > Hi, > > We have a Intel Timed IO peripheral with following functionalities : > > 1. Event capture capability - Captures event count and timestamp. > 2. Pulse generation - periodic or single event generation. > 3. Return cross-timestamp on request. > > Timed IO device is being used in various Industrial use cases such as : time capture, synchronization, fan speed calculation etc. > > IIO or counter subsystem seems to be suitable for timed-io driver. > > Is it favourable to implement as part of IIO or counter subsystem ? Wanted to know your feedback. That sounds like a mix of a counter and PPS device. Have you looked at the PPS subsystem[1]? [1] https://www.kernel.org/doc/html/latest/driver-api/pps.html