From: Paul Adam <adamp@posteo.de>
To: Stephan Gerhold <stephan.gerhold@linaro.org>
Cc: 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>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org
Subject: Re: [PATCH v3 3/3] arm64: dts: qcom: msm8916-wiko-chuppito: add initial devicetree
Date: Sat, 07 Mar 2026 17:20:08 +0000 [thread overview]
Message-ID: <aaxeRXsQlR-1CTKV@MyryksLaptop> (raw)
In-Reply-To: <aalRKuqzX48PzyL-@linaro.org>
On 26/03/05 10:47, Stephan Gerhold wrote:
> Did you mean "sleep" instead of "suspend" here? By default, there is
> "default", "init", "idle" and "sleep" [1], although drivers can request
> custom pinctrl states as well.
>
> Note that even with "sleep", the pinctrl state will be rarely used on
> Linux. Drivers need to explicitly call pinctrl_pm_select_sleep_state()
> to trigger these, but only few drivers do that [2]. From a quick look,
> I suspect that only the &sdhc_2 sleep pinctrl here is currently used on
> Linux.
>
> That doesn't mean that you can't add these pinctrl states (the DT is not
> supposed to be specific to one particular operating system), but it does
> mean that most of these are effectively untested right now. I would
> personally omit them.
>
> [1]: https://elixir.bootlin.com/linux/v7.0-rc1/source/include/linux/pinctrl/pinctrl-state.h#L36
> [2]: https://elixir.bootlin.com/linux/v7.0-rc1/A/ident/pinctrl_pm_select_sleep_state
Thanks, I will remove them.
[...]
> Does this need to be always-on?
Still works without, will take it out.
Paul
prev parent reply other threads:[~2026-03-07 17:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-01 22:29 [PATCH v3 0/3] Add wiko-chuppito devictree Paul Adam via B4 Relay
2026-03-01 22:29 ` [PATCH v3 1/3] dt-bindings: vendor-prefixes: add WIKO SAS Paul Adam via B4 Relay
2026-03-01 22:29 ` [PATCH v3 2/3] dt-bindings: arm: qcom: add wiko,chuppito compatible string Paul Adam via B4 Relay
2026-03-01 22:29 ` [PATCH v3 3/3] arm64: dts: qcom: msm8916-wiko-chuppito: add initial devicetree Paul Adam via B4 Relay
2026-03-02 11:08 ` Konrad Dybcio
2026-03-04 22:14 ` Paul Adam
2026-03-05 8:28 ` Konrad Dybcio
2026-03-05 9:47 ` Stephan Gerhold
2026-03-07 17:20 ` Paul Adam [this message]
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=aaxeRXsQlR-1CTKV@MyryksLaptop \
--to=adamp@posteo.de \
--cc=andersson@kernel.org \
--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=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=stephan.gerhold@linaro.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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