diff options
| author | Ryan Brue <ryanbrue.dev@gmail.com> | 2026-09-17 23:57:46 -0500 |
|---|---|---|
| committer | Alexandre Belloni <alexandre.belloni@bootlin.com> | 2026-09-30 16:40:41 +0200 |
| commit | 8423c476ab2a193e67d7f8db8621dbc02854dd9d (patch) | |
| tree | 3a3a184cd7f7d57b549287cad46d13232c2f0e3a /tools/perf/scripts/python | |
| parent | cba3b5f4cc008ca9877f8add2096ad09c7bfc6cb (diff) | |
| download | linux-next-8423c476ab2a193e67d7f8db8621dbc02854dd9d.tar.gz linux-next-8423c476ab2a193e67d7f8db8621dbc02854dd9d.zip | |
dt-bindings: mfd: mediatek: mt6397: describe the RTC's nvmem layout
Four of the MT6397 RTC's alarm registers use only their low bits; the
high byte of each is storage the clock and the alarm don't touch.
MediaTek's documentation names them RTC_NEW_SPARE0 to RTC_NEW_SPARE3 and
assigns the first to a fuel gauge, which is what a battery driver reads
at boot so that the reported capacity does not jump across a reboot.
They sit in the RTC's always-on domain, so the driver can offer them as
a battery-backed nvmem provider. Allow a board to lay cells out over
them.
Assisted-by: LLM
Signed-off-by: Ryan Brue <ryanbrue.dev@gmail.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
Link: https://patch.msgid.link/20260917-rbrue-suez-upstreaming-mt6397-rtc-nvmem-v1-1-558b8f95cfbc@gmail.com
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions