From: robh@kernel.org (Rob Herring)
Subject: [PATCH v5 2/4] dt-bindings: thermal: nvme: Add binding documentation
Date: Mon, 22 Jul 2019 16:16:45 -0600 [thread overview]
Message-ID: <20190722221645.GA32515@bogus> (raw)
In-Reply-To: <1561990354-4084-3-git-send-email-akinobu.mita@gmail.com>
On Mon, Jul 01, 2019@11:12:32PM +0900, Akinobu Mita wrote:
> Add thermal binding documentation for NVMe temperature sensor.
>
> Cc: Rob Herring <robh at kernel.org>
> Cc: Zhang Rui <rui.zhang at intel.com>
> Cc: Eduardo Valentin <edubezval at gmail.com>
> Cc: Daniel Lezcano <daniel.lezcano at linaro.org>
> Cc: Keith Busch <kbusch at kernel.org>
> Cc: Jens Axboe <axboe at fb.com>
> Cc: Christoph Hellwig <hch at lst.de>
> Cc: Sagi Grimberg <sagi at grimberg.me>
> Cc: Minwoo Im <minwoo.im.dev at gmail.com>
> Cc: Kenneth Heitke <kenneth.heitke at intel.com>
> Cc: Chaitanya Kulkarni <Chaitanya.Kulkarni at wdc.com>
> Signed-off-by: Akinobu Mita <akinobu.mita at gmail.com>
> ---
> * v5
> - New patch
>
> Documentation/devicetree/bindings/thermal/nvme.txt | 56 ++++++++++++++++++++++
> 1 file changed, 56 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/thermal/nvme.txt
>
> diff --git a/Documentation/devicetree/bindings/thermal/nvme.txt b/Documentation/devicetree/bindings/thermal/nvme.txt
> new file mode 100644
> index 0000000..60b90de
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/thermal/nvme.txt
> @@ -0,0 +1,56 @@
> +Binding for NVMe temperature sensor
> +
> +An NVMe controller reports up to nine temperature values in the SMART / Health
> +log.
> +
> +Required properties:
> +- reg: A five-cell address encoded as (phys.hi phys.mid phys.lo size.hi
> + size.lo). phys.hi should contain the device's BDF (Bus/Device/Function)
> + as 0b00000000 bbbbbbbb dddddfff 00000000. The other cells should be zero.
> + See also Documentation/devicetree/bindings/pci/pci.txt
> +
> +- #thermal-sensor-cells: Must be 1. See ./thermal.txt for a description.
> + In the thermal-sensors property, the sensor ID 0 for composite temperature,
> + 1 through 8 for NVMe temperature sensor N.
> +
> +Example:
> +
> +&pcie0 {
> + ...
> + nvme: nvme at 0,0 {
> + reg = <0x0000 0 0 0 0>;
> + #address-cells = <3>;
> + #size-cells = <2>;
> +
> + nvmetemp: nvmetemp {
> + reg = <0x0000 0 0 0 0>; /* DEVFN = 0x00 (0:0) */
I'm not sure this is really valid PCI addressing as the parent has the
same address.
> + #thermal-sensor-cells = <1>;
Can't you just put this in the parent? Is this really a separate
addressable device from the parent?
> + };
> + };
> +};
> +
> +&thermal_zones {
> + nvme_thermal: nvme {
> + polling-delay-passive = <2000>; /* milliseconds */
> + polling-delay = <0>; /* asynchronous event driven */
> +
> + /* sensor ID */
> + thermal-sensors = <&nvmetemp 0>;
> +
> + trips {
> + nvme_alert0: nvme_alert0 {
> + temperature = <80000>; /* millicelsius */
> + hysteresis = <2000>; /* millicelsius */
> + type = "passive";
> + };
> + };
> +
> + cooling-maps {
> + map0 {
> + trip = <&nvme_alert0>;
> + cooling-device =
> + <&fan0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>;
> + };
> + };
> + };
> +};
> --
> 2.7.4
>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: linux-nvme@lists.infradead.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, Zhang Rui <rui.zhang@intel.com>,
Eduardo Valentin <edubezval@gmail.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Minwoo Im <minwoo.im.dev@gmail.com>,
Kenneth Heitke <kenneth.heitke@intel.com>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Subject: Re: [PATCH v5 2/4] dt-bindings: thermal: nvme: Add binding documentation
Date: Mon, 22 Jul 2019 16:16:45 -0600 [thread overview]
Message-ID: <20190722221645.GA32515@bogus> (raw)
In-Reply-To: <1561990354-4084-3-git-send-email-akinobu.mita@gmail.com>
On Mon, Jul 01, 2019 at 11:12:32PM +0900, Akinobu Mita wrote:
> Add thermal binding documentation for NVMe temperature sensor.
>
> Cc: Rob Herring <robh@kernel.org>
> Cc: Zhang Rui <rui.zhang@intel.com>
> Cc: Eduardo Valentin <edubezval@gmail.com>
> Cc: Daniel Lezcano <daniel.lezcano@linaro.org>
> Cc: Keith Busch <kbusch@kernel.org>
> Cc: Jens Axboe <axboe@fb.com>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Sagi Grimberg <sagi@grimberg.me>
> Cc: Minwoo Im <minwoo.im.dev@gmail.com>
> Cc: Kenneth Heitke <kenneth.heitke@intel.com>
> Cc: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
> Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
> ---
> * v5
> - New patch
>
> Documentation/devicetree/bindings/thermal/nvme.txt | 56 ++++++++++++++++++++++
> 1 file changed, 56 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/thermal/nvme.txt
>
> diff --git a/Documentation/devicetree/bindings/thermal/nvme.txt b/Documentation/devicetree/bindings/thermal/nvme.txt
> new file mode 100644
> index 0000000..60b90de
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/thermal/nvme.txt
> @@ -0,0 +1,56 @@
> +Binding for NVMe temperature sensor
> +
> +An NVMe controller reports up to nine temperature values in the SMART / Health
> +log.
> +
> +Required properties:
> +- reg: A five-cell address encoded as (phys.hi phys.mid phys.lo size.hi
> + size.lo). phys.hi should contain the device's BDF (Bus/Device/Function)
> + as 0b00000000 bbbbbbbb dddddfff 00000000. The other cells should be zero.
> + See also Documentation/devicetree/bindings/pci/pci.txt
> +
> +- #thermal-sensor-cells: Must be 1. See ./thermal.txt for a description.
> + In the thermal-sensors property, the sensor ID 0 for composite temperature,
> + 1 through 8 for NVMe temperature sensor N.
> +
> +Example:
> +
> +&pcie0 {
> + ...
> + nvme: nvme@0,0 {
> + reg = <0x0000 0 0 0 0>;
> + #address-cells = <3>;
> + #size-cells = <2>;
> +
> + nvmetemp: nvmetemp {
> + reg = <0x0000 0 0 0 0>; /* DEVFN = 0x00 (0:0) */
I'm not sure this is really valid PCI addressing as the parent has the
same address.
> + #thermal-sensor-cells = <1>;
Can't you just put this in the parent? Is this really a separate
addressable device from the parent?
> + };
> + };
> +};
> +
> +&thermal_zones {
> + nvme_thermal: nvme {
> + polling-delay-passive = <2000>; /* milliseconds */
> + polling-delay = <0>; /* asynchronous event driven */
> +
> + /* sensor ID */
> + thermal-sensors = <&nvmetemp 0>;
> +
> + trips {
> + nvme_alert0: nvme_alert0 {
> + temperature = <80000>; /* millicelsius */
> + hysteresis = <2000>; /* millicelsius */
> + type = "passive";
> + };
> + };
> +
> + cooling-maps {
> + map0 {
> + trip = <&nvme_alert0>;
> + cooling-device =
> + <&fan0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>;
> + };
> + };
> + };
> +};
> --
> 2.7.4
>
next prev parent reply other threads:[~2019-07-22 22:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 14:12 [PATCH v5 0/4] nvme: add thermal zone devices Akinobu Mita
2019-07-01 14:12 ` Akinobu Mita
2019-07-01 14:12 ` [PATCH v5 1/4] " Akinobu Mita
2019-07-01 14:12 ` Akinobu Mita
2019-07-01 14:12 ` [PATCH v5 2/4] dt-bindings: thermal: nvme: Add binding documentation Akinobu Mita
2019-07-01 14:12 ` Akinobu Mita
2019-07-22 22:16 ` Rob Herring [this message]
2019-07-22 22:16 ` Rob Herring
2019-07-25 14:24 ` Akinobu Mita
2019-07-25 14:24 ` Akinobu Mita
2019-07-25 22:46 ` Rob Herring
2019-07-25 22:46 ` Rob Herring
2019-07-01 14:12 ` [PATCH v5 3/4] nvme: support DT thermal zone device Akinobu Mita
2019-07-01 14:12 ` Akinobu Mita
2019-07-01 14:12 ` [PATCH v5 4/4] nvme: notify thermal framework when temperature threshold events occur Akinobu Mita
2019-07-01 14:12 ` Akinobu Mita
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=20190722221645.GA32515@bogus \
--to=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.