From: robby.cai@oss.nxp.com
To: lgirdwood@gmail.com, broonie@kernel.org, andreas@kemnade.info
Cc: linux-kernel@vger.kernel.org, imx@lists.linux.dev
Subject: [PATCH 1/2] regulator: fp9931: Fix VPOS/VNEG voltage selector table
Date: Tue, 21 Jul 2026 17:59:58 +0800 [thread overview]
Message-ID: <20260721095959.1855436-2-robby.cai@oss.nxp.com> (raw)
In-Reply-To: <20260721095959.1855436-1-robby.cai@oss.nxp.com>
From: Robby Cai <robby.cai@nxp.com>
The VPOSNEG_table[] mapping does not match the FP9931/JD9930 datasheet.
The datasheet defines the VPOS/VNEG voltage mapping as:
00h-04h -> 7.04V (-7.04V)
05h -> 7.26V (-7.26V)
06h -> 7.49V (-7.49V)
...
28h-3Fh -> 15.06V (-15.06V)
However, the current table maps selector 0x05 to 7.04V instead of
7.26V, causing all subsequent entries to be shifted by one position.
Update VPOSNEG_table[] to match the documented register encoding.
Fixes: 12d821bd13d4 ("regulator: Add FP9931/JD9930 driver")
Signed-off-by: Robby Cai <robby.cai@nxp.com>
---
drivers/regulator/fp9931.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/regulator/fp9931.c b/drivers/regulator/fp9931.c
index 002b41f53eff..5eee21034f6b 100644
--- a/drivers/regulator/fp9931.c
+++ b/drivers/regulator/fp9931.c
@@ -42,7 +42,6 @@ static const unsigned int VPOSNEG_table[] = {
7040000,
7040000,
7040000,
- 7040000,
7260000,
7490000,
7710000,
--
2.50.1
next prev parent reply other threads:[~2026-07-21 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 9:59 [PATCH 0/2] regulator: fp9931: fix voltage mapping and runtime PM issues robby.cai
2026-07-21 9:59 ` robby.cai [this message]
2026-07-27 20:04 ` [PATCH 1/2] regulator: fp9931: Fix VPOS/VNEG voltage selector table Andreas Kemnade
2026-07-31 8:42 ` Robby Cai (OSS)
2026-07-21 9:59 ` [PATCH 2/2] regulator: fp9931: Fix Runtime PM usage count underflow in v3p3 ops robby.cai
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=20260721095959.1855436-2-robby.cai@oss.nxp.com \
--to=robby.cai@oss.nxp.com \
--cc=andreas@kemnade.info \
--cc=broonie@kernel.org \
--cc=imx@lists.linux.dev \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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®