From: Rob Herring <robh@kernel.org>
To: Dzmitry Sankouski <dsankouski@gmail.com>
Cc: Sebastian Reichel <sre@kernel.org>,
Chanwoo Choi <cw00.choi@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>, Lee Jones <lee@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Pavel Machek <pavel@ucw.cz>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-input@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: Re: [PATCH v5 2/7] dt-bindings: mfd: add maxim,max77705
Date: Thu, 26 Sep 2024 13:38:58 -0500 [thread overview]
Message-ID: <20240926183858.GA2718844-robh@kernel.org> (raw)
In-Reply-To: <20240617-starqltechn_integration_upstream-v5-2-e0033f141d17@gmail.com>
On Thu, Sep 26, 2024 at 01:20:19PM +0300, Dzmitry Sankouski wrote:
> Add maxim,max77705 core binding part.
>
> Signed-off-by: Dzmitry Sankouski <dsankouski@gmail.com>
>
> ---
> Changes in v5:
> - formatting changes
> - add unevaluatedProperties: false for nodes referencing
> common schemas
> - remove additionalProperties on nodes with
> unevaluatedProperties: false
> - add min and max to led index
> Changes in v4:
> - change dts example intendation from tabs
> to spaces
> - remove interrupt-names property
> - remove obvious reg description
> - split long(>80) lines
> ---
> Documentation/devicetree/bindings/mfd/maxim,max77705.yaml | 177 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 178 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mfd/maxim,max77705.yaml b/Documentation/devicetree/bindings/mfd/maxim,max77705.yaml
> new file mode 100644
> index 000000000000..214515f84c85
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mfd/maxim,max77705.yaml
> @@ -0,0 +1,177 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mfd/maxim,max77705.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Maxim MAX77705 Companion Power Management IC and USB Type-C interface IC
> +
> +maintainers:
> + - Dzmitry Sankouski <dsankouski@gmail.com>
> +
> +description: |
> + This is a part of device tree bindings for Maxim MAX77705 multi functional
> + device.
Drop this sentence. Just describe the device.
> +
> + The Maxim MAX77705 is a Companion Power Management and Type-C
> + interface IC which includes charger, fuelgauge, LED, haptic motor driver and
> + Type-C management IC.
> +
> +properties:
> + compatible:
> + const: maxim,max77705
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + charger:
> + $ref: /schemas/power/supply/power-supply.yaml
> + unevaluatedProperties: true
Must be false.
> + properties:
> + compatible:
> + const: maxim,max77705-charger
> +
> + required:
> + - compatible
> + - monitored-battery
> +
> + fuel-gauge:
> + $ref: /schemas/power/supply/power-supply.yaml
> + type: object
> + unevaluatedProperties: true
Must be false.
Rob
next prev parent reply other threads:[~2024-09-26 18:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 10:20 [PATCH v5 0/7] Add support for Maxim Integrated MAX77705 MFD Dzmitry Sankouski
2024-09-26 10:20 ` [PATCH v5 1/7] power: supply: add undervoltage health status property Dzmitry Sankouski
2024-09-26 10:20 ` [PATCH v5 2/7] dt-bindings: mfd: add maxim,max77705 Dzmitry Sankouski
2024-09-26 18:38 ` Rob Herring [this message]
2024-09-26 10:20 ` [PATCH v5 3/7] mfd: Add new driver for MAX77705 PMIC Dzmitry Sankouski
2024-09-26 10:20 ` [PATCH v5 4/7] input: max77693: add max77705 haptic support Dzmitry Sankouski
2024-09-27 16:36 ` Dmitry Torokhov
2024-09-26 10:20 ` [PATCH v5 5/7] power: supply: max77705: Add charger driver for Maxim 77705 Dzmitry Sankouski
2024-09-26 10:20 ` [PATCH v5 6/7] power: supply: max77705: Add fuel gauge " Dzmitry Sankouski
2024-09-26 10:20 ` [PATCH v5 7/7] leds: max77705: Add LEDs support Dzmitry Sankouski
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=20240926183858.GA2718844-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dsankouski@gmail.com \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sre@kernel.org \
/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).