From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: Rob Herring <robh@kernel.org>,
Saravana Kannan <saravanak@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Alexis Czezar Torreno <alexisczezar.torreno@analog.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Peng Fan <peng.fan@nxp.com>
Subject: [PATCH 0/5] of: Introduce *_read_*_default helpers and convert regulator drivers
Date: Mon, 19 Jan 2026 10:02:53 +0800 [thread overview]
Message-ID: <20260119-add_dt_default-v1-0-db4787ea7a9e@nxp.com> (raw)
Introduces new helper functions of_property_read_u32_default() and
of_property_read_s32_default() to simplify reading optional Device Tree
properties with well-defined default values.
A common pattern in drivers is to initialize a variable with a default
value and then override it when a DT property is present, or to explicitly
check the return value of of_property_read_*() and fall back to a default.
While correct, this leads to repetitive boilerplate code and obscures the
intent that the property is optional.
The new helpers make this intent explicit by directly expressing
“optional property with default”. They intentionally ignore error codes
and are meant for cases where a missing or invalid property is not
considered fatal and a sensible default exists.
On top of introducing the helpers, this series converts several
regulator drivers to use them, reducing boilerplate while preserving
existing behavior. No functional changes, except for a minor fix in one
error path where dev_err_probe() is now called with a proper error code.
Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
Peng Fan (5):
of: Add of_property_read_[u32,s32]_default
regulator: of: Use of_property_read_u32_default()
regulator: adp5055: use of_property_read_[u32|s32]_default()
regulator: max77620: Use of_property_read_u32_default() for DT parsing
regulator: fan53555: Use of_property_read_u32_default() for DT parsing
drivers/regulator/adp5055-regulator.c | 30 ++++++++++---------------
drivers/regulator/fan53555.c | 8 ++-----
drivers/regulator/max77620-regulator.c | 40 ++++++++++++++--------------------
drivers/regulator/of_regulator.c | 18 ++++++---------
include/linux/of.h | 38 ++++++++++++++++++++++++++++++++
5 files changed, 74 insertions(+), 60 deletions(-)
---
base-commit: 0f853ca2a798ead9d24d39cad99b0966815c582a
change-id: 20260115-add_dt_default-4ca95f2a6cd7
Best regards,
--
Peng Fan <peng.fan@nxp.com>
next reply other threads:[~2026-01-19 2:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 2:02 Peng Fan (OSS) [this message]
2026-01-19 2:02 ` [PATCH 1/5] of: Add of_property_read_[u32,s32]_default Peng Fan (OSS)
2026-01-20 22:21 ` Rob Herring
2026-01-23 6:58 ` Peng Fan
2026-01-19 2:02 ` [PATCH 2/5] regulator: of: Use of_property_read_u32_default() Peng Fan (OSS)
2026-01-19 2:02 ` [PATCH 3/5] regulator: adp5055: use of_property_read_[u32|s32]_default() Peng Fan (OSS)
2026-01-19 2:02 ` [PATCH 4/5] regulator: max77620: Use of_property_read_u32_default() for DT parsing Peng Fan (OSS)
2026-01-19 2:02 ` [PATCH 5/5] regulator: fan53555: " Peng Fan (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=20260119-add_dt_default-v1-0-db4787ea7a9e@nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=alexisczezar.torreno@analog.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=saravanak@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®