All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sibi Sankar <sibi.sankar@oss.qualcomm.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, andersson@kernel.org,
	konradybcio@kernel.org, bryan.odonoghue@linaro.org,
	ilpo.jarvinen@linux.intel.com, hansg@kernel.org,
	conor+dt@kernel.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH V3 4/5] arm64: dts: qcom: x1-crd: Add Embedded controller node
Date: Mon, 9 Mar 2026 10:09:20 +0100	[thread overview]
Message-ID: <3eaceb96-003b-47d2-9ae5-bb676dde0240@kernel.org> (raw)
In-Reply-To: <ff241b01-c7f4-433b-a822-c5cd14e3e696@oss.qualcomm.com>

On 09/03/2026 10:03, Sibi Sankar wrote:
> 
> On 3/9/2026 12:55 PM, Krzysztof Kozlowski wrote:
>> On Mon, Mar 09, 2026 at 05:06:45AM +0530, Sibi Sankar wrote:
>>> Add embedded controller node for Hamoa/Purwa CRDs which adds fan control,
>>> temperature sensors, access to EC internal state changes and suspend
>>> entry/exit notifications to the EC.
>>>
>>> Signed-off-by: Sibi Sankar <sibi.sankar@oss.qualcomm.com>
>>> ---
>>>   arch/arm64/boot/dts/qcom/x1-crd.dtsi | 16 ++++++++++++++++
>>>   1 file changed, 16 insertions(+)
>>>
>>> diff --git a/arch/arm64/boot/dts/qcom/x1-crd.dtsi b/arch/arm64/boot/dts/qcom/x1-crd.dtsi
>>> index ded96fb43489..29a1aeb98353 100644
>>> --- a/arch/arm64/boot/dts/qcom/x1-crd.dtsi
>>> +++ b/arch/arm64/boot/dts/qcom/x1-crd.dtsi
>>> @@ -1042,6 +1042,16 @@ eusb6_repeater: redriver@4f {
>>>   
>>>   		#phy-cells = <0>;
>>>   	};
>>> +
>>> +	embedded-controller@76 {
>>> +		compatible = "qcom,hamoa-it8987-ec", "qcom,hamoa-ec";
>> I don't see updates to other x1e boards, thus my arguments from v2 stay
>> valid. It's wrong to call it "hamoa-ec" since only one Hamoa board has
>> it. All of other Hamoa boards apparently do not have it.
> 
> 
> Hey Krzysztof,
> Thanks for taking time to review the series :)
> 
> What other Hamoa boards are you referring to? The series
> mentions that the driver and bindings is meant for Qualcomm
> Hamoa/Purwa/Glymur "reference" devices, so it only covers
> CRD and IOT-EVK. It definitely does not cover all Hamoa boards
> boards like you are assuming.

hamoa-ec compatible implies that and that's something I raised in v2
already. You need a specific compatible.


Best regards,
Krzysztof

  reply	other threads:[~2026-03-09  9:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-08 23:36 [PATCH V3 0/5] Add driver for EC found on Qualcomm reference devices Sibi Sankar
2026-03-08 23:36 ` [PATCH V3 1/5] dt-bindings: embedded-controller: Add EC bindings for " Sibi Sankar
2026-03-09  7:23   ` Krzysztof Kozlowski
2026-03-09 11:35     ` Sibi Sankar
2026-03-09 21:06   ` Dmitry Baryshkov
2026-03-10  5:10     ` Sibi Sankar
2026-03-08 23:36 ` [PATCH V3 2/5] platform: arm64: Add driver for EC found on " Sibi Sankar
2026-03-09  9:03   ` Stephan Gerhold
2026-03-09 10:04     ` Sibi Sankar
2026-03-09 11:47       ` Konrad Dybcio
2026-03-09 11:55         ` Stephan Gerhold
2026-03-09 12:10           ` Konrad Dybcio
2026-03-10  4:58             ` Sibi Sankar
2026-03-16 10:33               ` Konrad Dybcio
2026-03-10  6:18   ` kernel test robot
2026-03-10  6:29   ` kernel test robot
2026-03-08 23:36 ` [PATCH V3 3/5] arm64: dts: qcom: glymur-crd: Add Embedded controller node Sibi Sankar
2026-03-08 23:36 ` [PATCH V3 4/5] arm64: dts: qcom: x1-crd: " Sibi Sankar
2026-03-09  7:25   ` Krzysztof Kozlowski
2026-03-09  9:03     ` Sibi Sankar
2026-03-09  9:09       ` Krzysztof Kozlowski [this message]
2026-03-09 10:51         ` Sibi Sankar
2026-03-09 10:53           ` Krzysztof Kozlowski
2026-03-09 11:48             ` Konrad Dybcio
2026-03-10  7:10               ` Krzysztof Kozlowski
2026-03-09 11:50             ` Sibi Sankar
2026-03-09 21:13           ` Dmitry Baryshkov
2026-03-10  5:11             ` Sibi Sankar
2026-03-10  9:45             ` Konrad Dybcio
2026-03-08 23:36 ` [PATCH V3 5/5] arm64: dts: qcom: hamoa-iot-evk: " Sibi Sankar

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=3eaceb96-003b-47d2-9ae5-bb676dde0240@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.