From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: "Aleksandrs Vinarskis" <alex@vinarskis.com>,
"Bjorn Andersson" <andersson@kernel.org>,
"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>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Bryan O'Donoghue" <bryan.odonoghue@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, laurentiu.tudor1@dell.com,
Abel Vesa <abel.vesa@oss.qualcomm.com>,
Tobias Heider <tobias.heider@canonical.com>,
Val Packett <val@packett.cool>
Subject: Re: [PATCH 4/4] arm64: dts: qcom: x1e80100-dell-xps13-9345: introduce EC
Date: Wed, 1 Apr 2026 11:20:48 +0200 [thread overview]
Message-ID: <e9826e27-da9e-4cd5-b368-be3e56f62072@oss.qualcomm.com> (raw)
In-Reply-To: <20260401-dell-xps-9345-ec-v1-4-afa5cacd49be@vinarskis.com>
On 4/1/26 9:33 AM, Aleksandrs Vinarskis wrote:
> Describe embedded controller, its interrupt and required thermal zones.
> Add EC's reset GPIO to reserved range, as triggering it during device
> operation leads to unrecoverable and unusable state.
>
> Signed-off-by: Aleksandrs Vinarskis <alex@vinarskis.com>
> ---
[...]
> + io-channels = <&pmk8550_vadc PM8350_ADC7_GPIO3_100K_PU(1)>,
> + <&pmk8550_vadc PM8350_ADC7_GPIO4_100K_PU(1)>,
> + <&pmk8550_vadc PM8350_ADC7_AMUX_THM1_100K_PU(1)>,
> + <&pmk8550_vadc PM8350_ADC7_AMUX_THM2_100K_PU(1)>,
> + <&pmk8550_vadc PM8350_ADC7_AMUX_THM3_100K_PU(1)>,
> + <&pmk8550_vadc PM8350_ADC7_AMUX_THM4_100K_PU(1)>,
> + <&pmk8550_vadc PM8350_ADC7_AMUX_THM5_100K_PU(1)>;
> +
> + io-channel-names = "sys_therm0", "sys_therm1", "sys_therm2",
> + "sys_therm3", "sys_therm4", "sys_therm5",
> + "sys_therm6";
nit: one a line please, without a separating \n between x and x-names
[...]
> +&pmk8550_vadc {
> + /* sys_therm0, around DRAM */
another nit: I think repeating the name set in the label in each comment
is a little excessive
[...]
> &tlmm {
> gpio-reserved-ranges = <44 4>, /* SPI11 (TPM) */
> + <65 1>, /* EC Reset */
Is that a "this may not be accessed" or rather "you can, but it has dire
consequences"?
Would the EC driver/binding benefit from having a reference to that pin?
Konrad
next prev parent reply other threads:[~2026-04-01 9:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 7:33 [PATCH 0/4] Introduce EC driver for Snapdragon X1E based Dell XPS 13 9345 Aleksandrs Vinarskis
2026-04-01 7:33 ` [PATCH 1/4] dt-bindings: platform: introduce EC for " Aleksandrs Vinarskis
2026-04-02 8:26 ` Krzysztof Kozlowski
2026-04-01 7:33 ` [PATCH 2/4] platform: arm64: dell-xps-ec: new driver Aleksandrs Vinarskis
2026-04-01 9:16 ` Konrad Dybcio
2026-04-01 10:44 ` Ilpo Järvinen
2026-04-01 10:41 ` Ilpo Järvinen
2026-04-01 22:57 ` Bjorn Andersson
2026-04-01 7:33 ` [PATCH 3/4] arm64: dts: qcom: hamoa-pmics: define VADC for pmk8550 Aleksandrs Vinarskis
2026-04-01 9:19 ` Konrad Dybcio
2026-04-01 7:33 ` [PATCH 4/4] arm64: dts: qcom: x1e80100-dell-xps13-9345: introduce EC Aleksandrs Vinarskis
2026-04-01 9:20 ` Konrad Dybcio [this message]
2026-04-02 12:52 ` Aleksandrs Vinarskis
2026-04-07 10:43 ` Konrad Dybcio
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=e9826e27-da9e-4cd5-b368-be3e56f62072@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abel.vesa@oss.qualcomm.com \
--cc=alex@vinarskis.com \
--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=laurentiu.tudor1@dell.com \
--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=tobias.heider@canonical.com \
--cc=val@packett.cool \
/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