From: Stefan Wahren <wahrenst@gmx.net>
To: Zhang Rui <rui.zhang@intel.com>,
Eduardo Valentin <edubezval@gmail.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Amit Kucheria <amit.kucheria@verdurent.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Eric Anholt <eric@anholt.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Markus Mayer <mmayer@broadcom.com>
Cc: devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
Stefan Wahren <wahrenst@gmx.net>, Chen-Yu Tsai <wens@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM: Enable thermal support for Raspberry Pi 4
Date: Fri, 1 Nov 2019 14:42:25 +0100 [thread overview]
Message-ID: <1572615749-9524-1-git-send-email-wahrenst@gmx.net> (raw)
This series enables thermal support for the Raspberry Pi 4. Neither the
bcm2835_thermal nor the brcmstb_thermal are suitable for the BCM2711.
So add a new thermal driver to read out the SoC temperature from the
AVS RO block of the BCM2711.
Stefan Wahren (4):
dt-bindings: Add BCM2711 thermal
thermal: Add BCM2711 thermal driver
ARM: dts: bcm2711: Enable thermal
ARM: configs: Build BCM2711 thermal as module
.../bindings/thermal/brcm,bcm2711-thermal.txt | 39 ++++++
arch/arm/boot/dts/bcm2711.dtsi | 9 ++
arch/arm/configs/multi_v7_defconfig | 1 +
arch/arm64/configs/defconfig | 1 +
drivers/thermal/broadcom/Kconfig | 8 ++
drivers/thermal/broadcom/Makefile | 1 +
drivers/thermal/broadcom/bcm2711_thermal.c | 146 +++++++++++++++++++++
7 files changed, 205 insertions(+)
create mode 100644 Documentation/devicetree/bindings/thermal/brcm,bcm2711-thermal.txt
create mode 100644 drivers/thermal/broadcom/bcm2711_thermal.c
--
2.7.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-11-01 13:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 13:42 Stefan Wahren [this message]
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
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=1572615749-9524-1-git-send-email-wahrenst@gmx.net \
--to=wahrenst@gmx.net \
--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=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mmayer@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--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).