public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Mark Kettenis <mark.kettenis@xs4all.nl>,
	robh+dt@kernel.org, conor+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org
Cc: d3adme4t@gmail.com, macromorgan@hotmail.com, jbx6244@gmail.com,
	f.kardame@manjaro.org, amadeus@jmu.edu.cn, linux.amoon@gmail.com,
	aurelien@aurel32.net, anarsoul@gmail.com, wiagn233@outlook.com,
	frattaroli.nicolas@gmail.com, strit@manjaro.org,
	luiz.von.dentz@intel.com, zonyitoo@gmail.com, wens@csie.org,
	jensenhuang@friendlyarm.com, lasstp5011@gmail.com,
	frank-w@public-files.de, pgwipeout@gmail.com, leo@nabam.net,
	andyshrk@163.com, michael.riesch@wolfvision.net, jonas@kwiboo.se,
	festevam@denx.de, tobetter@gmail.com, jagan@amarulasolutions.com,
	cnsztl@gmail.com, cristian.ciocaltea@collabora.com,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH] arm64: dts: rockchip: Drop invalid regulator-init-microvolt property
Date: Mon, 10 Jul 2023 17:39:55 +0200	[thread overview]
Message-ID: <4519023.cEBGB3zze1@phil> (raw)
In-Reply-To: <87wmz7q1fr.fsf@bloch.sibelius.xs4all.nl>

Am Montag, 10. Juli 2023, 16:35:36 CEST schrieb Mark Kettenis:
> > From: Heiko Stuebner <heiko@sntech.de>
> > Date: Mon, 10 Jul 2023 16:16:16 +0200
> > 
> > On Fri, 7 Jul 2023 19:22:17 +0300, Cristian Ciocaltea wrote:
> > > The 'regulator-init-microvolt' property is not currently supported by
> > > any driver, it was simply carried on from downstream kernels.
> > > 
> > > The problem is also indicated by the following dtbs_check warning:
> > > 
> > >   rk3588-rock-5b.dtb: pmic@0: regulators:dcdc-reg4: Unevaluated properties are not allowed ('regulator-init-microvolt' was unexpected)
> > > 
> > > [...]
> > 
> > Applied, thanks!
> > 
> > [1/1] arm64: dts: rockchip: Drop invalid regulator-init-microvolt property
> >       commit: 4d08b19629495b29601991d09d07865694c25199
> 
> This property *is used* by the drivers in U-Boot.  Dropping this from
> the Linux DTBs will likely result in broken boards the next time the
> U-Boot DTBs are synched again from Linux.  At least that is what
> happened before...
> 
> I think the right solution is to add this property to the DT binding
> instead.

I do have this vague memory of this coming up in the past, though don't
remember what the resolution was then? Though it definitly doesn't look
like the property was added to the binding in the meantime.

Also I think that setting up initial regulator state would be (and
seemingly is) for firmware to handle, so that property should instead
be in the -uboot.dtsi.

That DT isn't a configuration-space also is a decade long mantra.


Heiko



      parent reply	other threads:[~2023-07-10 15:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07 16:22 [PATCH] arm64: dts: rockchip: Drop invalid regulator-init-microvolt property Cristian Ciocaltea
2023-07-07 20:24 ` David Heidelberg
2023-07-10  7:43 ` AngeloGioacchino Del Regno
2023-07-10 14:16 ` Heiko Stuebner
2023-07-10 14:35   ` Mark Kettenis
2023-07-10 15:36     ` David Heidelberg
2023-07-10 15:39     ` Heiko Stuebner [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=4519023.cEBGB3zze1@phil \
    --to=heiko@sntech.de \
    --cc=amadeus@jmu.edu.cn \
    --cc=anarsoul@gmail.com \
    --cc=andyshrk@163.com \
    --cc=aurelien@aurel32.net \
    --cc=cnsztl@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=cristian.ciocaltea@collabora.com \
    --cc=d3adme4t@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.kardame@manjaro.org \
    --cc=festevam@denx.de \
    --cc=frank-w@public-files.de \
    --cc=frattaroli.nicolas@gmail.com \
    --cc=jagan@amarulasolutions.com \
    --cc=jbx6244@gmail.com \
    --cc=jensenhuang@friendlyarm.com \
    --cc=jonas@kwiboo.se \
    --cc=kernel@collabora.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lasstp5011@gmail.com \
    --cc=leo@nabam.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux.amoon@gmail.com \
    --cc=luiz.von.dentz@intel.com \
    --cc=macromorgan@hotmail.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=michael.riesch@wolfvision.net \
    --cc=pgwipeout@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=strit@manjaro.org \
    --cc=tobetter@gmail.com \
    --cc=wens@csie.org \
    --cc=wiagn233@outlook.com \
    --cc=zonyitoo@gmail.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