From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Hans de Goede <hansg@kernel.org>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Guenter Roeck <linux@roeck-us.net>,
Bjorn Andersson <andersson@kernel.org>,
Abel Vesa <abelvesa@kernel.org>,
devicetree@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
platform-driver-x86@vger.kernel.org,
linux-hwmon@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3 2/3] platform: arm64: Add a driver for the EC found on ASUS Glymur machines
Date: Wed, 14 Oct 2026 21:20:21 +0300 (EEST) [thread overview]
Message-ID: <81e7e5b7-247b-b57f-5d78-4fac468ab121@linux.intel.com> (raw)
In-Reply-To: <5c87c231-6c76-4363-9f4d-6c43dd63ee9f@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]
On Wed, 14 Oct 2026, Konrad Dybcio wrote:
> On 10/8/26 1:28 PM, Ilpo Järvinen wrote:
> > On Wed, 23 Sep 2026, Konrad Dybcio wrote:
> >
> >> From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
> >>
> >> Some Qualcomm Snapdragon X2 Elite (Extreme)-based ASUS laptops (at
> >> least the Zenbook A14 and A16) expose a custom, somewhat
> >> Qualcomm reference-derived EC interface. Introduce a driver to
> >> communicate with said EC, allowing for fan speed reporting, keyboard
> >> backlight setting and receiving of a number of miscellaneous sideband
> >> events.
>
> [...]
>
>
> >> + ret = asus_qcom_ec_write(ec, ASUS_QCOM_EC_RECM_OFFS, frame,
> >> + ASUS_QCOM_EC_RECM_FRAME_LEN);
> >> + if (ret < 0)
> >> + return ret;
> >> +
> >> + ret = asus_qcom_ec_read(ec, ASUS_QCOM_EC_RECM_OFFS, resp,
> >> + ASUS_QCOM_EC_RECM_FRAME_LEN);
> >> + if (ret < 0)
> >> + return ret;
> >> +
> >> + *out = (count == 2) ? get_unaligned_le16(resp) : resp[0];
> >
> > Same problem here when it comes to sparse.
> >
> > Does the ec really input be16 and output le16?
>
> Yep, it really does..
I suggest you mention it in a comment then, as otherwise somebody else
might wonder the same thing. :-)
> Ack for the other comments
>
> Konrad
>
--
i.
next prev parent reply other threads:[~2026-10-14 18:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 10:14 [PATCH v3 0/3] Asus Zenbook A16/A14 (UX3607OA/UX3407NA) EC driver Konrad Dybcio
2026-09-23 10:14 ` [PATCH v3 1/3] dt-bindings: embedded-controller: Add ASUS Zenbook A16 EC Konrad Dybcio
2026-09-23 10:18 ` sashiko-bot
2026-09-28 10:37 ` Krzysztof Kozlowski
2026-09-23 10:14 ` [PATCH v3 2/3] platform: arm64: Add a driver for the EC found on ASUS Glymur machines Konrad Dybcio
2026-09-23 10:24 ` sashiko-bot
2026-10-08 11:28 ` Ilpo Järvinen
2026-10-14 14:37 ` Konrad Dybcio
2026-10-14 18:20 ` Ilpo Järvinen [this message]
2026-09-23 10:14 ` [PATCH v3 3/3] arm64: dts: qcom: glymur-zenbook-a16: Add Embedded Controller Konrad Dybcio
2026-09-23 10:19 ` 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=81e7e5b7-247b-b57f-5d78-4fac468ab121@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=abelvesa@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=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=platform-driver-x86@vger.kernel.org \
--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 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.