From: "Winiarska, Iwona" <iwona.winiarska@intel.com>
To: "linux@roeck-us.net" <linux@roeck-us.net>,
"changhuang.liang@starfivetech.com"
<changhuang.liang@starfivetech.com>
Cc: "linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: [PATCH v3 3/6] peci: Add support for PECI CC 0x83 retry condition
Date: Fri, 16 Oct 2026 20:09:28 +0000 [thread overview]
Message-ID: <42f38dc38a17ac35f97f68cea58c2540e4727578.camel@intel.com> (raw)
In-Reply-To: <20261008100623.7085-4-changhuang.liang@starfivetech.com>
On Thu, 2026-10-08 at 03:06 -0700, Changhuang Liang wrote:
> Some PECI client devices may return completion code 0x83, this
> completion code means that a command response is in progress, which
> is not currently handled by the driver.
>
> Add PECI_CC_RESP_IN_PROGRESS 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>
Reviewed-by: Iwona Winiarska <iwona.winiarska@intel.com>
Thanks
-Iwona
> ---
> drivers/peci/request.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/peci/request.c b/drivers/peci/request.c
> index db2cc30a42a4..bf80bd205e60 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_RESP_IN_PROGRESS 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_RESP_IN_PROGRESS:
> return -EAGAIN;
> case PECI_CC_INVALID_REQ:
> return -EINVAL;
next prev parent reply other threads:[~2026-10-16 20:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 10:06 [PATCH v3 0/6] Add StarFive JHB100 PECI support Changhuang Liang
2026-10-08 10:06 ` [PATCH v3 1/6] dt-bindings: peci: Add StarFive JHB100 PECI controller Changhuang Liang
2026-10-16 20:08 ` Winiarska, Iwona
2026-10-08 10:06 ` [PATCH v3 2/6] peci: controller: Add StarFive JHB100 PECI driver Changhuang Liang
2026-10-16 20:09 ` Winiarska, Iwona
2026-10-08 10:06 ` [PATCH v3 3/6] peci: Add support for PECI CC 0x83 retry condition Changhuang Liang
2026-10-16 20:09 ` Winiarska, Iwona [this message]
2026-10-08 10:06 ` [PATCH v3 4/6] peci: cpu: Add Intel Granite Rapids support Changhuang Liang
2026-10-16 20:09 ` Winiarska, Iwona
2026-10-08 10:06 ` [PATCH v3 5/6] hwmon: (peci/cputemp) Add support for Granite Rapids (GNR) Changhuang Liang
2026-10-16 20:10 ` Winiarska, Iwona
2026-10-08 10:06 ` [PATCH v3 6/6] hwmon: (peci/dimmtemp) " Changhuang Liang
2026-10-16 20:10 ` Winiarska, Iwona
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=42f38dc38a17ac35f97f68cea58c2540e4727578.camel@intel.com \
--to=iwona.winiarska@intel.com \
--cc=changhuang.liang@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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
all inboxes | Powered by JetHome®