From: muhammed.efecetin.67@gmail.com
To: linux-rockchip@lists.infradead.org
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, heiko@sntech.de,
neil.armstrong@linaro.org, lee@kernel.org, rafael@kernel.org,
efectn@protonmail.com, daniel.lezcano@linaro.org
Subject: [PATCH v3 0/5] Add Khadas MCU and fan control support for Khadas Edge 2
Date: Tue, 21 Oct 2025 17:22:40 +0200 [thread overview]
Message-ID: <cover.1761059314.git.efectn@protonmail.com> (raw)
From: Muhammed Efe Cetin <efectn@protonmail.com>
This patch series adds support for the Khadas MCU and fan control for Khadas Edge 2 board.
The first patch updates the device tree bindings to add new "khadas,mcu-edge2" compatible for Khadas Edge 2.
The second mfd patch removes unused nvmem code.
The third patch adds the Khadas Edge 2 registers to the mfd driver.
The fourth patch adds support for Khadas Edge 2's new fan control registers to MCU thermal driver and the last one adds the Khadas Edge 2 device tree node for the MCU and fan control.
And the final patch adds the Khadas Edge 2 device tree node for the MCU and fan control.
Changes in v3:
- Renamed the compatible "khadas,mcu-v2" to "khadas,mcu-edge2" for Khadas Edge 2.
- Renamed KHADAS_MCU_V2 registers prefix to KHADAS_MCU_EDGE2.
- Used of_device_get_match_data instead of of_device_is_compatible to identify the MCU variant.
Changes in v2:
- Added a new compatible "khadas,mcu-v2" for Khadas Edge 2 instead of cooling-levels property in old variant.
- Added Khadas Edge 2 registers with KHADAS_MCU_EDGE2 prefix.
Muhammed Efe Cetin (5):
dt-bindings: mfd: khadas-mcu: add new compatible for Khadas Edge 2
mfd: khadas-mcu: drop unused nvmem code
mfd: add Khadas Edge 2 registers to khadas-mcu.
thermal: khadas_mcu_fan: add support for Khadas Edge 2
arm64: dts: rockchip: add Khadas MCU and fan control nodes
.../devicetree/bindings/mfd/khadas,mcu.yaml | 5 +-
.../dts/rockchip/rk3588s-khadas-edge2.dts | 58 +++++++++++++++++++
drivers/mfd/khadas-mcu.c | 58 ++++++++++++++-----
drivers/thermal/khadas_mcu_fan.c | 20 +++++--
include/linux/mfd/khadas-mcu.h | 32 ++++++++++
5 files changed, 153 insertions(+), 20 deletions(-)
--
2.51.1.dirty
next reply other threads:[~2025-10-21 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 15:22 muhammed.efecetin.67 [this message]
2025-10-21 15:22 ` [PATCH v3 1/5] dt-bindings: mfd: khadas-mcu: add new compatible for Khadas Edge 2 muhammed.efecetin.67
2025-10-22 17:37 ` Conor Dooley
2025-10-21 15:22 ` [PATCH v3 2/5] mfd: khadas-mcu: drop unused nvmem code muhammed.efecetin.67
2025-10-21 15:22 ` [PATCH v3 3/5] mfd: add Khadas Edge 2 registers to khadas-mcu muhammed.efecetin.67
2025-10-22 7:18 ` kernel test robot
2025-10-23 2:03 ` kernel test robot
2025-10-21 15:22 ` [PATCH v3 4/5] thermal: khadas_mcu_fan: add support for Khadas Edge 2 muhammed.efecetin.67
2025-10-21 15:22 ` [PATCH v3 5/5] arm64: dts: rockchip: add Khadas MCU and fan control nodes muhammed.efecetin.67
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=cover.1761059314.git.efectn@protonmail.com \
--to=muhammed.efecetin.67@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=efectn@protonmail.com \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=rafael@kernel.org \
--cc=robh+dt@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).