From: Rob Herring <robh@kernel.org>
To: Pankaj Patil <pankaj.patil@oss.qualcomm.com>
Cc: sboyd@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: spmi: add bindings for glymur-spmi-pmic-arb (arbiter v8)
Date: Wed, 24 Sep 2025 11:04:14 -0500 [thread overview]
Message-ID: <20250924160414.GA1780679-robh@kernel.org> (raw)
In-Reply-To: <20250919140952.1057737-1-pankaj.patil@oss.qualcomm.com>
On Fri, Sep 19, 2025 at 07:39:52PM +0530, Pankaj Patil wrote:
> From: Jishnu Prakash <jishnu.prakash@oss.qualcomm.com>
>
> SPMI PMIC Arbiter version 8 builds upon version 7 with support for
> up to four SPMI buses. To achieve this, the register map was
> slightly rearranged. Add a new binding file and compatible string
> for version 8 using the name 'glymur' as the Qualcomm Technologies,
> Inc. Glymur SoC is the first one to use PMIC arbiter version 8. This
> specifies the new register ranges needed only for version 8.
>
> Signed-off-by: David Collins <david.collins@oss.qualcomm.com>
> Signed-off-by: Jishnu Prakash <jishnu.prakash@oss.qualcomm.com>
> Signed-off-by: Pankaj Patil <pankaj.patil@oss.qualcomm.com>
> ---
> .../spmi/qcom,glymur-spmi-pmic-arb.yaml | 158 ++++++++++++++++++
> 1 file changed, 158 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/spmi/qcom,glymur-spmi-pmic-arb.yaml
>
> diff --git a/Documentation/devicetree/bindings/spmi/qcom,glymur-spmi-pmic-arb.yaml b/Documentation/devicetree/bindings/spmi/qcom,glymur-spmi-pmic-arb.yaml
> new file mode 100644
> index 000000000000..e80997a5fb4b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/spmi/qcom,glymur-spmi-pmic-arb.yaml
> @@ -0,0 +1,158 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/spmi/qcom,glymur-spmi-pmic-arb.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm Technologies, Inc. Glymur SPMI Controller (PMIC Arbiter v8)
> +
> +maintainers:
> + - Stephen Boyd <sboyd@kernel.org>
> +
> +description: |
> + The Glymur SPMI PMIC Arbiter implements HW version 8 and it's an SPMI
> + controller with wrapping arbitration logic to allow for multiple on-chip
> + devices to control up to 4 SPMI separate buses.
> +
> + The PMIC Arbiter can also act as an interrupt controller, providing interrupts
> + to slave devices.
> +
> +properties:
> + compatible:
> + enum:
> + - qcom,glymur-spmi-pmic-arb
> +
> + reg:
> + items:
> + - description: core registers
> + - description: tx-channel per virtual slave registers
> + - description: rx-channel (called observer) per virtual slave registers
> + - description: channel to PMIC peripheral mapping registers
> +
> + reg-names:
> + items:
> + - const: core
> + - const: chnls
> + - const: obsrvr
> + - const: chnl_map
> +
> + ranges: true
> +
> + '#address-cells':
> + const: 2
> +
> + '#size-cells':
> + const: 2
> +
> + qcom,ee:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + minimum: 0
> + maximum: 5
> + description: >
> + indicates the active Execution Environment identifier
> +
> + qcom,channel:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + minimum: 0
> + maximum: 5
> + description: >
> + which of the PMIC Arb provided channels to use for accesses
We already have these properties defined elsewhere. You need to pull the
common properties out into a shared schema and then reference that
schema in this one. IOW, a given property should only have a type $ref
in a single place.
> +
> +patternProperties:
> + "^spmi@[a-f0-9]+$":
> + type: object
> + $ref: /schemas/spmi/spmi.yaml
> + unevaluatedProperties: false
> +
> + properties:
> + reg:
> + items:
> + - description: configuration registers
> + - description: interrupt controller registers
> + - description: channel owner EE mapping registers
> +
> + reg-names:
> + items:
> + - const: cnfg
> + - const: intr
> + - const: chnl_owner
> +
> + interrupts:
> + maxItems: 1
> +
> + interrupt-names:
> + const: periph_irq
> +
> + interrupt-controller: true
> +
> + '#interrupt-cells':
> + const: 4
> + description: |
> + cell 1: slave ID for the requested interrupt (0-15)
> + cell 2: peripheral ID for requested interrupt (0-255)
> + cell 3: the requested peripheral interrupt (0-7)
> + cell 4: interrupt flags indicating level-sense information,
> + as defined in dt-bindings/interrupt-controller/irq.h
> +
> +required:
> + - compatible
> + - reg-names
> + - qcom,ee
> + - qcom,channel
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> +
> + soc {
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + arbiter@c400000 {
> + compatible = "qcom,glymur-spmi-pmic-arb";
> + reg = <0x0 0xc400000 0x0 0x3000>,
> + <0x0 0xc900000 0x0 0x400000>,
> + <0x0 0xc4c0000 0x0 0x400000>,
> + <0x0 0xc403000 0x0 0x8000>;
> + reg-names = "core", "chnls", "obsrvr", "chnl_map";
> +
> + qcom,ee = <0>;
> + qcom,channel = <0>;
> +
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + spmi@c426000 {
> + reg = <0x0 0xc426000 0x0 0x4000>,
> + <0x0 0xc8c0000 0x0 0x10000>,
> + <0x0 0xc42a000 0x0 0x8000>;
> + reg-names = "cnfg", "intr", "chnl_owner";
> +
> + interrupts-extended = <&pdc 1 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-names = "periph_irq";
> + interrupt-controller;
> + #interrupt-cells = <4>;
> +
> + #address-cells = <2>;
> + #size-cells = <0>;
> + };
> +
> + spmi@c437000 {
> + reg = <0x0 0xc437000 0x0 0x4000>,
> + <0x0 0xc8d0000 0x0 0x10000>,
> + <0x0 0xc43b000 0x0 0x8000>;
> + reg-names = "cnfg", "intr", "chnl_owner";
> +
> + interrupts-extended = <&pdc 3 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-names = "periph_irq";
> + interrupt-controller;
> + #interrupt-cells = <4>;
> +
> + #address-cells = <2>;
> + #size-cells = <0>;
> + };
> + };
> + };
> --
> 2.34.1
>
prev parent reply other threads:[~2025-09-24 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 14:09 Pankaj Patil
2025-09-24 16:04 ` Rob Herring [this message]
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=20250924160414.GA1780679-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.patil@oss.qualcomm.com \
--cc=sboyd@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
all inboxes | Powered by JetHome®