linux-rtc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Matt Ranostay <mranostay@ti.com>
Cc: nm@ti.com, j-keerthy@ti.com, lee@kernel.org,
	linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/6] Documentation: tps6594x: Add DT bindings for the TPS6594x PMIC
Date: Tue, 16 Aug 2022 11:20:49 -0600	[thread overview]
Message-ID: <20220816172049.GA2399563-robh@kernel.org> (raw)
In-Reply-To: <20220812032242.564026-2-mranostay@ti.com>

On Thu, Aug 11, 2022 at 08:22:37PM -0700, Matt Ranostay wrote:
> Signed-off-by: Matt Ranostay <mranostay@ti.com>

Commit message? Use a subject prefix appropriate for the subsystem.

> ---
>  .../devicetree/bindings/mfd/ti,tps6594x.yaml  | 56 +++++++++++++++++++
>  1 file changed, 56 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/mfd/ti,tps6594x.yaml
> 
> diff --git a/Documentation/devicetree/bindings/mfd/ti,tps6594x.yaml b/Documentation/devicetree/bindings/mfd/ti,tps6594x.yaml
> new file mode 100644
> index 000000000000..9b5e17f63709
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mfd/ti,tps6594x.yaml
> @@ -0,0 +1,56 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mfd/ti,tps6594x.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: TPS6594x Power Management Integrated Circuit (PMIC)
> +
> +maintainers:
> +  - Keerthy <j-keerthy@ti.com>
> +
> +properties:
> +  compatible:
> +    contains:

No, this means '"foo", "ti,tps6594x", "bar"' is valid.

> +      enum:

Use 'const' if only 1 entry.

> +        - ti,tps6594x

Don't use wildcards in compatible strings.

> +
> +  reg:
> +    const: 0x48
> +    description: I2C slave address
> +
> +  ti,system-power-controller:
> +    type: boolean
> +    description: PMIC is controlling the system power.
> +
> +  rtc:

Why do you need a sub-node here? Is the RTC a separate block with its 
own resources?

> +    type: object
> +    $ref: /schemas/rtc/rtc.yaml#
> +    unevaluatedProperties: false
> +    properties:
> +      compatible:
> +        const: ti,tps6594x-rtc
> +
> +additionalProperties: false
> +
> +required:
> +  - compatible
> +  - reg
> +
> +examples:
> +  - |
> +    i2c0 {

i2c {

> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +
> +        pmic: pmic@48 {
> +            compatible = "ti,tps6594x";
> +            reg = <0x48>;
> +
> +            rtc {
> +                compatible = "ti,tps6594x-rtc";
> +            };
> +        };
> +    };
> +
> +...
> -- 
> 2.36.1
> 
> 

  reply	other threads:[~2022-08-16 17:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12  3:22 [PATCH v2 0/6] mfd: add tps6594x support for Jacinto platform Matt Ranostay
2022-08-12  3:22 ` [PATCH v2 1/6] Documentation: tps6594x: Add DT bindings for the TPS6594x PMIC Matt Ranostay
2022-08-16 17:20   ` Rob Herring [this message]
2022-08-12  3:22 ` [PATCH v2 2/6] MFD: TPS6594x: Add new PMIC device driver for TPS6594x chips Matt Ranostay
2022-08-12  7:01   ` Lee Jones
2022-08-30 20:09     ` Matt Ranostay
2022-09-05 14:35       ` Lee Jones
2022-08-12  3:22 ` [PATCH v2 3/6] rtc: rtc-tps6594x: Add support for TPS6594X PMIC RTC Matt Ranostay
2022-08-12  3:22 ` [PATCH v2 4/6] arm64: dts: ti: k3-j7200-common-proc-board: Add TPS6594x PMIC node Matt Ranostay
2022-08-12  3:22 ` [PATCH v2 5/6] arm64: dts: ti: k3-j721e-common-proc-board: " Matt Ranostay
2022-08-12  3:22 ` [PATCH v2 6/6] arm64: dts: ti: k3-j721s2-common-proc-board: " Matt Ranostay

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220816172049.GA2399563-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=j-keerthy@ti.com \
    --cc=lee@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=mranostay@ti.com \
    --cc=nm@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).