From patchwork Fri Aug 18 16:57:48 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: marius.cristea@microchip.com X-Patchwork-Id: 13358069 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 1A813C71159 for ; Fri, 18 Aug 2023 16:58:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1378841AbjHRQ6Q (ORCPT ); Fri, 18 Aug 2023 12:58:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53542 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1378891AbjHRQ6C (ORCPT ); Fri, 18 Aug 2023 12:58:02 -0400 Received: from esa.microchip.iphmx.com (esa.microchip.iphmx.com [68.232.153.233]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D4B6C3C3F; Fri, 18 Aug 2023 09:57:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=microchip.com; i=@microchip.com; q=dns/txt; s=mchp; t=1692377877; x=1723913877; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=tYP9zSg0rueRu76BbY3YrCv6Yjv7OvHqs7Z8XMR1gAU=; b=f/BIbdwOTk+bogM+M6vaCnTyjpiing8iyJ376Dm2tuhM/oihiEETsWGI n9y4+PTwtMGVS1S/86C3FrJyqo1gkaNus1kzsxw20GU9GKP3RaOYpuBLW eJ9yqCbcL3kvZWVgbABqN009As/AggwVMo+kLPj4BDE1hOqIaljxgeHtr eQYJqZ7m+USSV403Ynp30VKNHHPJ0bZ/wI8yYMqk4W+9NcLctdOFFEMof oleQkfm4AjH1IYrr93bFCn0koXO+cTAnFK2aBEhzTzk09BpDcpli3gDk7 uxxH4FGxk7p0hw7lCNHApjKjGZsW3lDJvSltKQXFC2LZJ/BeTzI3Vb8XQ w==; X-IronPort-AV: E=Sophos;i="6.01,183,1684825200"; d="scan'208";a="230584349" X-Amp-Result: SKIPPED(no attachment in message) Received: from unknown (HELO email.microchip.com) ([170.129.1.10]) by esa5.microchip.iphmx.com with ESMTP/TLS/AES256-SHA256; 18 Aug 2023 09:57:56 -0700 Received: from chn-vm-ex02.mchp-main.com (10.10.85.144) by chn-vm-ex04.mchp-main.com (10.10.85.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Fri, 18 Aug 2023 09:57:56 -0700 Received: from marius-VM.mshome.net (10.10.115.15) by chn-vm-ex02.mchp-main.com (10.10.85.144) with Microsoft SMTP Server id 15.1.2507.21 via Frontend Transport; Fri, 18 Aug 2023 09:57:54 -0700 From: To: , , CC: , , , , , Subject: [PATCH v4 0/2] Adding support for Microchip MCP3564 ADC family Date: Fri, 18 Aug 2023 19:57:48 +0300 Message-ID: <20230818165750.55406-1-marius.cristea@microchip.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: linux-iio@vger.kernel.org From: Marius Cristea Adding support for Microchip family of 153.6 ksps, Low-Noise 16/24-Bit Delta-Sigma ADCs with an SPI interface. This driver covers the following part numbers: - MCP3561, MCP3562, MCP3564, MCP3561R, MCP3562R, MCP3564R, - MCP3461, MCP3462, MCP3464, MCP3461R, MCP3462R and MCP3464R. Differences related to previous patch: v3: - fix review comments from v3: - adding label names for channels into the example from the "microchip,mcp3564.yaml" file - update defines names (with _REG and _MASK) - code clean-up - flip logic to cut down on indent in some cases - use "spi_get_device_match_data" instead of "device_get_match_data" - remove some unnecessary _SET functions - change "boost_current" attribute to "boost_current_gain". The attribute is a gain not an absolute value. - change "boost_current_available" attribute to "boost_current_gain_available" - update comment from v3 (to better describe the change) "fallback compatible in device tree to deal with some newer part number" to "stop failing to probe when the chip id is not recognized. In this case a fallback compatible has been used to support a new part number" v3: - fix review comments: - fix and update the device tree bindings - enable "auto_zeroing_ref_enable" attribute only when internal reference is used - remove unused headers - fix comments (kernel-docs) - remove scan_type - replace "extend_name" with read_label - print label for each channel (label could be added into the dt) - add comment to explain the maximum channels numbers - add protection around critical region - stop failing to probe when the chip id is not recognized. In this case a fallback compatible has been used to support a new part number - Open questions: - whether or not to add a spi-mux type of thing to deal with the part number address in case there are multiple devices connected to the same chip select. - discussion related to the "custom property". Last time around a consensus wasn't reached. v2: - fix review comments: - change the device tree bindings - change the ADC channel creation (starting from DT) - use defines, masks and FIELD_PREP() instead of hardcoded values - mode the PGA from Hardware Gain to scale - add a current output channel from burnout current - fix coding style issues - use self-explanatory naming to drop the comment - renumbered the versioning (start with v1 instead of v0) v1: - first version committed to review Marius Cristea (2): dt-bindings: iio: adc: adding MCP3564 ADC iio: adc: adding support for MCP3564 ADC .../ABI/testing/sysfs-bus-iio-adc-mcp3564 | 53 + .../bindings/iio/adc/microchip,mcp3564.yaml | 205 +++ MAINTAINERS | 7 + drivers/iio/adc/Kconfig | 13 + drivers/iio/adc/Makefile | 1 + drivers/iio/adc/mcp3564.c | 1527 +++++++++++++++++ 6 files changed, 1806 insertions(+) create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-adc-mcp3564 create mode 100644 Documentation/devicetree/bindings/iio/adc/microchip,mcp3564.yaml create mode 100644 drivers/iio/adc/mcp3564.c base-commit: 9e66fb52449538406cea43e9f3889c391350e76e