From: Mihai Sain <mihai.sain@microchip.com>
To: <robh@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>, <nicolas.ferre@microchip.com>,
<alexandre.belloni@bootlin.com>, <claudiu.beznea@tuxon.dev>,
<lgirdwood@gmail.com>, <broonie@kernel.org>,
<andrei.simion@microchip.com>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: Mihai Sain <mihai.sain@microchip.com>
Subject: [PATCH 0/7] regulator: mcp16502: Update the names from buck regulators
Date: Wed, 27 Mar 2024 12:17:17 +0200 [thread overview]
Message-ID: <20240327101724.2982-1-mihai.sain@microchip.com> (raw)
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.
Using BUCK1-4 as node names is consistent with the node naming rules.
Link: https://ww1.microchip.com/downloads/aemDocuments/documents/APID/ProductDocuments/DataSheets/MCP16502-Data-Sheet-DS20006275.pdf
Mihai Sain (7):
ARM: dts: microchip: sama5d27_wlsom1: Update the node names from pmic-regulators
ARM: dts: microchip: sama5d29_curiosity: Update the node names from pmic-regulators
ARM: dts: microchip: sama5d2_icp: Update the node names from pmic-regulators
ARM: dts: microchip: sama7g54_curiosity: Update the node names from pmic-regulators
ARM: dts: microchip: sama7g5ek: Update the node names from pmic-regulators
regulator: dt-bindings: microchip,mcp16502: Update the node names from buck regulators
regulator: mcp16502: Update the names from buck regulators
.../bindings/regulator/microchip,mcp16502.yaml | 10 +++++-----
arch/arm/boot/dts/microchip/at91-sama5d27_wlsom1.dtsi | 8 ++++----
.../arm/boot/dts/microchip/at91-sama5d29_curiosity.dts | 8 ++++----
arch/arm/boot/dts/microchip/at91-sama5d2_icp.dts | 8 ++++----
.../arm/boot/dts/microchip/at91-sama7g54_curiosity.dts | 8 ++++----
arch/arm/boot/dts/microchip/at91-sama7g5ek.dts | 8 ++++----
drivers/regulator/mcp16502.c | 8 ++++----
7 files changed, 29 insertions(+), 29 deletions(-)
--
2.44.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2024-03-27 10:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 10:17 Mihai Sain [this message]
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
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=20240327101724.2982-1-mihai.sain@microchip.com \
--to=mihai.sain@microchip.com \
--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=nicolas.ferre@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