From: "krzk@kernel.org" <krzk@kernel.org>
To: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>
Cc: "daniel.baluta@nxp.com" <daniel.baluta@nxp.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"festevam@gmail.com" <festevam@gmail.com>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"Anson.Huang@nxp.com" <Anson.Huang@nxp.com>,
"aford173@gmail.com" <aford173@gmail.com>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"richard@nod.at" <richard@nod.at>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-imx@nxp.com" <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"han.xu@nxp.com" <han.xu@nxp.com>,
"lee.jones@linaro.org" <lee.jones@linaro.org>,
"yibin.gong@nxp.com" <yibin.gong@nxp.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"jun.li@nxp.com" <jun.li@nxp.com>
Subject: Re: [PATCH 03/16] arm64: dts: imx8mm-beacon-som.dtsi: Align regulator names with schema
Date: Tue, 25 Aug 2020 09:45:00 +0200 [thread overview]
Message-ID: <20200825074500.GA19323@kozik-lap> (raw)
In-Reply-To: <20200825072537.GA5914@kozik-lap>
On Tue, Aug 25, 2020 at 09:25:37AM +0200, krzk@kernel.org wrote:
> On Tue, Aug 25, 2020 at 06:51:33AM +0000, Vaittinen, Matti wrote:
> > Hello Krzysztof,
> >
> > Just some questions - please ignore if I misunderstood the impact of
> > the change.
> >
> > On Mon, 2020-08-24 at 21:06 +0200, Krzysztof Kozlowski wrote:
> > > Device tree schema expects regulator names to be lowercase. This
> > > fixes
> > > dtbs_check warnings like:
> > >
> > > arch/arm64/boot/dts/freescale/imx8mn-ddr4-evk.dt.yaml: pmic@4b:
> > > regulators:LDO1:regulator-name:0: 'LDO1' does not match '^ldo[1-6]$'
> > >
> > > Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> > > ---
> > > .../boot/dts/freescale/imx8mn-ddr4-evk.dts | 22 +++++++++------
> > > ----
> > > 1 file changed, 11 insertions(+), 11 deletions(-)
> > >
> > > diff --git a/arch/arm64/boot/dts/freescale/imx8mn-ddr4-evk.dts
> > > b/arch/arm64/boot/dts/freescale/imx8mn-ddr4-evk.dts
> > > index a1e5483dbbbe..299caed5d46e 100644
> > > --- a/arch/arm64/boot/dts/freescale/imx8mn-ddr4-evk.dts
> > > +++ b/arch/arm64/boot/dts/freescale/imx8mn-ddr4-evk.dts
> > > @@ -60,7 +60,7 @@
> > >
> > > regulators {
> > > buck1_reg: BUCK1 {
> > > - regulator-name = "BUCK1";
> > > + regulator-name = "buck1";
> >
> > I am not against this change but I would expect seeing some other
> > patches too? I guess this will change the regulator name in regulator
> > core, right? So maybe I am mistaken but it looks to me this change is
> > visible in suppliers, sysfs and debugfs too? Thus changing this sounds
> > a bit like asking for a nose bleed :) Am I right that the impact of
> > this change has been thoroughly tested? Are there any other patches
> > (that I have not seen) related to this change?
>
> Oh, crap, the names of regulators in the driver are lowercase, but they
> use of_match_ptr for upper case. Seriously, why making a binding which
> is contradictory to the driver implementation on the first day?
>
> The driver goes with binding, right? One expects uppercase, other
> lowercase...
>
> And tell me, what is now the ABI? The binding or the incorrect
> implementation?
Wait, my mistake. I got confused by my own change. The node name stays
the same, so of_match will be correct.
The driver internally already uses lowercase names.
Everything looks good. I will just double check whether the constraints
did not change on the board after boot.
>
> >
> > > regulator-min-microvolt = <700000>;
> > > regulator-max-microvolt = <1300000>;
> > > regulator-boot-on;
> > > @@ -69,7 +69,7 @@
> > > };
> > >
> > > buck2_reg: BUCK2 {
> > > - regulator-name = "BUCK2";
> > > + regulator-name = "buck2";
> > > regulator-min-microvolt = <700000>;
> > > regulator-max-microvolt = <1300000>;
> > > regulator-boot-on;
> > > @@ -79,14 +79,14 @@
> > >
> > > buck3_reg: BUCK3 {
> > > // BUCK5 in datasheet
> > > - regulator-name = "BUCK3";
> > > + regulator-name = "buck3";
> > > regulator-min-microvolt = <700000>;
> > > regulator-max-microvolt = <1350000>;
> > > };
> > >
> > > buck4_reg: BUCK4 {
> > > // BUCK6 in datasheet
> > > - regulator-name = "BUCK4";
> > > + regulator-name = "buck4";
> > > regulator-min-microvolt = <3000000>;
> > > regulator-max-microvolt = <3300000>;
> > > regulator-boot-on;
> > > @@ -95,7 +95,7 @@
> > >
> > > buck5_reg: BUCK5 {
> > > // BUCK7 in datasheet
> > > - regulator-name = "BUCK5";
> > > + regulator-name = "buck5";
> >
> > What I see in bd718x7-regulator.c for LDO6 desc is:
> >
> > /* LDO6 is supplied by buck5 */
> > .supply_name = "buck5",
> >
> > So, is this change going to change the supply-chain for the board? Is
> > this intended? (Or am I mistaken on what is the impact of regulator-
> > name property?)
Good point, let me check the supplies.
>
> The names will take regulator names from the driver. The problem is with
> matching the of_node.
>
>
> Dear Rob,
>
> Maybe you have an idea how to fix this driver-binding ABI
> incompatibility? Or better just leave it?
Not valid anymore, I just got confused...
Best regards,
Krzysztof
_______________________________________________
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:[~2020-08-25 7:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 19:06 [PATCH 01/16] dt-bindings: mfd: rohm, bd71847-pmic: Correct clock properties requirements Krzysztof Kozlowski
2020-08-24 19:06 ` [PATCH 02/16] dt-bindings: mtd: gpmi-nand: Fix matching of clocks on different SoCs Krzysztof Kozlowski
2020-08-25 6:40 ` Sascha Hauer
2020-08-25 6:49 ` Krzysztof Kozlowski
2020-08-24 19:06 ` [PATCH 03/16] arm64: dts: imx8mm-beacon-som.dtsi: Align regulator names with schema Krzysztof Kozlowski
2020-08-25 6:51 ` Vaittinen, Matti
2020-08-25 7:25 ` krzk
2020-08-25 7:45 ` krzk [this message]
2020-08-25 7:50 ` krzk
2020-08-25 8:22 ` Vaittinen, Matti
2020-08-25 8:27 ` krzk
2020-08-25 9:35 ` Vaittinen, Matti
2020-08-25 8:29 ` Krzysztof Kozlowski
2020-08-24 19:06 ` [PATCH 04/16] arm64: dts: imx8mm-beacon-baseboard: Correct SPI CS polarity Krzysztof Kozlowski
2020-08-24 20:07 ` Fabio Estevam
2020-08-24 19:06 ` [PATCH 05/16] arm64: dts: imx8mm-beacon: Align pin configuration group names with schema Krzysztof Kozlowski
2020-08-24 19:06 ` [PATCH 06/16] arm64: dts: imx8mm-evk: Add 32.768 kHz clock to PMIC Krzysztof Kozlowski
2020-08-24 19:06 ` [PATCH 07/16] arm64: dts: imx8mm-evk: Align pin configuration group names with schema Krzysztof Kozlowski
2020-08-24 19:06 ` [PATCH 08/16] arm64: dts: imx8mm-ddr4-evk: " Krzysztof Kozlowski
2020-08-24 19:06 ` [PATCH 09/16] arm64: dts: imx8mn-evk: " Krzysztof Kozlowski
2020-08-24 19:06 ` [PATCH 10/16] arm64: dts: imx8mq-evk: " Krzysztof Kozlowski
2020-08-24 19:06 ` [PATCH 11/16] arm64: dts: imx8mq-librem5-devkit: " Krzysztof Kozlowski
2020-08-24 19:06 ` [PATCH 12/16] arm64: dts: imx8mq-phanbell: " Krzysztof Kozlowski
2020-08-24 19:06 ` [PATCH 13/16] arm64: dts: imx8mq-pico-pi: " Krzysztof Kozlowski
2020-08-24 19:06 ` [PATCH 14/16] arm64: dts: imx8mq-sr-som: " Krzysztof Kozlowski
2020-08-24 19:07 ` [PATCH 15/16] arm64: dts: imx8mq-hummingboard-pulse: " Krzysztof Kozlowski
2020-08-24 19:07 ` [PATCH 16/16] arm64: dts: imx8qxp-colibri: " Krzysztof Kozlowski
2020-08-25 6:23 ` [PATCH 01/16] dt-bindings: mfd: rohm, bd71847-pmic: Correct clock properties requirements Vaittinen, Matti
2020-08-25 6:55 ` krzk
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=20200825074500.GA19323@kozik-lap \
--to=krzk@kernel.org \
--cc=Anson.Huang@nxp.com \
--cc=Matti.Vaittinen@fi.rohmeurope.com \
--cc=aford173@gmail.com \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=han.xu@nxp.com \
--cc=jun.li@nxp.com \
--cc=kernel@pengutronix.de \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=vigneshr@ti.com \
--cc=yibin.gong@nxp.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;
as well as URLs for NNTP newsgroup(s).