Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp548215pxf; Wed, 17 Mar 2021 10:14:17 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwL7wLuEnYQFcoYigZZ9ft9oEfz8zXuETQbMgx2cDWhA0IFZfPUbQ9cXg6YWKpqWlKNEhNt X-Received: by 2002:a17:907:7637:: with SMTP id jy23mr35254646ejc.12.1616001257076; Wed, 17 Mar 2021 10:14:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616001257; cv=none; d=google.com; s=arc-20160816; b=Vl+SZxCTvkvI+0u8fjtn8Mz9f1UGulcY7A9vF6Hv846zA9yALEPElaSspAvPq3NN8D vrzi/e8WVj2CzHg4kgKI+1aaVGxYKd7/KHZkoFJxsQn6+Vz3obfAZEZnJh2yAlxZyzyQ ReTrfzUAHWfhyKT9IqMfIgqk1kOb5E9llqb4lY8VPZeezLc5s0MJDt2gXxv0v3SjnCwE 6fZE/enEfYlN+YfUyQ476NyHV7uFsPIN4iLqy0udKA2G5I/W4uzYCEeBwVGT+78siuYA HLVENQ14gzFOXGhDI9OcZ9QnPvvjO8phf1fQI2p8biih1goDk8OKxoEl3dgCuZmmlb+q lRXA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=HB2Rc/rZCldQdyt5cO6Jv/pqUnaDX3aycjycPvRA+KU=; b=bThR5w73FUGMPOmhUSft+B4VdvKyV8uTmNnyeMdfl7qIu7A3pIey3yRPxXQlRL84L2 SXx3l33jOE64/vpS7DjgpZ3nUm4SHdVd9RitOcUs04BrUq9UUWsY//KAHTAeA8Eok7rC kf3bbI2KGUZh4dngBMOeLcFJy/2ZedLY5v6z6fhFaniS3azaDzIozohMmNd2UJayHNAl tWWDRJ/dS2BdiGYtyMUfUv/ETNOzcW9L1JTk9n6XBqeCO4lcQkQS9ve3+4pyupg0AMMU //kZik9cGzVdhWNO+BriQ9WOedEKNJGLSisfMpuluMwv5fjt9uGgS0eoOlONdv8YX6l/ jO4w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l11si16885819edb.511.2021.03.17.10.13.53; Wed, 17 Mar 2021 10:14:17 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231660AbhCQN4x (ORCPT + 99 others); Wed, 17 Mar 2021 09:56:53 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47830 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231491AbhCQN4E (ORCPT ); Wed, 17 Mar 2021 09:56:04 -0400 Received: from bhuna.collabora.co.uk (bhuna.collabora.co.uk [IPv6:2a00:1098:0:82:1000:25:2eeb:e3e3]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 88966C06174A; Wed, 17 Mar 2021 06:56:03 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: sre) with ESMTPSA id 790261F45201 Received: by jupiter.universe (Postfix, from userid 1000) id 1B5E2480119; Wed, 17 Mar 2021 14:49:06 +0100 (CET) From: Sebastian Reichel To: Sebastian Reichel , Rob Herring Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Sebastian Reichel , kernel@collabora.com Subject: [PATCHv2 31/38] dt-bindings: power: supply: lt3651: Convert to DT schema format Date: Wed, 17 Mar 2021 14:48:57 +0100 Message-Id: <20210317134904.80737-32-sebastian.reichel@collabora.com> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20210317134904.80737-1-sebastian.reichel@collabora.com> References: <20210317134904.80737-1-sebastian.reichel@collabora.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Convert the binding to DT schema format. Signed-off-by: Sebastian Reichel --- .../power/supply/lltc,lt3651-charger.yaml | 44 +++++++++++++++++++ .../bindings/power/supply/lt3651-charger.txt | 29 ------------ 2 files changed, 44 insertions(+), 29 deletions(-) create mode 100644 Documentation/devicetree/bindings/power/supply/lltc,lt3651-charger.yaml delete mode 100644 Documentation/devicetree/bindings/power/supply/lt3651-charger.txt diff --git a/Documentation/devicetree/bindings/power/supply/lltc,lt3651-charger.yaml b/Documentation/devicetree/bindings/power/supply/lltc,lt3651-charger.yaml new file mode 100644 index 000000000000..e2d8d2aebb73 --- /dev/null +++ b/Documentation/devicetree/bindings/power/supply/lltc,lt3651-charger.yaml @@ -0,0 +1,44 @@ +# SPDX-License-Identifier: GPL-2.0 +%YAML 1.2 +--- +$id: "http://devicetree.org/schemas/power/supply/lltc,lt3651-charger.yaml#" +$schema: "http://devicetree.org/meta-schemas/core.yaml#" + +title: Analog Devices LT3651 Charger Power Supply bindings + +maintainers: + - Sebastian Reichel + +allOf: + - $ref: power-supply.yaml# + +properties: + compatible: + enum: + - lltc,lt3651-charger + - lltc,ltc3651-charger # deprecated, use lltc,lt3651-charger + + lltc,acpr-gpios: + maxItems: 1 + + lltc,fault-gpios: + maxItems: 1 + + lltc,chrg-gpios: + maxItems: 1 + +required: + - compatible + - lltc,acpr-gpios + +additionalProperties: false + +examples: + - | + #include + charger { + compatible = "lltc,lt3651-charger"; + lltc,acpr-gpios = <&gpio0 68 GPIO_ACTIVE_LOW>; + lltc,fault-gpios = <&gpio0 64 GPIO_ACTIVE_LOW>; + lltc,chrg-gpios = <&gpio0 63 GPIO_ACTIVE_LOW>; + }; diff --git a/Documentation/devicetree/bindings/power/supply/lt3651-charger.txt b/Documentation/devicetree/bindings/power/supply/lt3651-charger.txt deleted file mode 100644 index 40811ff8de10..000000000000 --- a/Documentation/devicetree/bindings/power/supply/lt3651-charger.txt +++ /dev/null @@ -1,29 +0,0 @@ -Analog Devices LT3651 Charger Power Supply bindings: lt3651-charger - -Required properties: -- compatible: Should contain one of the following: - * "lltc,ltc3651-charger", (DEPRECATED: Use "lltc,lt3651-charger") - * "lltc,lt3651-charger" - - lltc,acpr-gpios: Connect to ACPR output. See remark below. - -Optional properties: - - lltc,fault-gpios: Connect to FAULT output. See remark below. - - lltc,chrg-gpios: Connect to CHRG output. See remark below. - -The lt3651 outputs are open-drain type and active low. The driver assumes the -GPIO reports "active" when the output is asserted, so if the pins have been -connected directly, the GPIO flags should be set to active low also. - -The driver will attempt to aquire interrupts for all GPIOs to detect changes in -line state. If the system is not capabale of providing interrupts, the driver -cannot report changes and userspace will need to periodically read the sysfs -attributes to detect changes. - -Example: - - charger: battery-charger { - compatible = "lltc,lt3651-charger"; - lltc,acpr-gpios = <&gpio0 68 GPIO_ACTIVE_LOW>; - lltc,fault-gpios = <&gpio0 64 GPIO_ACTIVE_LOW>; - lltc,chrg-gpios = <&gpio0 63 GPIO_ACTIVE_LOW>; - }; -- 2.30.2