From: Lee Jones <lee.jones@linaro.org>
To: Guru Das Srinagesh <gurus@codeaurora.org>
Cc: devicetree@vger.kernel.org,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Subbaraman Narayanamurthy <subbaram@codeaurora.org>,
David Collins <collinsd@codeaurora.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] dt-bindings: mfd: Document QTI I2C PMIC controller
Date: Wed, 29 Apr 2020 08:51:49 +0100 [thread overview]
Message-ID: <20200429075149.GY3559@dell> (raw)
In-Reply-To: <0960b5d17013124d9bbdbe7f28374b3d6c9c026e.1588115326.git.gurus@codeaurora.org>
On Tue, 28 Apr 2020, Guru Das Srinagesh wrote:
> The Qualcomm Technologies, Inc. I2C PMIC Controller is used by
> multi-function PMIC devices which communicate over the I2C bus. The
> controller enumerates all child nodes as platform devices, and
> instantiates a regmap interface for them to communicate over the I2C
> bus.
>
> The controller also controls interrupts for all of the children platform
> devices. The controller handles the summary interrupt by deciphering
> which peripheral triggered the interrupt, and which of the peripheral
> interrupts were triggered. Finally, it calls the interrupt handlers for
> each of the virtual interrupts that were registered.
>
> Signed-off-by: Guru Das Srinagesh <gurus@codeaurora.org>
> ---
> Changes from v0:
> - Fixed "FATAL ERROR: Unable to parse input tree" error thrown by `make
> dt_binding_check`.
>
> .../devicetree/bindings/mfd/qcom,i2c-pmic.yaml | 86 ++++++++++++++++++++++
> 1 file changed, 86 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mfd/qcom,i2c-pmic.yaml
>
> diff --git a/Documentation/devicetree/bindings/mfd/qcom,i2c-pmic.yaml b/Documentation/devicetree/bindings/mfd/qcom,i2c-pmic.yaml
> new file mode 100644
> index 0000000..42482af
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mfd/qcom,i2c-pmic.yaml
> @@ -0,0 +1,86 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mfd/qcom,i2c-pmic.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm Technologies, Inc. I2C PMIC Interrupt Controller Platform Independent Bindings
> +
> +description: |
> + The I2C PMIC Controller is used by multi-function PMIC devices which
> + communicate over the I2C bus. An I2C PMIC controller node typically contains
> + one or more child nodes representing the device's peripherals. Each of the
> + peripherals typically has its own driver on the platform bus and will be
> + enumerated by this controller. The controller exposes a regmap to the
> + peripherals to communicate over the I2C bus.
> +
> + The controller also controls interrupts for all of the peripherals on the
> + bus. The controller takes a summary interrupt, deciphers which peripheral
> + triggered the interrupt, and which of the peripheral's interrupts were
> + triggered. Finally, it calls the handlers for each of the virtual interrupts
> + that were registered.
> +
> + This document describes the common platform independent bindings that apply
> + to all I2C PMIC interrupt controllers.
> +
> +maintainers:
> + - Guru Das Srinagesh <gurus@codeaurora.org>
> +
> +properties:
> + compatible:
> + const: qcom,i2c-pmic
> +
> + reg:
> + description: 7-bit I2C address of the device.
> + maxItems: 1
> +
> + interrupts:
> + description: Summary interrupt specifier.
> +
> + interrupt-controller:
> + description: Flag indicating that this device is an interrupt controller.
> +
> + "#interrupt-cells":
> + description: Number of cells to encode an interrupt source.
> +
> + qcom,periph-map:
> + description: |
> + A contiguous list of u32 arrays where each element specifies the base
> + address of a single peripheral within the chip. This provides a mapping
> + between the summary status register bits and peripheral addresses as each
> + bit in the summary status register represents a peripheral.
> +
> + The number of arrays should match the number of summary registers with up
> + to 8 elements each. Within each array, One element per bit of the summary
> + status register in order from the least sigificant bit to the most
> + significant bit.
> + $ref: /schemas/types.yaml#/definitions/uint32-array
> +
> + pinctrl-names:
> + const: default
> +
> + pinctrl-0:
> + description: phandle of the pin configuration.
> + $ref: /schemas/types.yaml#/definitions/phandle
> +
> +required:
> + - compatible
> + - reg
> +
> +examples:
> + - |
> + qcom,smb138x@8 {
> + compatible = "qcom,i2c-pmic";
> + reg = <0x8>;
> + interrupt-parent = <&tlmm_pinmux>;
> + interrupts = <83 0>;
> + interrupt-controller;
> + #interrupt-cells = <3>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&smb_stat_active>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> + qcom,periph-map = <0x10 0x11 0x12 0x13 0x14 0x16 0x36>;
Please provide examples of this device's children.
> + };
> +
> +...
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2020-04-29 7:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 0:30 [PATCH v1 0/2] Introduce QTI I2C PMIC controller Guru Das Srinagesh
2020-04-29 0:30 ` [PATCH v1 1/2] dt-bindings: mfd: Document " Guru Das Srinagesh
2020-04-29 7:51 ` Lee Jones [this message]
2020-04-29 21:01 ` Rob Herring
2020-04-29 0:30 ` [PATCH v1 2/2] mfd: Introduce " Guru Das Srinagesh
2020-04-29 7:50 ` Lee Jones
2020-05-01 1:13 ` Guru Das Srinagesh
2020-05-01 1:18 ` Joe Perches
2020-05-01 1:28 ` Guru Das Srinagesh
2020-05-15 10:45 ` Lee Jones
2020-05-19 18:57 ` Guru Das Srinagesh
2020-05-20 6:39 ` Lee Jones
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=20200429075149.GY3559@dell \
--to=lee.jones@linaro.org \
--cc=collinsd@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=gurus@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=subbaram@codeaurora.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).