Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Robby Cai <robby.cai@nxp.com>
To: broonie@kernel.org, lgirdwood@gmail.com, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, andreas@kemnade.info
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	imx@lists.linux.dev
Subject: [PATCH v2 0/2] regulator: fp9931: Make vin-supply mandatory
Date: Fri, 13 Mar 2026 21:31:00 +0800	[thread overview]
Message-ID: <20260313133102.2749890-1-robby.cai@nxp.com> (raw)

The FP9931 regulator requires a valid "vin" supply to operate correctly.
Therefore, the driver should treat "vin" as a mandatory supply.

This patchset updates the binding documentation to mark vin-supply as a
required property, and modifies the driver accordingly. As suggested in
the reviews from Andreas and Mark, v2 switches to using
devm_regulator_get() since the supply is mandatory.

Changes in v2:
  - Addressed feedback from Andreas and Mark by replacing
    devm_regulator_get_optional() with devm_regulator_get()
    because VIN is required.
  - Added a new patch updating the binding documentation to make
    vin-supply a required property.

v1: https://patchwork.kernel.org/project/imx/patch/20260312040148.GA4007088@shlinux88/

Robby Cai (2):
  dt-bindings: regulator: fitipower,fp9931: Make vin-supply property as
    required
  regulator: fp9931: Fix handling of mandatory "vin" supply

 .../devicetree/bindings/regulator/fitipower,fp9931.yaml         | 1 +
 drivers/regulator/fp9931.c                                      | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

-- 
2.37.1


             reply	other threads:[~2026-03-13 13:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 13:31 Robby Cai [this message]
2026-03-13 13:31 ` [PATCH v2 1/2] dt-bindings: regulator: fp9931: Make vin-supply property as required Robby Cai
2026-03-13 13:33   ` Mark Brown
2026-03-13 14:16     ` Andreas Kemnade
2026-03-13 14:38       ` Mark Brown
2026-03-13 17:24   ` Conor Dooley
2026-03-13 13:31 ` [PATCH v2 2/2] regulator: fp9931: Fix handling of mandatory "vin" supply Robby Cai
2026-03-13 17:24   ` Conor Dooley
2026-03-16  7:26     ` Robby Cai
2026-03-16 14:28     ` Andreas Kemnade
2026-03-13 13:31 ` [PATCH v2 0/2] regulator: fp9931: Make vin-supply mandatory Mark Brown
2026-03-13 16:27   ` Mark Brown
2026-03-16  7:31     ` Robby Cai
2026-03-16 18:56       ` Mark Brown
2026-03-17 18:08 ` Mark Brown
2026-03-17 19:00 ` Mark Brown

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=20260313133102.2749890-1-robby.cai@nxp.com \
    --to=robby.cai@nxp.com \
    --cc=andreas@kemnade.info \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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