From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Maud Spierings <maud_spierings@hotmail.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
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>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 5/6] arm64: dts: qcom: x1e80100-vivobook-s15: add charge limit nvmem
Date: Mon, 17 Nov 2025 16:35:54 +0100 [thread overview]
Message-ID: <ff773af3-d843-42ff-b4dc-e5a9d85c2285@oss.qualcomm.com> (raw)
In-Reply-To: <PR3P189MB1020E7393F72B285173137A2E3C9A@PR3P189MB1020.EURP189.PROD.OUTLOOK.COM>
On 11/17/25 3:13 PM, Maud Spierings wrote:
> Hi Konrad,
>
> On 11/17/25 13:59, Konrad Dybcio wrote:
>> On 11/16/25 11:52 AM, Maud Spierings via B4 Relay wrote:
>>> From: Maud Spierings <maud_spierings@hotmail.com>
>>>
>>> Add nvmem cells for getting charge control thresholds if they have
>>> been set previously.
>>>
>>> Signed-off-by: Maud Spierings <maud_spierings@hotmail.com>
>>> ---
>>
>> Have you verified that e.g.
>>
>> connecting the charger
>> setting the charge threshold
>> rebooting to windows
>> rebooting to windows once more for good measure
>> rebooting to linux
>>
>> still has the settings persist?
>
> Hmm I have tried several things but I can't seem to get the values to stick. I the spmi-sdam driver is compiled in, I am not quite sure if I might be missing something.
Hm, I wonder if Windows/UEFI overwrites these values or whether they're
used by something else..
Can you set a threshold in windows and see if Linux can read back that
data?
Konrad
next prev parent reply other threads:[~2025-11-17 15:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-16 10:52 [PATCH v2 0/6] arm64: dts: qcom: x1e80100-vivobook-s15: add more missing features Maud Spierings via B4 Relay
2025-11-16 10:52 ` [PATCH v2 1/6] dt-bindings: display: bridge: simple: document the Parade PS185HDM DP-to-HDMI bridge Maud Spierings via B4 Relay
2025-11-16 10:52 ` [PATCH v2 2/6] drm/bridge: simple: add " Maud Spierings via B4 Relay
2025-11-16 10:52 ` [PATCH v2 3/6] arm64: dts: qcom: x1e80100-vivobook-s15: enable ps8830 retimers Maud Spierings via B4 Relay
2025-11-17 12:58 ` Konrad Dybcio
2025-11-16 10:52 ` [PATCH v2 4/6] arm64: dts: qcom: x1e80100-vivobook-s15: add HDMI port Maud Spierings via B4 Relay
2025-11-24 11:50 ` Konrad Dybcio
2025-11-16 10:52 ` [PATCH v2 5/6] arm64: dts: qcom: x1e80100-vivobook-s15: add charge limit nvmem Maud Spierings via B4 Relay
2025-11-17 12:59 ` Konrad Dybcio
2025-11-17 14:13 ` Maud Spierings
2025-11-17 15:35 ` Konrad Dybcio [this message]
2025-11-17 15:44 ` Maud Spierings
2025-11-20 15:36 ` Konrad Dybcio
2025-11-22 11:07 ` Maud Spierings
2025-11-22 13:37 ` Konrad Dybcio
2025-11-23 11:03 ` Maud Spierings
2025-11-24 11:01 ` Konrad Dybcio
2025-11-16 10:52 ` [PATCH v2 6/6] arm64: dts: qcom: x1e80100-vivobook-s15: enable IRIS Maud Spierings via B4 Relay
2025-11-17 12:59 ` Konrad Dybcio
2025-11-16 11:36 ` (subset) [PATCH v2 0/6] arm64: dts: qcom: x1e80100-vivobook-s15: add more missing features Dmitry Baryshkov
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=ff773af3-d843-42ff-b4dc-e5a9d85c2285@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=andrzej.hajda@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maud_spierings@hotmail.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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