From: Sean Anderson <sean.anderson@linux.dev>
To: Michal Simek <michal.simek@amd.com>,
linux-arm-kernel@lists.infradead.org
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Sean Anderson <sean.anderson@linux.dev>
Subject: [PATCH 0/3] arm64: zynqmp: Add thermal zones
Date: Mon, 12 Aug 2024 17:51:25 -0400 [thread overview]
Message-ID: <20240812215129.3599832-1-sean.anderson@linux.dev> (raw)
At the moment, the ZynqMP Analog Monitoring System (AMS) is only used
sporadically. As it is built into the SoC and doesn't depend on external
hardware, it can be exposed to userspace for all boards. Additionally,
we can use it to implement thermal zones.
Sean Anderson (3):
arm64: zynqmp: Enable AMS for all boards
arm64: zynqmp: Expose AMS to userspace as HWMON
arm64: zynqmp: Add thermal zones
.../boot/dts/xilinx/zynqmp-sm-k26-revA.dts | 18 ----
.../boot/dts/xilinx/zynqmp-zcu100-revC.dts | 4 -
.../boot/dts/xilinx/zynqmp-zcu102-revA.dts | 4 -
.../boot/dts/xilinx/zynqmp-zcu104-revA.dts | 4 -
.../boot/dts/xilinx/zynqmp-zcu104-revC.dts | 4 -
arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 101 +++++++++++++++++-
6 files changed, 100 insertions(+), 35 deletions(-)
--
2.35.1.1320.gc452695387.dirty
next reply other threads:[~2024-08-12 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 21:51 Sean Anderson [this message]
2024-08-12 21:51 ` [PATCH 1/3] arm64: zynqmp: Enable AMS for all boards Sean Anderson
2024-08-12 21:51 ` [PATCH 2/3] arm64: zynqmp: Expose AMS to userspace as HWMON Sean Anderson
2024-08-12 21:51 ` [PATCH 3/3] arm64: zynqmp: Add thermal zones Sean Anderson
2024-09-03 8:32 ` Thangaraj, Senthil Nathan
2024-09-03 14:27 ` Sean Anderson
2024-09-09 18:28 ` Thangaraj, Senthil Nathan
2024-09-26 6:55 ` Michal Simek
2024-10-02 10:46 ` [PATCH 0/3] " Michal Simek
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=20240812215129.3599832-1-sean.anderson@linux.dev \
--to=sean.anderson@linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=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 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).