From: Amit Kucheria <amit.kucheria@linaro.org>
To: Manaf Meethalavalappu Pallikunhi <manafm@codeaurora.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Zhang Rui <rui.zhang@intel.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
DTML <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] dt-bindings: thermal: tsens: Add zeroc interrupt support in yaml
Date: Tue, 5 May 2020 17:41:55 +0530 [thread overview]
Message-ID: <CAP245DX2=bY4kCERgnm_L26o9mY7CoOZRScXmXwfe-bAYczOnQ@mail.gmail.com> (raw)
In-Reply-To: <20200505111204.963-3-manafm@codeaurora.org>
On Tue, May 5, 2020 at 4:43 PM Manaf Meethalavalappu Pallikunhi
<manafm@codeaurora.org> wrote:
>
> Add 0C (zeroc) interrupt support for tsens in yaml.
>
> Signed-off-by: Manaf Meethalavalappu Pallikunhi <manafm@codeaurora.org>
> ---
> Documentation/devicetree/bindings/thermal/qcom-tsens.yaml | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/thermal/qcom-tsens.yaml b/Documentation/devicetree/bindings/thermal/qcom-tsens.yaml
> index 2ddd39d96766..8a0893f77d20 100644
> --- a/Documentation/devicetree/bindings/thermal/qcom-tsens.yaml
> +++ b/Documentation/devicetree/bindings/thermal/qcom-tsens.yaml
> @@ -52,12 +52,14 @@ properties:
> items:
> - description: Combined interrupt if upper or lower threshold crossed
> - description: Interrupt if critical threshold crossed
> + - description: Interrupt if zeroC threshold is crossed
>
> interrupt-names:
> minItems: 1
> items:
> - const: uplow
> - const: critical
> + - const: zeroc
>
> nvmem-cells:
> minItems: 1
> @@ -168,8 +170,9 @@ examples:
> <0xc222000 0x1ff>;
>
> interrupts = <GIC_SPI 506 IRQ_TYPE_LEVEL_HIGH>,
> - <GIC_SPI 508 IRQ_TYPE_LEVEL_HIGH>;
> - interrupt-names = "uplow", "critical";
> + <GIC_SPI 508 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 510 IRQ_TYPE_EDGE_RISING>;
> + interrupt-names = "uplow", "critical", "zeroc";
Add a new example for v2 with 0C interrupt here instead of reusing the old one.
> #qcom,sensors = <13>;
> #thermal-sensor-cells = <1>;
> --
> 2.26.2
next prev parent reply other threads:[~2020-05-05 12:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 11:12 [PATCH 0/2] Add 0C (zeorC) interrupt support to tsens driver Manaf Meethalavalappu Pallikunhi
2020-05-05 11:12 ` [PATCH 1/2] drivers: thermal: tsens: Add 0C (zeorC) interrupt support Manaf Meethalavalappu Pallikunhi
2020-05-05 12:09 ` Amit Kucheria
2020-05-17 10:28 ` manafm
2020-05-18 15:33 ` Amit Kucheria
2020-05-05 11:12 ` [PATCH 2/2] dt-bindings: thermal: tsens: Add zeroc interrupt support in yaml Manaf Meethalavalappu Pallikunhi
2020-05-05 12:11 ` Amit Kucheria [this message]
2020-05-17 10:30 ` manafm
2020-05-05 15:38 ` Rob Herring
2020-05-17 10:32 ` manafm
2020-05-05 12:12 ` [PATCH 0/2] Add 0C (zeorC) interrupt support to tsens driver Amit Kucheria
2020-05-17 10:30 ` manafm
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='CAP245DX2=bY4kCERgnm_L26o9mY7CoOZRScXmXwfe-bAYczOnQ@mail.gmail.com' \
--to=amit.kucheria@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=manafm@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
/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).