From patchwork Mon Sep 9 12:16:04 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Felipe Balbi X-Patchwork-Id: 11137783 Return-Path: Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org [172.30.200.123]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id E458F1599 for ; Mon, 9 Sep 2019 12:16:10 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id CC51C206A5 for ; Mon, 9 Sep 2019 12:16:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2404805AbfIIMQK (ORCPT ); Mon, 9 Sep 2019 08:16:10 -0400 Received: from mga17.intel.com ([192.55.52.151]:22495 "EHLO mga17.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404804AbfIIMQK (ORCPT ); Mon, 9 Sep 2019 08:16:10 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Sep 2019 05:16:09 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,484,1559545200"; d="scan'208";a="268056052" Received: from pipin.fi.intel.com ([10.237.72.175]) by orsmga001.jf.intel.com with ESMTP; 09 Sep 2019 05:16:07 -0700 From: Felipe Balbi To: Jonathan Cameron Cc: Hartmut Knaack , Lars-Peter Clausen , Peter Meerwald-Stadler , linux-iio@vger.kernel.org, Felipe Balbi Subject: [RFC/PATCH 0/1] Quadrature Encoder Support Date: Mon, 9 Sep 2019 15:16:04 +0300 Message-Id: <20190909121605.92008-1-felipe.balbi@linux.intel.com> X-Mailer: git-send-email 2.23.0 MIME-Version: 1.0 Sender: linux-iio-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-iio@vger.kernel.org Hi, Here's a simple RFC for Intel's Quadrature Encoder. Let me make it clear that I don't mean we should the following patch as is, rather I'd like to open the discussion to, perhaps, extending Industrial Automation Framework with support for Quadrature Encoders. Let me know if you think IIO would be correct place for such devices, then I can start reworking the driver to provide an IIO-compliant interface. I'm thinking we would need standard sysfs files for configuring the QEP into single-shot QEP mode or buffered Capture mode, configure thresholds and other details. Cheers Felipe Balbi (1): misc: introduce intel QEP drivers/misc/Kconfig | 7 + drivers/misc/Makefile | 1 + drivers/misc/intel-qep.c | 813 +++++++++++++++++++++++++++++++++++++++ 3 files changed, 821 insertions(+) create mode 100644 drivers/misc/intel-qep.c