From: Changhuang Liang <changhuang.liang@starfivetech.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Iwona Winiarska <iwona.winiarska@intel.com>,
Guenter Roeck <linux@roeck-us.net>
Cc: 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 v1 3/6] peci: Add support for PECI CC 0x83 retry condition
Date: Thu, 3 Sep 2026 06:34:05 -0700 [thread overview]
Message-ID: <20260903133408.110847-4-changhuang.liang@starfivetech.com> (raw)
In-Reply-To: <20260903133408.110847-1-changhuang.liang@starfivetech.com>
Some PECI client devices may return completion code 0x83 (CMD_TIMEOUT)
under certain conditions, which is not currently handled by the driver.
Add PECI_CC_CMD_TIMEOUT definition and map it to -EAGAIN so that the
request will be retried appropriately, similar to other retryable
completion codes (0x80, 0x81, 0x82).
Signed-off-by: Changhuang Liang <changhuang.liang@starfivetech.com>
---
drivers/peci/request.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/peci/request.c b/drivers/peci/request.c
index db2cc30a42a4..2bf8b6a255d4 100644
--- a/drivers/peci/request.c
+++ b/drivers/peci/request.c
@@ -71,6 +71,7 @@
#define PECI_CC_NEED_RETRY 0x80
#define PECI_CC_OUT_OF_RESOURCE 0x81
#define PECI_CC_UNAVAIL_RESOURCE 0x82
+#define PECI_CC_CMD_TIMEOUT 0x83
#define PECI_CC_INVALID_REQ 0x90
#define PECI_CC_MCA_ERROR 0x91
#define PECI_CC_CATASTROPHIC_MCA_ERROR 0x93
@@ -112,6 +113,7 @@ int peci_request_status(struct peci_request *req)
case PECI_CC_NEED_RETRY:
case PECI_CC_OUT_OF_RESOURCE:
case PECI_CC_UNAVAIL_RESOURCE:
+ case PECI_CC_CMD_TIMEOUT:
return -EAGAIN;
case PECI_CC_INVALID_REQ:
return -EINVAL;
--
2.25.1
next prev parent reply other threads:[~2026-09-03 13:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 13:34 [PATCH v1 0/6] Add StarFive JHB100 PECI support Changhuang Liang
2026-09-03 13:34 ` [PATCH v1 1/6] dt-bindings: peci: Add StarFive JHB100 PECI controller Changhuang Liang
2026-09-03 16:35 ` Conor Dooley
2026-09-03 13:34 ` [PATCH v1 2/6] peci: controller: Add StarFive JHB100 PECI driver Changhuang Liang
2026-09-03 13:34 ` Changhuang Liang [this message]
2026-09-03 13:34 ` [PATCH v1 4/6] peci: cpu: Add Intel Granite Rapids support Changhuang Liang
2026-09-03 13:34 ` [PATCH v1 5/6] hwmon: (peci/cputemp) Add support for Granite Rapids (GNR) Changhuang Liang
2026-09-03 13:34 ` [PATCH v1 6/6] hwmon: (peci/dimmtemp) " Changhuang Liang
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=20260903133408.110847-4-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