From: Krzysztof Kozlowski <krzk@kernel.org>
To: Anvesh Jain P <anvesh.p@oss.qualcomm.com>
Cc: Sibi Sankar <sibi.sankar@oss.qualcomm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: embedded-controller: qcom,hamoa-crd-ec: Add Purwa IOT EVK
Date: Sun, 5 Jul 2026 11:45:41 +0200 [thread overview]
Message-ID: <20260705-sensible-agile-kagu-df3b78@quoll> (raw)
In-Reply-To: <20260703-ec_support_for_purwa_evk-v2-1-c59aac5c6aac@oss.qualcomm.com>
On Fri, Jul 03, 2026 at 03:23:41PM +0530, Anvesh Jain P wrote:
> Document the qcom,purwa-iot-evk-ec compatible for the embedded controller
> found on Purwa IOT EVK boards.
>
> Like the CRD, the Purwa IOT EVK carries an on-board embedded controller,
> provided by ITE and running on a separate MCU, which handles fan control,
> temperature sensors and EC state-change/suspend notifications. The existing
> Hamoa IOT EVK documents the same EC via qcom,hamoa-iot-evk-ec.
>
> Like the other reference designs, it uses qcom,hamoa-crd-ec as its fallback
> compatible.
>
> Signed-off-by: Anvesh Jain P <anvesh.p@oss.qualcomm.com>
> ---
> .../devicetree/bindings/embedded-controller/qcom,hamoa-crd-ec.yaml | 1 +
> 1 file changed, 1 insertion(+)
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-07-05 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 9:53 [PATCH v2 0/2] Add EC support for Purwa IOT EVK Anvesh Jain P
2026-07-03 9:53 ` [PATCH v2 1/2] dt-bindings: embedded-controller: qcom,hamoa-crd-ec: Add " Anvesh Jain P
2026-07-05 9:45 ` Krzysztof Kozlowski [this message]
2026-07-03 9:53 ` [PATCH v2 2/2] arm64: dts: qcom: purwa-iot-evk: Add Embedded controller node Anvesh Jain P
2026-07-03 10:07 ` 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=20260705-sensible-agile-kagu-df3b78@quoll \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=anvesh.p@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sibi.sankar@oss.qualcomm.com \
/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