xref: /linux/Documentation/devicetree/bindings/power/supply/twl4030-charger.yaml (revision 4f2c0a4acffbec01079c28f839422e64ddeff004) 
1# SPDX-License-Identifier: GPL-2.0
2%YAML 1.2
3---
4$id: http://devicetree.org/schemas/power/supply/twl4030-charger.yaml#
5$schema: http://devicetree.org/meta-schemas/core.yaml#
6
7title: TWL4030 BCI (Battery Charger Interface)
8
9description: |
10  The battery charger needs to interact with the USB phy in order to know when
11  charging is permissible, and when there is a connection or disconnection.
12
13  The choice of phy cannot be configured at a hardware level, so there is no
14  value in explicit configuration in device-tree. Rather if there is a sibling
15  of the BCI node which is compatible with "ti,twl4030-usb", then that is used
16  to determine when and how use USB power for charging.
17
18maintainers:
19  - Sebastian Reichel <sre@kernel.org>
20
21allOf:
22  - $ref: power-supply.yaml#
23
24properties:
25  compatible:
26    const: ti,twl4030-bci
27
28  interrupts:
29    minItems: 2
30    maxItems: 2
31
32  ti,bb-uvolt:
33    $ref: /schemas/types.yaml#/definitions/uint32
34    description: microvolts for charging the backup battery
35
36  ti,bb-uamp:
37    $ref: /schemas/types.yaml#/definitions/uint32
38    description: microamps for charging the backup battery
39
40  io-channels:
41    items:
42      - description: Accessory Charger Voltage Channel
43
44  io-channel-names:
45    items:
46      - const: vac
47
48  bci3v1-supply:
49    description: 3.1V USB regulator
50
51required:
52  - compatible
53  - interrupts
54
55additionalProperties: false
56
57examples:
58  - |
59    pmic {
60      charger {
61        compatible = "ti,twl4030-bci";
62        interrupts = <9>, <2>;
63        ti,bb-uvolt = <3200000>;
64        ti,bb-uamp = <150>;
65        io-channels = <&twl_madc 11>;
66        io-channel-names = "vac";
67      };
68    };
69