Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp699488ybe; Thu, 19 Sep 2019 02:19:21 -0700 (PDT) X-Google-Smtp-Source: APXvYqzwQcvMZNitNK3R97ACAYa+wMUOuiI6ws0xC36zQNU0kzEIKuaH6RNIpxVpiGWM3mADASjZ X-Received: by 2002:a05:6402:1855:: with SMTP id v21mr13131395edy.242.1568884761383; Thu, 19 Sep 2019 02:19:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568884761; cv=none; d=google.com; s=arc-20160816; b=FX2thBi4g1/W8WMoux9ipeK2/dm93o5CNW/xHK8D273gkAEEyjavXwb14oAd0QSypJ 2iqO1yajKlnZLD8A0enU4OPADqlriPGjzG6okQ1qrVKgRzwhaOrxdRsfpbRTVGX8h1gp vzerWg8lPIJMVynAiquiiRCc7fbVWceuwh/1u0m5xbPeXARdgSMwHZ03e4NGAtGuh0VA 38IFzg02j55jImTEPHn1oOqktcxqFOZinf4PtCblvahgEvZUEfuuvDoYphQxD0Lurf0C MiLXEcysQeUmdFDk/a3JrMvCKelUIUBcCD9J7XmG7V4IhqzOtkhFhoFaOsm5+VK8x8H9 VaIw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=WqrRADtTlcI8SoUaz6eCZpn8fy3GSVE0nreT7C5rtEg=; b=JWNd16B4U4WdX9aN8e0kwE65RM+4O3TH54+4kjn8y7Lg7uzO3EaZofsZmvTU3hCjNg 7qm1H3IIQ73YZBHZj6grn3qLij4xo6HhrWUj/UwP6MiozKEPnvjJtPlNo65G+cTpEv9z 5Jqw9nfQjS0WYt4MW9RsixYvweVaYCLugcXExejSbsUYtqXDd3Z+OEJLRLZWwx9jdIsK tNFQIXePrpcuooA1tTadKBsuAnZ3nertOFnLIWKlho/bGqG8CZnT3rC+1fd8pwKiIwKI HCVhnlq+dSYteExxePer45A0PVDoTwq1nmdqFqyEuw8eP82I0Xjm8Klp2jkTdYxJIsJz UPVg== 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 7si4210755ejz.151.2019.09.19.02.18.57; Thu, 19 Sep 2019 02:19:21 -0700 (PDT) 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 S2388672AbfISJRE (ORCPT + 99 others); Thu, 19 Sep 2019 05:17:04 -0400 Received: from smtp3.goneo.de ([85.220.129.37]:59148 "EHLO smtp3.goneo.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387637AbfISJRE (ORCPT ); Thu, 19 Sep 2019 05:17:04 -0400 Received: from localhost (localhost [127.0.0.1]) by smtp3.goneo.de (Postfix) with ESMTP id C71A623F49A; Thu, 19 Sep 2019 11:17:00 +0200 (CEST) X-Virus-Scanned: by goneo X-Spam-Flag: NO X-Spam-Score: -3.025 X-Spam-Level: X-Spam-Status: No, score=-3.025 tagged_above=-999 tests=[ALL_TRUSTED=-1, AWL=-0.125, BAYES_00=-1.9] autolearn=ham Received: from smtp3.goneo.de ([127.0.0.1]) by localhost (smtp3.goneo.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KE7yAJdxsjhX; Thu, 19 Sep 2019 11:16:59 +0200 (CEST) Received: from lem-wkst-02.lemonage.de. (hq.lemonage.de [87.138.178.34]) by smtp3.goneo.de (Postfix) with ESMTPA id EAEE123F2CC; Thu, 19 Sep 2019 11:16:58 +0200 (CEST) From: Lars Poeschel To: "David S. Miller" , Rob Herring , Mark Rutland , "GitAuthor: Lars Poeschel" , netdev@vger.kernel.org (open list:NFC SUBSYSTEM), devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS), linux-kernel@vger.kernel.org (open list) Cc: Johan Hovold , Simon Horman Subject: [PATCH v8 2/7] nfc: pn532: Add uart phy docs and rename it Date: Thu, 19 Sep 2019 11:16:39 +0200 Message-Id: <20190919091645.16439-2-poeschel@lemonage.de> X-Mailer: git-send-email 2.23.0 In-Reply-To: <20190919091645.16439-1-poeschel@lemonage.de> References: <20190919091645.16439-1-poeschel@lemonage.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This adds documentation about the uart phy to the pn532 binding doc. As the filename "pn533-i2c.txt" is not appropriate any more, rename it to the more general "pn532.txt". This also documents the deprecation of the compatible strings ending with "...-i2c". Cc: Johan Hovold Cc: Simon Horman Signed-off-by: Lars Poeschel --- Changes in v8: - Update existing binding doc instead of adding a new one: - Add uart phy example - Add general "pn532" compatible string - Deprecate "...-i2c" compatible strings - Rename file to a more general filename - Intentionally drop Rob's Reviewed-By as I guess this rather big change requires a new review Changes in v7: - Accidentally lost Rob's Reviewed-By Changes in v6: - Rebased the patch series on v5.3-rc5 - Picked up Rob's Reviewed-By Changes in v4: - Add documentation about reg property in case of i2c Changes in v3: - seperate binding doc instead of entry in trivial-devices.txt .../devicetree/bindings/net/nfc/pn532.txt | 46 +++++++++++++++++++ .../devicetree/bindings/net/nfc/pn533-i2c.txt | 29 ------------ 2 files changed, 46 insertions(+), 29 deletions(-) create mode 100644 Documentation/devicetree/bindings/net/nfc/pn532.txt delete mode 100644 Documentation/devicetree/bindings/net/nfc/pn533-i2c.txt diff --git a/Documentation/devicetree/bindings/net/nfc/pn532.txt b/Documentation/devicetree/bindings/net/nfc/pn532.txt new file mode 100644 index 000000000000..f0591f160bee --- /dev/null +++ b/Documentation/devicetree/bindings/net/nfc/pn532.txt @@ -0,0 +1,46 @@ +* NXP Semiconductors PN532 NFC Controller + +Required properties: +- compatible: Should be + - "nxp,pn532" Place a node with this inside the devicetree node of the bus + where the NFC chip is connected to. + Currently the kernel has phy bindings for uart and i2c. + - "nxp,pn532-i2c" (DEPRECATED) only works for the i2c binding. + - "nxp,pn533-i2c" (DEPRECATED) only works for the i2c binding. + +Required properties if connected on i2c: +- clock-frequency: I²C work frequency. +- reg: for the I²C bus address. This is fixed at 0x24 for the PN532. +- interrupts: GPIO interrupt to which the chip is connected + +Optional SoC Specific Properties: +- pinctrl-names: Contains only one value - "default". +- pintctrl-0: Specifies the pin control groups used for this controller. + +Example (for ARM-based BeagleBone with PN532 on I2C2): + +&i2c2 { + + + pn532: pn532@24 { + + compatible = "nxp,pn532"; + + reg = <0x24>; + clock-frequency = <400000>; + + interrupt-parent = <&gpio1>; + interrupts = <17 IRQ_TYPE_EDGE_FALLING>; + + }; +}; + +Example (for PN532 connected via uart): + +uart4: serial@49042000 { + compatible = "ti,omap3-uart"; + + pn532: nfc { + compatible = "nxp,pn532"; + }; +}; diff --git a/Documentation/devicetree/bindings/net/nfc/pn533-i2c.txt b/Documentation/devicetree/bindings/net/nfc/pn533-i2c.txt deleted file mode 100644 index 2efe3886b95b..000000000000 --- a/Documentation/devicetree/bindings/net/nfc/pn533-i2c.txt +++ /dev/null @@ -1,29 +0,0 @@ -* NXP Semiconductors PN532 NFC Controller - -Required properties: -- compatible: Should be "nxp,pn532-i2c" or "nxp,pn533-i2c". -- clock-frequency: I²C work frequency. -- reg: address on the bus -- interrupts: GPIO interrupt to which the chip is connected - -Optional SoC Specific Properties: -- pinctrl-names: Contains only one value - "default". -- pintctrl-0: Specifies the pin control groups used for this controller. - -Example (for ARM-based BeagleBone with PN532 on I2C2): - -&i2c2 { - - - pn532: pn532@24 { - - compatible = "nxp,pn532-i2c"; - - reg = <0x24>; - clock-frequency = <400000>; - - interrupt-parent = <&gpio1>; - interrupts = <17 IRQ_TYPE_EDGE_FALLING>; - - }; -}; -- 2.23.0