From: Kumar Gala <galak@codeaurora.org>
To: "Ivan T. Ivanov" <ivan.ivanov@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Russell King <linux@arm.linux.org.uk>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 1/7] ARM: dts: qcom: Add PM8841 functions device nodes
Date: Wed, 1 Apr 2015 14:54:59 -0500 [thread overview]
Message-ID: <B79AE5C9-D035-4B0E-A3C4-2648D49F03F3@codeaurora.org> (raw)
In-Reply-To: <1427900715-26273-2-git-send-email-ivan.ivanov@linaro.org>
On Apr 1, 2015, at 10:05 AM, Ivan T. Ivanov <ivan.ivanov@linaro.org> wrote:
> Add configuration nodes for multi purpose pins and
> thermal sensor devices. Thermal sensor will report
> PMIC die temperature.
>
> Signed-off-by: Ivan T. Ivanov <ivan.ivanov@linaro.org>
> ---
> arch/arm/boot/dts/qcom-pm8841.dtsi | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/arch/arm/boot/dts/qcom-pm8841.dtsi b/arch/arm/boot/dts/qcom-pm8841.dtsi
> index 73813cc..5c109bd 100644
> --- a/arch/arm/boot/dts/qcom-pm8841.dtsi
> +++ b/arch/arm/boot/dts/qcom-pm8841.dtsi
> @@ -7,6 +7,20 @@
> reg = <0x4 SPMI_USID>;
> #address-cells = <1>;
> #size-cells = <0>;
> +
> + pm8841_mpps: mpps@a000 {
> + compatible = "qcom,pm8841-mpp";
> + reg = <0xa000 0x400>;
> + gpio-controller;
> + #gpio-cells = <2>;
> + interrupts = <4 0xa0 0 0>, <4 0xa1 0 0>, <4 0xa2 0 0>, <4 0xa3 0 0>;
What’s the interrupt parent here with 4 cells? Can we cleanup the last cell to use proper define for level/edge etc.
> + };
> +
> + temp-alarm@2400 {
> + compatible = "qcom,spmi-temp-alarm";
> + reg = <0x2400 0x100>;
> + interrupts = <4 0x24 0 IRQ_TYPE_EDGE_RISING>;
> + };
> };
>
> usid5: pm8841@5 {
> --
> 1.9.1
>
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-04-01 19:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 15:05 [PATCH 0/7] ARM: dts: qcom: Add more device coniguration nodes Ivan T. Ivanov
2015-04-01 15:05 ` [PATCH 1/7] ARM: dts: qcom: Add PM8841 functions device nodes Ivan T. Ivanov
2015-04-01 19:54 ` Kumar Gala [this message]
2015-04-08 7:07 ` Ivan T. Ivanov
2015-04-01 15:05 ` [PATCH 2/7] ARM: dts: qcom: Add PM8941 " Ivan T. Ivanov
2015-04-01 19:58 ` Kumar Gala
2015-04-01 15:05 ` [PATCH 3/7] ARM: dts: qcom: Add PMA8084 " Ivan T. Ivanov
2015-04-01 15:05 ` [PATCH 4/7] arm64: dts: qcom: Add SPMI PMIC Arbiter node for MSM8916 Ivan T. Ivanov
2015-04-01 19:58 ` Kumar Gala
2015-04-01 15:05 ` [PATCH 5/7] arm64: dts: qcom: Add 8x16 chipset SPMI PMIC's nodes Ivan T. Ivanov
2015-04-01 20:00 ` Kumar Gala
2015-04-01 15:05 ` [PATCH 6/7] arm64: dts: qcom: Add MSM8916 restart device node Ivan T. Ivanov
2015-04-01 15:05 ` [PATCH 7/7] arm64: dts: qcom: Add initial set of PMIC and SoC pins for APQ8016 SBC board Ivan T. Ivanov
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=B79AE5C9-D035-4B0E-A3C4-2648D49F03F3@codeaurora.org \
--to=galak@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ivan.ivanov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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).