From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Rob Herring <robh@kernel.org>
Cc: lee@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
matthias.bgg@gmail.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH v1 1/2] dt-bindings: mfd: Add binding for MediaTek MT6363 series SPMI PMIC
Date: Wed, 25 Jun 2025 10:30:44 +0200 [thread overview]
Message-ID: <40f07604-f4eb-4a7d-88b4-ed29e9242d6e@collabora.com> (raw)
In-Reply-To: <20250625005130.GA2106374-robh@kernel.org>
Il 25/06/25 02:51, Rob Herring ha scritto:
> On Mon, Jun 23, 2025 at 02:00:37PM +0200, AngeloGioacchino Del Regno wrote:
>> Add a binding for the MediaTek MT6363/6373 (and similar) multi
>> function PMICs connected over SPMI.
>>
>> These PMICs are found on board designs using newer MediaTek SoCs,
>> such as the Dimensity 9400 Smartphone chip, or the Chromebook
>> MT8196 chip.
>>
>> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
>> ---
>> .../bindings/mfd/mediatek,mt6363.yaml | 98 +++++++++++++++++++
>> 1 file changed, 98 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/mfd/mediatek,mt6363.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/mfd/mediatek,mt6363.yaml b/Documentation/devicetree/bindings/mfd/mediatek,mt6363.yaml
>> new file mode 100644
>> index 000000000000..2ce57e659d12
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/mfd/mediatek,mt6363.yaml
>> @@ -0,0 +1,98 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/mfd/mediatek,mt6363.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: MediaTek MT6363 series SPMI PMICs multi-function device
>> +
>> +maintainers:
>> + - AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
>> +
>> +description: |
>> + Some MediaTek Power Management ICs (PMICs) found in board designs with
>> + the Helio, Dimensity and/or Kompanio series of SoCs are interfaced to
>> + the chip via the System Power Management Interface (SPMI) bus.
>> +
>> + These PMICs are multi-function devices with various sub modules.
>> + For example, those may include one, or more of the following:
>> + - Auxiliary ADC Controller
>> + - Clock Controller
>> + - eFuses
>> + - GPIO Controller
>> + - Interrupt Controller
>> + - Keys
>> + - LEDs Controller
>> + - Regulators
>> + - RTC
>> +
>> +properties:
>> + compatible:
>> + items:
>> + - enum:
>> + - mediatek,mt6363
>> + - mediatek,mt6373
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + '#address-cells':
>> + const: 0
>> +
>> + '#size-cells':
>> + const: 0
>> +
>> + interrupts:
>> + maxItems: 1
>> +
>> + interrupt-controller: true
>> +
>> + "#interrupt-cells":
>> + const: 3
>> +
>> + adc:
>> + type: object
>> + $ref: /schemas/iio/adc/mediatek,mt6359-auxadc.yaml#
>> + unevaluatedProperties: false
>> +
>> + regulators:
>> + type: object
>> + oneOf:
>> + - $ref: /schemas/regulator/mediatek,mt6363-regulator.yaml#
>> + - $ref: /schemas/regulator/mediatek,mt6373-regulator.yaml#
>
> This causes the schemas to be applied 4 times (2 each). Better if you
> do:
>
> properties:
> compatible:
> contains:
> enum: [ the compatibles in those schemas ]
>
>
Noted, thanks!
>> + additionalProperties: true
>> +
>> + keys:
>> + type: object
>> + $ref: /schemas/input/mediatek,pmic-keys.yaml
>> + unevaluatedProperties: false
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - '#address-cells'
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/interrupt-controller/irq.h>
>> + #include <dt-bindings/spmi/spmi.h>
>> +
>> + spmi {
>> + #address-cells = <2>;
>> + #size-cells = <0>;
>> +
>> + pmic@4 {
>> + compatible = "mediatek,mt6363";
>> + reg = <0x4 SPMI_USID>;
>> + interrupts = <4 64 IRQ_TYPE_LEVEL_HIGH>;
>> + interrupt-controller;
>> + #address-cells = <0>;
>> + #interrupt-cells = <3>;
>> +
>> + regulators {
>> + compatible = "mediatek,mt6363-regulator";
>> + };
>
> Make the example complete. with adc and keys nodes.
>
You mean just adding a
adc {
compatible = xyz;
};
keys {
compatible = xyz;
};
right?
I will add the full example in the next version :-)
Thank you!
Angelo
>> + };
>> + };
>> --
>> 2.49.0
>>
next prev parent reply other threads:[~2025-06-25 8:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 12:00 [PATCH v1 0/2] mfd: Add driver for multifunction MediaTek SPMI PMICs AngeloGioacchino Del Regno
2025-06-23 12:00 ` [PATCH v1 1/2] dt-bindings: mfd: Add binding for MediaTek MT6363 series SPMI PMIC AngeloGioacchino Del Regno
2025-06-23 14:22 ` Rob Herring (Arm)
2025-06-24 7:27 ` AngeloGioacchino Del Regno
2025-06-25 0:47 ` Rob Herring
2025-06-25 0:51 ` Rob Herring
2025-06-25 8:30 ` AngeloGioacchino Del Regno [this message]
2025-06-23 12:00 ` [PATCH v1 2/2] drivers: mfd: Add support for MediaTek SPMI PMICs and MT6363/73 AngeloGioacchino Del Regno
2025-06-24 15:03 ` [PATCH v1 0/2] mfd: Add driver for multifunction MediaTek SPMI PMICs Nícolas F. R. A. Prado
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=40f07604-f4eb-4a7d-88b4-ed29e9242d6e@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@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).