mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 v2 0/2] regulator: fp9931: fix voltage mapping and runtime PM issues
Date: Fri, 24 Jul 2026 18:34:39 +0800	[thread overview]
Message-ID: <20260724103441.800522-1-robby.cai@oss.nxp.com> (raw)

From: Robby Cai <robby.cai@nxp.com>

This series fixes two issues in the FP9931/JD9930 regulator driver.

Patch 1 fixes errors in the VPOS/VNEG voltage selector table, correcting
an off-by-one entry and extending the table to cover the full selector
range defined by the datasheet [1].

Patch 2 fixes a Runtime PM reference counting bug in the V3P3 regulator
callbacks that can lead to "Runtime PM usage count underflow!" warnings.


[1] https://www.fitipower.com/dl/file/flXa6hIchVeu0W3K (Datasheet, p.13)

Thanks,
Robby


---

Changes in v2:
- [1/2] Extend VPOSNEG_table[] to cover selectors 0x29-0x3f as defined by the datasheet and reformat the table for readability.
- [2/2] Refine commit message; no code change.

Link to v1: https://lore.kernel.org/imx/20260721095959.1855436-1-robby.cai@oss.nxp.com/


---

Robby Cai (2):
  regulator: fp9931: Fix VPOS/VNEG voltage selector table
  regulator: fp9931: Fix Runtime PM usage count underflow in v3p3 ops

 drivers/regulator/fp9931.c | 61 +++++++++++---------------------------
 1 file changed, 17 insertions(+), 44 deletions(-)

-- 
2.50.1


             reply	other threads:[~2026-07-24 10:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24 10:34 robby.cai [this message]
2026-07-24 10:34 ` [PATCH v2 1/2] regulator: fp9931: Fix VPOS/VNEG voltage selector table robby.cai
2026-08-04 22:36   ` Andreas Kemnade
2026-07-24 10:34 ` [PATCH v2 2/2] regulator: fp9931: Fix Runtime PM usage count underflow in v3p3 ops robby.cai
2026-07-25 19:50   ` Andreas Kemnade
2026-07-31  8:35     ` Robby Cai (OSS)

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=20260724103441.800522-1-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®