From: "embedded (VIVAVIS AG)" <embedded-dQ8pE230Wp9BDgjK7y7TUQ@public.gmane.org>
To: "devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Voltage and current regulator: usage of 'regulators' parent node in device tree
Date: Mon, 23 Aug 2021 12:53:36 +0000 [thread overview]
Message-ID: <809518e1649a469cb4fc6fffd9bf427c@vivavis.com> (raw)
Dear maintainer,
I see a lot of Device trees wrapping the regulator nodes within a parent node
like this
regulators {
compatible = "simple-bus";
#address-cells = <1>;
#size-cells = <0>;
reg_p3v3: regulator@0 {
compatible = "regulator-fixed";
[...]
regulator-always-on;
};
[...]
Contrary to that, patches exist removing the 'regulators' node, because the 'simple-bus'
doesn't really exist in hardware. Unfortunately, the documentation is unclear about
wrapping regulator nodes like shown above.
Should I avoid the parent 'regulators' node and why?
Is the given naming schema in fixed-regulator.yaml best practice to follow?
reg_xyz: regulator-xyz {
compatible = "regulator-fixed";
regulator-name = "xyz";
Thank you for clarification.
Carsten Stelling
next reply other threads:[~2021-08-23 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 12:53 embedded (VIVAVIS AG) [this message]
[not found] ` <809518e1649a469cb4fc6fffd9bf427c-dQ8pE230Wp9BDgjK7y7TUQ@public.gmane.org>
2021-09-07 15:40 ` AW: Voltage and current regulator: usage of 'regulators' parent node in device tree embedded (VIVAVIS AG)
2021-09-07 18:16 ` Rob Herring
[not found] ` <CAL_JsqLBiq0+MnYQ0=vMEDe_n+gHAT8PP6VO=Quj-A4yOCu_6w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-09-08 8:38 ` AW: " embedded (VIVAVIS AG)
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=809518e1649a469cb4fc6fffd9bf427c@vivavis.com \
--to=embedded-dq8pe230wp9bdgjk7y7tuq@public.gmane.org \
--cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).