From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: Rob Herring <robh@kernel.org>
Cc: Zhang Rui <rui.zhang@intel.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Amit Kucheria <amit.kucheria@verdurent.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: thermal: Convert UniPhier thermal monitor to json-schema
Date: Thu, 30 Apr 2020 12:00:19 +0900 [thread overview]
Message-ID: <077715ad-f327-a39f-3702-d06d4010d20b@socionext.com> (raw)
In-Reply-To: <20200428162055.GA27628@bogus>
Hi Rob,
On 2020/04/29 1:20, Rob Herring wrote:
> On Thu, Apr 16, 2020 at 02:12:15PM +0900, Kunihiko Hayashi wrote:
>> Convert the UniPhier thermal monitor binding to DT schema format.
>>
>> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
>> ---
>> .../thermal/socionext,uniphier-thermal.yaml | 57 +++++++++++++++++++
>> .../bindings/thermal/uniphier-thermal.txt | 65 ----------------------
>> 2 files changed, 57 insertions(+), 65 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/thermal/socionext,uniphier-thermal.yaml
>> delete mode 100644 Documentation/devicetree/bindings/thermal/uniphier-thermal.txt
>>
>> diff --git a/Documentation/devicetree/bindings/thermal/socionext,uniphier-thermal.yaml b/Documentation/devicetree/bindings/thermal/socionext,uniphier-thermal.yaml
>> new file mode 100644
>> index 0000000..bdddc5b
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/thermal/socionext,uniphier-thermal.yaml
>> @@ -0,0 +1,57 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/thermal/socionext,uniphier-thermal.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Socionext UniPhier thermal monitor
>> +
>> +description: |
>> + This describes the devicetree bindings for thermal monitor supported by
>> + PVT(Process, Voltage and Temperature) monitoring unit implemented on
>> + Socionext UniPhier SoCs.
>> +
>> +maintainers:
>> + - Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
>> +
>> +properties:
>> + compatible:
>> + enum:
>> + - socionext,uniphier-pxs2-thermal
>> + - socionext,uniphier-ld20-thermal
>> + - socionext,uniphier-pxs3-thermal
>> +
>> + interrupts:
>> + maxItems: 1
>> +
>> + "#thermal-sensor-cells":
>> + const: 0
>> +
>> + socionext,tmod-calibration:
>> + $ref: /schemas/types.yaml#/definitions/uint32-array
>> + description:
>> + A pair of calibrated values referred from PVT, in case that the values
>> + aren't set on SoC, like a reference board.
>
> So?:
>
> maxItems: 2
Okay, I'll add that in v2.
Thank you,
---
Best Regards
Kunihiko Hayashi
prev parent reply other threads:[~2020-04-30 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 5:12 [PATCH] dt-bindings: thermal: Convert UniPhier thermal monitor to json-schema Kunihiko Hayashi
2020-04-28 16:20 ` Rob Herring
2020-04-30 3:00 ` Kunihiko Hayashi [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=077715ad-f327-a39f-3702-d06d4010d20b@socionext.com \
--to=hayashi.kunihiko@socionext.com \
--cc=amit.kucheria@verdurent.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.com \
--cc=yamada.masahiro@socionext.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).