From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Luca Weiss <luca.weiss@fairphone.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>,
Marijn Suijten <marijn.suijten@somainline.org>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] arm64: dts: qcom: qcm6490-fairphone-fp5: Add VTOF_LDO_2P8 regulator
Date: Mon, 20 Oct 2025 14:08:05 +0200 [thread overview]
Message-ID: <36928f42-3603-4e01-a31d-8f9e60f54009@oss.qualcomm.com> (raw)
In-Reply-To: <DDDPKMMSAMJR.1JIQMK3W2Y40V@fairphone.com>
On 10/9/25 12:10 PM, Luca Weiss wrote:
> On Thu Oct 9, 2025 at 11:22 AM CEST, Konrad Dybcio wrote:
>> On 10/9/25 11:16 AM, Luca Weiss wrote:
>>> Hi Konrad,
>>>
>>> On Wed Oct 1, 2025 at 10:30 AM CEST, Konrad Dybcio wrote:
>>>> On 9/30/25 3:57 PM, Luca Weiss wrote:
>>>>> Describe yet another regulator-fixed on this board, powering the ToF
>>>>> sensor.
>>>>>
>>>>> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
>>>>> ---
>>>>> arch/arm64/boot/dts/qcom/qcm6490-fairphone-fp5.dts | 13 +++++++++++++
>>>>> 1 file changed, 13 insertions(+)
>>>>>
>>>>> diff --git a/arch/arm64/boot/dts/qcom/qcm6490-fairphone-fp5.dts b/arch/arm64/boot/dts/qcom/qcm6490-fairphone-fp5.dts
>>>>> index 36d5750584831d66b4c2faf6042e4cbb3274eca7..0a64e5721e092d1f3e4bb7329335704eee567761 100644
>>>>> --- a/arch/arm64/boot/dts/qcom/qcm6490-fairphone-fp5.dts
>>>>> +++ b/arch/arm64/boot/dts/qcom/qcm6490-fairphone-fp5.dts
>>>>> @@ -195,6 +195,19 @@ vreg_usb_redrive_1v8: regulator-usb-redrive-1v8 {
>>>>> pinctrl-names = "default";
>>>>> };
>>>>>
>>>>> + vreg_vtof_ldo_2p8: regulator-vtof-ldo-2p8 {
>>>>> + compatible = "regulator-fixed";
>>>>> + regulator-name = "VTOF_LDO_2P8";
>>>>> + regulator-min-microvolt = <2800000>;
>>>>> + regulator-max-microvolt = <2800000>;
>>>>> + regulator-enable-ramp-delay = <233>;
>>>>> +
>>>>> + gpio = <&tlmm 141 GPIO_ACTIVE_HIGH>;
>>>>
>>>> You may want to define the pincfg/mux config for this gpio too
>>>
>>> While I wouldn't say it's not good to have it, there's plenty of GPIOs
>>> that have no pinctrl for it. Downstream doesn't set anything for gpio141
>>> either.
>>>
>>> I honestly wouldn't even know what the 'default' for a GPIO is in the
>>> first place, or could I query the runtime state from the kernel? Is
>>> /sys/kernel/debug/pinctrl/f100000.pinctrl/pinconf-groups trustworthy to
>>> solidify this in the dts?
>>
>> I normally use /sys/kernel/debug/gpios
>
> Oh, if that works at least the path is a bit more memorable. I needed to
> check quite some files in this directory to find the correct one.
>
>>
>>>
>>> 141 (gpio141): input bias disabled, output drive strength (2 mA), output enabled, pin output (0 level)
>>
>> but this seems to be formatted very similarly if not identically
>>
>> Generally it reads out HW state, via (among other things)
>> msm_config_group_get()
>
> So, you recommend setting a pinctrl for every single GPIO that's
> referenced in the dts? Shall I send a patch to add all the missing ones?
That would make the state always deterministic and it's probably
desirable yeah
Konrad
next prev parent reply other threads:[~2025-10-20 12:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 13:57 [PATCH 0/5] Mix of dts fixes and improvements for qcm6490/sm7325 devices Luca Weiss
2025-09-30 13:57 ` [PATCH 1/5] arm64: dts: qcom: qcm6490-fairphone-fp5: Add supplies to simple-fb node Luca Weiss
2025-10-02 3:20 ` Dmitry Baryshkov
2025-09-30 13:57 ` [PATCH 2/5] arm64: dts: qcom: qcm6490-fairphone-fp5: Add VTOF_LDO_2P8 regulator Luca Weiss
2025-10-01 8:30 ` Konrad Dybcio
2025-10-09 9:16 ` Luca Weiss
2025-10-09 9:22 ` Konrad Dybcio
2025-10-09 10:10 ` Luca Weiss
2025-10-20 12:08 ` Konrad Dybcio [this message]
2025-09-30 13:57 ` [PATCH 3/5] arm64: dts: qcom: qcm6490-fairphone-fp5: Use correct compatible for audiocc Luca Weiss
2025-10-02 4:03 ` Dmitry Baryshkov
2025-09-30 13:57 ` [PATCH 4/5] arm64: dts: qcom: qcm6490-shift-otter: " Luca Weiss
2025-10-04 6:18 ` Dmitry Baryshkov
2025-09-30 13:57 ` [PATCH 5/5] arm64: dts: qcom: sm7325-nothing-spacewar: " Luca Weiss
2025-10-04 6:18 ` Dmitry Baryshkov
2025-10-27 22:37 ` [PATCH 0/5] Mix of dts fixes and improvements for qcm6490/sm7325 devices Bjorn Andersson
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=36928f42-3603-4e01-a31d-8f9e60f54009@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--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=luca.weiss@fairphone.com \
--cc=marijn.suijten@somainline.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.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