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>
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] arm64: dts: qcom: milos-fairphone-fp6: Add Hall Effect sensor
Date: Tue, 20 Jan 2026 11:18:35 +0100 [thread overview]
Message-ID: <66a2cba1-551f-4f6e-b8f2-66524664c495@oss.qualcomm.com> (raw)
In-Reply-To: <DFSOPXFSOUY2.2Z6XCLCD796Q@fairphone.com>
On 1/19/26 4:52 PM, Luca Weiss wrote:
> On Mon Jan 19, 2026 at 3:41 PM CET, Konrad Dybcio wrote:
>> On 1/16/26 3:22 PM, Luca Weiss wrote:
>>> Add a node for the Hall Effect sensor, used to detect whether the Flip
>>> Cover is closed or not.
>>>
>>> The sensor is powered through vreg_l10b, so let's put a
>>> regulator-always-on on that to make sure the sensor gets power.
>>
>> Is there anything else on L10B? Can we turn it off if the hall sensor
>> is e.g. user-disabled?
>
> It's the voltage source for pull-up of sensor I2C bus (so
> ADSP-managed?), DVDD for amplifiers and VDD for a most sensors like
> the gyro.
>
> So realistically, it'll probably be (nearly) always on anyways. And I
> don't want to shave another yak by adding vdd support to gpio-keys...
That's okay
Let's configure the gpio70 in v2 like Dmitry pointed out
Konrad
next prev parent reply other threads:[~2026-01-20 10:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 14:22 Luca Weiss
2026-01-16 16:29 ` Dmitry Baryshkov
2026-01-19 14:41 ` Konrad Dybcio
2026-01-19 15:52 ` Luca Weiss
2026-01-20 10:18 ` Konrad Dybcio [this message]
2026-01-20 23:05 ` Dmitry Baryshkov
2026-01-21 8:07 ` Luca Weiss
2026-01-21 20:06 ` Dmitry Torokhov
2026-01-22 7:48 ` Luca Weiss
2026-01-22 8:32 ` 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=66a2cba1-551f-4f6e-b8f2-66524664c495@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=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
all inboxes | Powered by JetHome®