Re: [PATCH v2 5/6] arm64: dts: qcom: x1e80100-vivobook-s15: add charge limit nvmem

[Maud Spierings <maud_spierings@hotmail.com>]

On 11/20/25 16:36, Konrad Dybcio wrote:
> On 11/17/25 4:44 PM, Maud Spierings wrote:
>> On 11/17/25 16:35, Konrad Dybcio wrote:
>>> 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?
>> the values in /sys/class/power_supply/jada-jada/ are zero when rebooting from Windows into Linux after enabling charge limitting in the Asus application.
>>
>> I remember my old vivobook (x86) also forgot its settings each boot, but given the nvmem cells that should not be happing here I guess. It is odd that there seems to be no collision between Windows and Linux. Maybe the Windows mechanism is doing the old trick of writing it in there every boot?
> Odd indeed.. Does it work if you reboot from Linux to Linux?
It seems not, I seem to remember testing it quite some time ago, but I 
cannot get it to remember any way, at least it is not popping up in 
sysfs, always back to 0

Kind regards,
Maud