From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753913AbdEEGiq (ORCPT ); Fri, 5 May 2017 02:38:46 -0400 Received: from atl4mhob20.registeredsite.com ([209.17.115.114]:41102 "EHLO atl4mhob20.registeredsite.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752037AbdEEGio (ORCPT ); Fri, 5 May 2017 02:38:44 -0400 X-TCPREMOTEIP: 37.74.225.130 X-Authenticated-UID: mike@milosoftware.com From: Mike Looijmans To: devicetree@vger.kernel.org Cc: sre@kernel.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, robh+dt@kernel.org, mark.rutland@arm.com, Mike Looijmans Subject: [PATCH] dt-bindings: power: New bindings for ltc3651-charger Date: Fri, 5 May 2017 08:38:35 +0200 Message-Id: <1493966315-15893-1-git-send-email-mike.looijmans@topic.nl> X-Mailer: git-send-email 1.9.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This adds the devicetree bindings documentation for the LTC3651 battery charger. Signed-off-by: Mike Looijmans --- .../bindings/power/supply/ltc3651-charger.txt | 26 ++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 Documentation/devicetree/bindings/power/supply/ltc3651-charger.txt diff --git a/Documentation/devicetree/bindings/power/supply/ltc3651-charger.txt b/Documentation/devicetree/bindings/power/supply/ltc3651-charger.txt new file mode 100644 index 0000000..a7dd80f --- /dev/null +++ b/Documentation/devicetree/bindings/power/supply/ltc3651-charger.txt @@ -0,0 +1,26 @@ +ltc3651-charger + +Required properties: + - compatible: "lltc,ltc3651-charger" + - acpr-gpios: Connect to ACPR output. See remark below. + +Optional properties: + - fault-gpios: Connect to FAULT output. See remark below. + - chrg-gpios: Connect to CHRG output. See remark below. + +The ltc3651 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. If the system is +not capabale of providing that, the driver cannot report changes and userspace +will need to periodically read the sysfs attributes to detect changes. + +Example: + + charger: battery-charger { + compatible = "lltc,ltc3651-charger"; + acpr-gpios = <&gpio0 68 GPIO_ACTIVE_LOW>; + fault-gpios = <&gpio0 64 GPIO_ACTIVE_LOW>; + chrg-gpios = <&gpio0 63 GPIO_ACTIVE_LOW>; + }; -- 1.9.1