From: "Paul Louvel" <paul.louvel@bootlin.com>
To: "Paul Louvel" <paul.louvel@bootlin.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Herve Codina" <herve.codina@bootlin.com>,
"Miquel Raynal" <miquel.raynal@bootlin.com>
Subject: Re: [PATCH v5 3/3] regulator: Add TI LM51772 support
Date: Tue, 10 Nov 2026 09:26:04 +0100 [thread overview]
Message-ID: <DMRDYWVZ4LY9.13BL0K8BOX2VC@bootlin.com> (raw)
In-Reply-To: <DMO344BLD9UQ.2X4YL7T3UZOWL@bootlin.com>
Hello Mark,
On Fri Nov 6, 2026 at 12:17 PM CET, Paul Louvel wrote:
> On Fri Nov 6, 2026 at 11:12 AM CET, Paul Louvel wrote:
>> +static const struct regulator_desc lm51772_regulator_template[] = {
>> + { .name = "vout",
>> + .of_match = of_match_ptr("vout"),
>> + .of_parse_cb = lm51772_vout_of_parse,
>> + .regulators_node = of_match_ptr("regulators"),
>> + .id = 0,
>> + .type = REGULATOR_VOLTAGE,
>> + .owner = THIS_MODULE,
>> + .linear_ranges = lm51772_voltage_ranges,
>> + .linear_range_selectors_bitfield = lm51772_voltage_ranges_sel,
>> + .n_linear_ranges = ARRAY_SIZE(lm51772_voltage_ranges),
>> + .n_voltages = 100 + 2301 + 165 + 2236,
>> + .vsel_reg = LM51772_REG_VOUT_TARGET1_LSB,
>> + .vsel_mask = LM51772_VOUT_TARGET1_MASK,
>> + .vsel_reg_oversize = true,
>> + .vsel_range_reg = LM51772_REG_MFR_SPECIFIC_D8,
>> + .vsel_range_mask = LM51772_SEL_FB_DIV20,
>> + .active_discharge_reg = LM51772_REG_MFR_SPECIFIC_D2,
>> + .active_discharge_mask = LM51772_DISCHARGE_CONFIG1 | LM51772_DISCHARGE_CONFIG0,
>> + .active_discharge_on =
>> + FIELD_PREP_CONST(LM51772_DISCHARGE_CONFIG1, 1) |
>> + FIELD_PREP_CONST(LM51772_DISCHARGE_CONFIG0, 1),
>> + .active_discharge_off =
>> + FIELD_PREP_CONST(LM51772_DISCHARGE_CONFIG1, 0) |
>> + FIELD_PREP_CONST(LM51772_DISCHARGE_CONFIG0, 0),
Please find the comment I made to my own patch below.
>
> Maybe would it be better if the core could also change the active discharge
> strength:
>
> int (*set_active_discharge)(struct regulator_dev *rdev, bool enable,
> int strength_uA);
>
> That would remove the need for introducing a vendor-specific property:
> 'ti,active-discharge-strength-microamp'.
>
Let me know what you think.
Thanks.
Best regards,
--
Paul Louvel, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-11-10 8:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 10:12 [PATCH v5 0/3] Add TI LM51772 buck-boost voltage regulator Paul Louvel
2026-11-06 10:12 ` [PATCH v5 1/3] regulator: dt-bindings: Add TI LM51772 support Paul Louvel
2026-11-06 10:12 ` [PATCH v5 2/3] regulator: core: Support regulators where the voltage selector spans two registers Paul Louvel
2026-11-06 10:12 ` [PATCH v5 3/3] regulator: Add TI LM51772 support Paul Louvel
2026-11-06 11:17 ` Paul Louvel
2026-11-06 12:22 ` Mark Brown
2026-11-06 16:44 ` Paul Louvel
2026-11-09 23:11 ` Mark Brown
2026-11-10 8:26 ` Paul Louvel [this message]
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=DMRDYWVZ4LY9.13BL0K8BOX2VC@bootlin.com \
--to=paul.louvel@bootlin.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=herve.codina@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/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®