| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 20 Mar 2023 17:35:03 +0100
From: Julien Panis <jpanis@...libre.com>
To: Rob Herring <robh@...nel.org>
Cc: lee@...nel.org, krzysztof.kozlowski+dt@...aro.org, corbet@....net,
arnd@...db.de, gregkh@...uxfoundation.org,
derek.kiernan@...inx.com, dragan.cvetic@...inx.com,
eric.auger@...hat.com, jgg@...pe.ca, razor@...ckwall.org,
stephen@...workplumber.org, davem@...emloft.net,
christian.koenig@....com, contact@...rsion.fr,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, sterzik@...com, u-kumar1@...com,
eblanc@...libre.com, jneanne@...libre.com
Subject: Re: [PATCH v2 1/4] dt-bindings: mfd: Add TI TPS6594 PMIC
On 3/20/23 16:53, Rob Herring wrote:
> On Wed, Mar 15, 2023 at 12:07:33PM +0100, Julien Panis wrote:
>> TPS6594 is a Power Management IC which provides regulators and others
>> features like GPIOs, RTC, watchdog, ESMs (Error Signal Monitor), and
>> PFSM (Pre-configurable Finite State Machine) managing the state of the
>> device.
>> TPS6594 is the super-set device while TPS6593 and LP8764X are derivatives.
> As mentioned, the binding needs to be complete. It's missing GPIO at
> least. RTC and watchdog may or may not need binding changes.
Thank you for your feedback.
About GPIO, do you speak about 'gpio-controller'
and/or '#gpio-cells' properties ?
For RTC (and for watchdog, once the driver will be
implemented), our driver do not require any node
to work. What could make an explicit instantiation
necessary in DT ?
>
>> Signed-off-by: Julien Panis <jpanis@...libre.com>
>> ---
>> .../devicetree/bindings/mfd/ti,tps6594.yaml | 191 ++++++++++++++++++
>> 1 file changed, 191 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/mfd/ti,tps6594.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/mfd/ti,tps6594.yaml b/Documentation/devicetree/bindings/mfd/ti,tps6594.yaml
>> new file mode 100644
>> index 000000000000..18f47cd6a2f9
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/mfd/ti,tps6594.yaml
>> @@ -0,0 +1,191 @@
>> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/mfd/ti,tps6594.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: TI TPS6594 Power Management Integrated Circuit
>> +
>> +maintainers:
>> + - Julien Panis <jpanis@...libre.com>
>> +
>> +description: |
> Don't need '|'.
>
>> + TPS6594 is a Power Management IC which provides regulators and others
>> + features like GPIOs, RTC, watchdog, ESMs (Error Signal Monitor), and
>> + PFSM (Pre-configurable Finite State Machine) managing the state of the device.
>> + TPS6594 is the super-set device while TPS6593 and LP8764X are derivatives.
>> +
>> +properties:
>> + compatible:
>> + enum:
>> + - ti,lp8764x
>> + - ti,tps6593
>> + - ti,tps6594
>> +
>> + reg:
>> + description: I2C slave address or SPI chip select number.
>> + maxItems: 1
>> +
>> + ti,spmi-controller:
>> + type: boolean
>> + description: |
>> + Identify the primary PMIC on SPMI bus.
> Perhaps the property name should include 'primary' and 'pmic'.
> Otherwise, it looks like it is just marked as 'a SPMI controller'.
Including 'primary' and 'pmic' will be more understandable indeed.
I will change that in v3.
>
>
>> + A multi-PMIC synchronization scheme is implemented in the PMIC device
>> + to synchronize the power state changes with other PMIC devices. This is
>> + accomplished through a SPMI bus: the primary PMIC is the controller
>> + device on the SPMI bus, and the secondary PMICs are the target devices
>> + on the SPMI bus.
> Is this a TI specific feature?
I don't think so. I will double-check that.
If not, shall I remove the 'ti,' prefix ?
>
>> +
>> + system-power-controller: true
>> +
>> + interrupts:
>> + maxItems: 1
>> +
>> + ti,multi-phase-id:
>> + description: |
>> + Describes buck multi-phase configuration, if any. For instance, XY id means
>> + that outputs of buck converters X and Y are combined in multi-phase mode.
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> + enum: [12, 34, 123, 1234]
> coupled regulator stuff doesn't work here?
Coupled regulator stuff works here.
Is it also necessary to specify some 'allOf' logic here to ensure
that mutual exclusions described below (for regulators) will be
applied ?
>
>> +
>> + regulators:
>> + type: object
>> + description: List of regulators provided by this controller.
>> +
>> + patternProperties:
>> + "^buck([1-5]|12|34|123|1234)$":
>> + type: object
>> + $ref: /schemas/regulator/regulator.yaml#
>> +
>> + unevaluatedProperties: false
>> +
>> + "^ldo[1-4]$":
>> + type: object
>> + $ref: /schemas/regulator/regulator.yaml#
>> +
>> + unevaluatedProperties: false
>> +
>> + allOf:
>> + - if:
>> + required:
>> + - buck12
>> + then:
>> + properties:
>> + buck123: false
>> + buck1234: false
>> + - if:
>> + required:
>> + - buck123
>> + then:
>> + properties:
>> + buck34: false
>> + - if:
>> + required:
>> + - buck1234
>> + then:
>> + properties:
>> + buck34: false
>> +
>> + additionalProperties: false
>> +
>> +patternProperties:
>> + "^buck([1-5]|12|34|123|1234)-supply$":
>> + description: Input supply phandle for each buck.
>> +
>> + "^ldo[1-4]-supply$":
>> + description: Input supply phandle for each ldo.
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - interrupts
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/interrupt-controller/arm-gic.h>
>> + i2c {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + tps6593: pmic@48 {
>> + compatible = "ti,tps6593";
>> + reg = <0x48>;
>> + ti,spmi-controller;
>> + system-power-controller;
>> +
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&pmic_irq_pins_default>;
>> + interrupt-parent = <&mcu_gpio0>;
>> + interrupts = <0 IRQ_TYPE_EDGE_FALLING>;
>> +
>> + ti,multi-phase-id = <123>;
>> +
>> + buck123-supply = <&vcc_3v3_sys>;
>> + buck4-supply = <&vcc_3v3_sys>;
>> + buck5-supply = <&vcc_3v3_sys>;
>> + ldo1-supply = <&vcc_3v3_sys>;
>> + ldo2-supply = <&vcc_3v3_sys>;
>> + ldo3-supply = <&buck5>;
>> + ldo4-supply = <&vcc_3v3_sys>;
>> +
>> + regulators {
>> + buck123: buck123 {
>> + regulator-name = "vcc_core";
>> + regulator-min-microvolt = <750000>;
>> + regulator-max-microvolt = <850000>;
>> + regulator-boot-on;
>> + regulator-always-on;
>> + };
>> +
>> + buck4: buck4 {
>> + regulator-name = "vcc_1v1";
>> + regulator-min-microvolt = <1100000>;
>> + regulator-max-microvolt = <1100000>;
>> + regulator-boot-on;
>> + regulator-always-on;
>> + };
>> +
>> + buck5: buck5 {
>> + regulator-name = "vcc_1v8_sys";
>> + regulator-min-microvolt = <1800000>;
>> + regulator-max-microvolt = <1800000>;
>> + regulator-boot-on;
>> + regulator-always-on;
>> + };
>> +
>> + ldo1: ldo1 {
>> + regulator-name = "vddshv5_sdio";
>> + regulator-min-microvolt = <3300000>;
>> + regulator-max-microvolt = <3300000>;
>> + regulator-boot-on;
>> + regulator-always-on;
>> + };
>> +
>> + ldo2: ldo2 {
>> + regulator-name = "vpp_1v8";
>> + regulator-min-microvolt = <1800000>;
>> + regulator-max-microvolt = <1800000>;
>> + regulator-boot-on;
>> + regulator-always-on;
>> + };
>> +
>> + ldo3: ldo3 {
>> + regulator-name = "vcc_0v85";
>> + regulator-min-microvolt = <850000>;
>> + regulator-max-microvolt = <850000>;
>> + regulator-boot-on;
>> + regulator-always-on;
>> + };
>> +
>> + ldo4: ldo4 {
>> + regulator-name = "vdda_1v8";
>> + regulator-min-microvolt = <1800000>;
>> + regulator-max-microvolt = <1800000>;
>> + regulator-boot-on;
>> + regulator-always-on;
>> + };
>> + };
>> + };
>> + };
>> --
>> 2.37.3
>>
Powered by blists - more mailing lists