From: Conor Dooley <conor@kernel.org>
To: Mihai Sain <mihai.sain@microchip.com>
Cc: robh@kernel.org, conor+dt@kernel.org, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, alexandre.belloni@bootlin.com,
devicetree@vger.kernel.org, broonie@kernel.org,
krzysztof.kozlowski+dt@linaro.org, claudiu.beznea@tuxon.dev,
andrei.simion@microchip.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 7/7] regulator: mcp16502: Update the names from buck regulators
Date: Wed, 27 Mar 2024 16:28:49 +0000 [thread overview]
Message-ID: <20240327-agreed-routine-0cc60186876b@spud> (raw)
In-Reply-To: <20240327101724.2982-8-mihai.sain@microchip.com>
[-- Attachment #1.1: Type: text/plain, Size: 2047 bytes --]
On Wed, Mar 27, 2024 at 12:17:24PM +0200, Mihai Sain wrote:
> Use generic names for buck regulators to avoid any confusion.
> Update the names from buck regulators in order to match
> the datasheet block diagram for the buck regulators.
>
> Signed-off-by: Mihai Sain <mihai.sain@microchip.com>
I know the regulator core will create dummy regulators when they are not
provided in the devicetree, so I am not 100% on how backwards
compatibility works here.
You'll end up with a bunch of dummies and therefore the regulator-names
and constraints on the regulator will be lost, no?
Can you explain how is this backwards compatible with the old
devicetrees?
Thanks,
Conor.
> ---
> drivers/regulator/mcp16502.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/regulator/mcp16502.c b/drivers/regulator/mcp16502.c
> index 0c15a19fe83a..d6fc9f1afaef 100644
> --- a/drivers/regulator/mcp16502.c
> +++ b/drivers/regulator/mcp16502.c
> @@ -468,13 +468,13 @@ static const struct linear_range b234_ranges[] = {
>
> static const struct regulator_desc mcp16502_desc[] = {
> /* MCP16502_REGULATOR(_name, _id, ranges, regulator_ops, ramp_table) */
> - MCP16502_REGULATOR("VDD_IO", BUCK1, b1l12_ranges, mcp16502_buck_ops,
> + MCP16502_REGULATOR("BUCK1", BUCK1, b1l12_ranges, mcp16502_buck_ops,
> mcp16502_ramp_b1l12),
> - MCP16502_REGULATOR("VDD_DDR", BUCK2, b234_ranges, mcp16502_buck_ops,
> + MCP16502_REGULATOR("BUCK2", BUCK2, b234_ranges, mcp16502_buck_ops,
> mcp16502_ramp_b234),
> - MCP16502_REGULATOR("VDD_CORE", BUCK3, b234_ranges, mcp16502_buck_ops,
> + MCP16502_REGULATOR("BUCK3", BUCK3, b234_ranges, mcp16502_buck_ops,
> mcp16502_ramp_b234),
> - MCP16502_REGULATOR("VDD_OTHER", BUCK4, b234_ranges, mcp16502_buck_ops,
> + MCP16502_REGULATOR("BUCK4", BUCK4, b234_ranges, mcp16502_buck_ops,
> mcp16502_ramp_b234),
> MCP16502_REGULATOR("LDO1", LDO1, b1l12_ranges, mcp16502_ldo_ops,
> mcp16502_ramp_b1l12),
> --
> 2.44.0
>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-03-27 16:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 10:17 [PATCH 0/7] regulator: mcp16502: Update the names from buck regulators Mihai Sain
2024-03-27 10:17 ` [PATCH 1/7] ARM: dts: microchip: sama5d27_wlsom1: Update the node names from pmic-regulators Mihai Sain
2024-03-27 10:17 ` [PATCH 2/7] ARM: dts: microchip: sama5d29_curiosity: " Mihai Sain
2024-03-27 10:17 ` [PATCH 3/7] ARM: dts: microchip: sama5d2_icp: " Mihai Sain
2024-03-27 10:17 ` [PATCH 4/7] ARM: dts: microchip: sama7g54_curiosity: " Mihai Sain
2024-03-27 10:17 ` [PATCH 5/7] ARM: dts: microchip: sama7g5ek: " Mihai Sain
2024-03-27 10:17 ` [PATCH 6/7] regulator: dt-bindings: microchip,mcp16502: Update the node names from buck regulators Mihai Sain
2024-03-27 10:17 ` [PATCH 7/7] regulator: mcp16502: Update the " Mihai Sain
2024-03-27 16:28 ` Conor Dooley [this message]
2024-03-28 13:45 ` Mark Brown
2024-03-27 15:41 ` [PATCH 0/7] " Rob Herring
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=20240327-agreed-routine-0cc60186876b@spud \
--to=conor@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=andrei.simion@microchip.com \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mihai.sain@microchip.com \
--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