From: Florian Fainelli <f.fainelli@gmail.com>
To: Rob Herring <robh@kernel.org>, Stefan Wahren <wahrenst@gmx.net>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Amit Kucheria <amit.kucheria@verdurent.com>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-pm@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Eduardo Valentin <edubezval@gmail.com>,
Eric Anholt <eric@anholt.net>,
bcm-kernel-feedback-list@broadcom.com,
Markus Mayer <mmayer@broadcom.com>,
Zhang Rui <rui.zhang@intel.com>, Chen-Yu Tsai <wens@kernel.org>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/4] dt-bindings: Add BCM2711 thermal
Date: Tue, 5 Nov 2019 20:41:39 -0800 [thread overview]
Message-ID: <fee109e6-fdf8-d132-b390-c2878915fb11@gmail.com> (raw)
In-Reply-To: <20191106042107.GA27699@bogus>
On 11/5/2019 8:21 PM, Rob Herring wrote:
> On Fri, Nov 01, 2019 at 02:42:26PM +0100, Stefan Wahren wrote:
>> Since the BCM2711 doesn't have a AVS TMON block, the thermal information
>> must be retrieved from the AVS ring oscillator block. So add a new
>> suitable binding.
>
> Anything else in that block?
Yes, the register space is quite big, and contains a bunch of raw
sensors (voltage, ring oscillators etc.). It might be more appropriate
to define the ring oscillator node and then use a syscon phandle to it
with the appropriate register offset within that block.
>>
>> Signed-off-by: Stefan Wahren <wahrenst@gmx.net>
>> ---
>> .../bindings/thermal/brcm,bcm2711-thermal.txt | 39 ++++++++++++++++++++++
>> 1 file changed, 39 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/thermal/brcm,bcm2711-thermal.txt
>>
>> diff --git a/Documentation/devicetree/bindings/thermal/brcm,bcm2711-thermal.txt b/Documentation/devicetree/bindings/thermal/brcm,bcm2711-thermal.txt
>> new file mode 100644
>> index 0000000..5531d3f
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/thermal/brcm,bcm2711-thermal.txt
>> @@ -0,0 +1,39 @@
>> +Binding for Thermal Sensor driver for BCM2711 SoCs.
>> +
>> +Required properties:
>> +- compatible: must be: "brcm,bcm2711-thermal"
>
> If the block is called 'AVS ring oscillator', then the compatible name
> should mirror that.
>
>> +- reg: Address range of the thermal registers.
>> +- clocks: Phandle of the clock used by the thermal sensor.
>> +- #thermal-sensor-cells: should be 0 (see thermal.txt)
>> +
>> +Example:
>> +
>> +thermal-zones {
>> + cpu_thermal: cpu-thermal {
>> + polling-delay-passive = <0>;
>> + polling-delay = <1000>;
>> +
>> + thermal-sensors = <&thermal>;
>> +
>> + trips {
>> + cpu-crit {
>> + temperature = <80000>;
>> + hysteresis = <0>;
>> + type = "critical";
>> + };
>> + };
>> +
>> + coefficients = <(-487) 410040>;
>> +
>> + cooling-maps {
>> + };
>> + };
>> +};
>> +
>> +thermal@7d5d2200 {
>> + compatible = "brcm,bcm2711-thermal";
>> + reg = <0x7d5d2200 0x4>;
>> + clocks = <&clocks BCM2835_CLOCK_TSENS>;
>> + #thermal-sensor-cells = <0>;
>> +};
>> +
>> --
>> 2.7.4
>>
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-11-06 4:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 13:42 [PATCH 0/4] ARM: Enable thermal support for Raspberry Pi 4 Stefan Wahren
2019-11-01 13:42 ` [PATCH 1/4] dt-bindings: Add BCM2711 thermal Stefan Wahren
2019-11-06 4:21 ` Rob Herring
2019-11-06 4:41 ` Florian Fainelli [this message]
2019-11-07 19:26 ` Stefan Wahren
2019-11-01 13:42 ` [PATCH 2/4] thermal: Add BCM2711 thermal driver Stefan Wahren
2019-11-01 13:42 ` [PATCH 3/4] ARM: dts: bcm2711: Enable thermal Stefan Wahren
2019-11-01 13:42 ` [PATCH 4/4] ARM: configs: Build BCM2711 thermal as module Stefan Wahren
2019-11-02 20:08 ` [PATCH 0/4] ARM: Enable thermal support for Raspberry Pi 4 Florian Fainelli
2019-11-03 8:43 ` Stefan Wahren
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=fee109e6-fdf8-d132-b390-c2878915fb11@gmail.com \
--to=f.fainelli@gmail.com \
--cc=amit.kucheria@verdurent.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=eric@anholt.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mmayer@broadcom.com \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.com \
--cc=wahrenst@gmx.net \
--cc=wens@kernel.org \
--cc=will@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).