From: Changhuang Liang <changhuang.liang@starfivetech.com>
To: Iwona Winiarska <iwona.winiarska@intel.com>,
Guenter Roeck <linux@roeck-us.net>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-hwmon@vger.kernel.org,
Philipp Zabel <p.zabel@pengutronix.de>,
Changhuang Liang <changhuang.liang@starfivetech.com>
Subject: [PATCH v3 0/6] Add StarFive JHB100 PECI support
Date: Thu, 8 Oct 2026 03:06:17 -0700 [thread overview]
Message-ID: <20261008100623.7085-1-changhuang.liang@starfivetech.com> (raw)
Add PECI controller driver for StarFive JHB100 SoC. The driver
supports PECI protocol communication for CPU thermal management.
This series has been tested on the JHB100 EVB1 board.
Changes since v2:
PATCH 2:
- Replace devm_reset_control_get() with devm_reset_control_get_exclusive()
v2: https://lore.kernel.org/all/20260928075956.62298-1-changhuang.liang@starfivetech.com/
v1: https://lore.kernel.org/all/20260903133408.110847-1-changhuang.liang@starfivetech.com/
Changhuang Liang (6):
dt-bindings: peci: Add StarFive JHB100 PECI controller
peci: controller: Add StarFive JHB100 PECI driver
peci: Add support for PECI CC 0x83 retry condition
peci: cpu: Add Intel Granite Rapids support
hwmon: (peci/cputemp) Add support for Granite Rapids (GNR)
hwmon: (peci/dimmtemp) Add support for Granite Rapids (GNR)
.../bindings/peci/starfive,jhb100-peci.yaml | 57 +++
MAINTAINERS | 8 +
drivers/hwmon/peci/cputemp.c | 21 +
drivers/hwmon/peci/dimmtemp.c | 33 +-
drivers/peci/controller/Kconfig | 17 +
drivers/peci/controller/Makefile | 1 +
drivers/peci/controller/peci-starfive.c | 376 ++++++++++++++++++
drivers/peci/cpu.c | 4 +
drivers/peci/request.c | 2 +
9 files changed, 515 insertions(+), 4 deletions(-)
create mode 100644 Documentation/devicetree/bindings/peci/starfive,jhb100-peci.yaml
create mode 100644 drivers/peci/controller/peci-starfive.c
--
2.25.1
next reply other threads:[~2026-10-08 10:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 10:06 Changhuang Liang [this message]
2026-10-08 10:06 ` [PATCH v3 1/6] dt-bindings: peci: Add StarFive JHB100 PECI controller Changhuang Liang
2026-10-08 11:45 ` sashiko-bot
2026-10-08 10:06 ` [PATCH v3 2/6] peci: controller: Add StarFive JHB100 PECI driver Changhuang Liang
2026-10-08 11:52 ` sashiko-bot
2026-10-08 10:06 ` [PATCH v3 3/6] peci: Add support for PECI CC 0x83 retry condition Changhuang Liang
2026-10-08 11:51 ` sashiko-bot
2026-10-08 10:06 ` [PATCH v3 4/6] peci: cpu: Add Intel Granite Rapids support Changhuang Liang
2026-10-08 11:49 ` sashiko-bot
2026-10-08 10:06 ` [PATCH v3 5/6] hwmon: (peci/cputemp) Add support for Granite Rapids (GNR) Changhuang Liang
2026-10-08 11:48 ` sashiko-bot
2026-10-08 10:06 ` [PATCH v3 6/6] hwmon: (peci/dimmtemp) " Changhuang Liang
2026-10-08 11:48 ` sashiko-bot
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=20261008100623.7085-1-changhuang.liang@starfivetech.com \
--to=changhuang.liang@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=iwona.winiarska@intel.com \
--cc=krzk+dt@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=openbmc@lists.ozlabs.org \
--cc=p.zabel@pengutronix.de \
--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