From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Abel Vesa <abel.vesa@oss.qualcomm.com>
Cc: "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>,
"Rajendra Nayak" <quic_rjendra@quicinc.com>,
"Abel Vesa" <abelvesa@kernel.org>,
"Sibi Sankar" <sibi.sankar@oss.qualcomm.com>,
"Marc Zyngier" <maz@kernel.org>,
"Aleksandrs Vinarskis" <alex.vinarskis@gmail.com>,
"Konstantin Shabanov" <mail@etehtsea.me>,
"Srinivas Kandagatla" <srini@kernel.org>,
"Ettore Chimenti" <ettore.chimenti@linaro.org>,
"Georg Gottleuber" <ggo@tuxedocomputers.com>,
"Xilin Wu" <wuxilin123@gmail.com>,
"Bryan O'Donoghue" <bryan.odonoghue@linaro.org>,
"Val Packett" <val@packett.cool>,
"Laurentiu Tudor" <laurentiu.tudor1@dell.com>,
"Jens Glathe" <jens.glathe@oldschoolsolutions.biz>,
"Dale Whinham" <daleyo@gmail.com>,
"Jérôme de Bretagne" <jerome.debretagne@gmail.com>,
"Harrison Vanderbyl" <harrison.vanderbyl@gmail.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Konrad Dybcio" <quic_kdybcio@quicinc.com>
Subject: Re: [PATCH v2 01/16] arm64: dts: qcom: x1-crd: Mark the EC reset gpio as reserved
Date: Thu, 3 Sep 2026 11:16:20 +0200 [thread overview]
Message-ID: <182336df-b505-4ae4-901f-e09c0eae80ed@oss.qualcomm.com> (raw)
In-Reply-To: <ygyu3t7o2p2xvm3j5wrxp4svzo2rzymvzgod2szhz4z57elc7a@hznrw2e35oen>
On 9/3/26 10:34 AM, Abel Vesa wrote:
> On 26-09-02 17:53:23, Konrad Dybcio wrote:
>> On 9/1/26 10:06 AM, Abel Vesa wrote:
>>> GPIO 65 from TLMM is used by the embedded controller as its reset line.
>>>
>>> On some devices, toggling the embedded controller reset line makes the
>>> device not power up at all, unless the battery is unplugged.
>>
>> Have you confirmed that behavior on the CRD?
>
> Toggling it does nothing observable.
>
> However, the documentation says this GPIO is actually tied to EC reset.
>
> I still think we should reserve it, just to be safe.
>
> What do you think?
I believe that contradicts the reasoning you gave in the commit
message then..
Konrad
next prev parent reply other threads:[~2026-09-03 9:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 8:06 [PATCH v2 00/16] arm64: dts: qcom: hamoa: Mark the EC reset gpio as reserved on all boards Abel Vesa
2026-09-01 8:06 ` [PATCH v2 01/16] arm64: dts: qcom: x1-crd: Mark the EC reset gpio as reserved Abel Vesa
2026-09-02 15:53 ` Konrad Dybcio
2026-09-03 8:34 ` Abel Vesa
2026-09-03 9:16 ` Konrad Dybcio [this message]
2026-09-03 9:29 ` Abel Vesa
2026-09-03 9:37 ` Konrad Dybcio
2026-09-03 10:28 ` Abel Vesa
2026-09-01 8:06 ` [PATCH v2 02/16] arm64: dts: qcom: x1e001de-devkit: " Abel Vesa
2026-09-01 8:07 ` [PATCH v2 03/16] arm64: dts: qcom: x1e78100-t14s: " Abel Vesa
2026-09-01 8:07 ` [PATCH v2 04/16] arm64: dts: qcom: x1e80100-dell-xps13-9345: " Abel Vesa
2026-09-01 8:07 ` [PATCH v2 05/16] arm64: dts: qcom: honor-magicbook-art-14: " Abel Vesa
2026-09-01 8:07 ` [PATCH v2 06/16] arm64: dts: qcom: x1e80100-yoga-slim7x: " Abel Vesa
2026-09-01 8:07 ` [PATCH v2 07/16] arm64: dts: qcom: medion-sprchrgd-14-s1: " Abel Vesa
2026-09-01 8:07 ` [PATCH v2 08/16] arm64: dts: qcom: microsoft-romulus: " Abel Vesa
2026-09-02 15:50 ` Konrad Dybcio
2026-09-03 8:35 ` Abel Vesa
2026-09-01 8:07 ` [PATCH v2 09/16] arm64: dts: qcom: x1e80100-qcp: " Abel Vesa
2026-09-01 8:07 ` [PATCH v2 10/16] arm64: dts: qcom: x1-asus-vivobook-s15: " Abel Vesa
2026-09-01 8:07 ` [PATCH v2 11/16] arm64: dts: qcom: x1-asus-zenbook-a14: " Abel Vesa
2026-09-01 8:07 ` [PATCH v2 12/16] arm64: dts: qcom: x1-dell-thena: " Abel Vesa
2026-09-01 8:07 ` [PATCH v2 13/16] arm64: dts: qcom: x1-hp-omnibook-x14: " Abel Vesa
2026-09-01 8:07 ` [PATCH v2 14/16] arm64: dts: qcom: x1-microsoft-denali: " Abel Vesa
2026-09-02 15:54 ` Konrad Dybcio
2026-09-01 8:07 ` [PATCH v2 15/16] arm64: dts: qcom: x1p42100-thinkbook-16: " Abel Vesa
2026-09-01 8:07 ` [PATCH v2 16/16] arm64: dts: qcom: x1p42100-microsoft-sp12in: " Abel Vesa
2026-09-02 15:54 ` 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=182336df-b505-4ae4-901f-e09c0eae80ed@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abel.vesa@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=alex.vinarskis@gmail.com \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=daleyo@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=ettore.chimenti@linaro.org \
--cc=ggo@tuxedocomputers.com \
--cc=harrison.vanderbyl@gmail.com \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=jerome.debretagne@gmail.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=mail@etehtsea.me \
--cc=maz@kernel.org \
--cc=quic_kdybcio@quicinc.com \
--cc=quic_rjendra@quicinc.com \
--cc=robh@kernel.org \
--cc=sibi.sankar@oss.qualcomm.com \
--cc=srini@kernel.org \
--cc=val@packett.cool \
--cc=wuxilin123@gmail.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.