From: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
To: Doug Anderson <dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: "Chris Zhong" <zyw-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
"Heiko Stübner" <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>,
"Tao Huang" <huangtao-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
"Eddie Cai" <cf-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
zhangqing <zhangqing-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
"Rob Herring" <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"Pawel Moll" <Pawel.Moll-5wv7dgnIgG8@public.gmane.org>,
"Ian Campbell"
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
"Kumar Gala" <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"Lee Jones" <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH 2/2] dt-bindings: add devicetree bindings for st-pwm regulator
Date: Wed, 17 Sep 2014 20:46:12 +0100 [thread overview]
Message-ID: <20140917194612.GE7983@leverpostej> (raw)
In-Reply-To: <CAD=FV=WCQ4oU1O9JcZ9SuwWJ7g+GLsUiE=wmQQoWvL41o24eWg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Wed, Sep 17, 2014 at 07:16:23PM +0100, Doug Anderson wrote:
> Chris,
>
> On Wed, Sep 17, 2014 at 6:08 AM, Chris Zhong <zyw-TNX95d0MmH7DzftRWevZcw@public.gmane.org> wrote:
> > Document the st-pwm regulator
> >
> > Signed-off-by: Chris Zhong <zyw-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
> >
> > ---
> >
> > .../devicetree/bindings/regulator/st-pwm.txt | 35 ++++++++++++++++++++
> > 1 file changed, 35 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/regulator/st-pwm.txt
> >
> > diff --git a/Documentation/devicetree/bindings/regulator/st-pwm.txt b/Documentation/devicetree/bindings/regulator/st-pwm.txt
> > new file mode 100644
> > index 0000000..38fec1d
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/regulator/st-pwm.txt
> > @@ -0,0 +1,35 @@
> > +st pwm regulator bindings
> > +
> > +Required properties:
> > + - compatible: "pwm-regulator"
>
> This compatible string doesn't include "st,b2105-pwm-regulator".
>
> Should be something like:
>
> - compatible: Should be "pwm-regulator" to get voltage table / regulator
> period from the device tree. Deprecated: if "st,b2105-pwm-regulator" then
> voltage table and regulator will be handled by the driver.
Do a list, with a bullet point for each string, like:
- compatible: should contain:
* "pwm-regulator" when using voltage-table
* "st,b2105-pwm-regulator" for .... (DEPRECATED)
That's easier to extend and it's clearer as to which strings the
comments above apply to.
>
> Assuming that everyone is OK calling "st,b2105-pwm-regulator" the
> deprecated way of doing things.
>
>
> > + - pwms: OF device-tree PWM specification (see PWM binding pwm.txt)
> > + - voltage-table: voltage and duty table, include 2 merbers in each set of
> > + brackets, first one is voltage(unit: uv), the next is duty(unit: percent)
> > + - pwm-reg-period: duration (in nanoseconds) of one cycle
Perhaps just 'period-ns'? We know it applies to the PWM we're using as a
regulator.
That said, is this even needed? The pwm bindings describe that the
period would typically be described in the pwm-specifier, so duplicating
that feels wrong.
>
> The voltage-table and pwm-reg-period should not be required if we're
> using "st,b2105-pwm-regulator". If someone lists both
> "st,b2105-pwm-regulator" and "pwm-regulator" then I'd assume that
> you'd allow them to override via the device tree but fallback to the
> old hardcoded values.
>
>
> > +
> > +Any property defined as part of the core regulator binding defined in
> > +regulator.txt can also be used.
> > +
> > +Example:
> > + pwm_regulator {
> > + compatible = "st,b2105-pwm-regulator;
> > + pwms = <&pwm1 0 1000000 0>;
> > +
> > + voltage-table = <1114000 0>,
> > + <1095000 10>,
> > + <1076000 20>,
> > + <1056000 30>,
> > + <1036000 40>,
> > + <1016000 50>;
> > +
> > + pwm-reg-period = <8448>;
> > + regulators {
> > + vdd_logic: pwm-regulator {
> > + regulator-always-on;
> > + regulator-boot-on;
> > + regulator-min-microvolt = <1016000>;
> > + regulator-max-microvolt = <1114000>;
> > + regulator-name = "vdd_logic";
> > + };
> > + };
>
> I _think_ that the "regulators" subnode and the "pwm-regulator"
> subnode are not needed at all and should be removed. Other instances
> of devices that are "just" regulators don't have it (like
> fixed-regulator, gpio-regulator, etc).
Yes. The pwm_regulator node _is_ the regulator, so the subnode is
bizarre.
Mark.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland@arm.com>
To: Doug Anderson <dianders@chromium.org>
Cc: "Chris Zhong" <zyw@rock-chips.com>,
"Heiko Stübner" <heiko@sntech.de>,
"Tao Huang" <huangtao@rock-chips.com>,
"Eddie Cai" <cf@rock-chips.com>,
zhangqing <zhangqing@rock-chips.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Pawel Moll" <Pawel.Moll@arm.com>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Kumar Gala" <galak@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"Lee Jones" <lee.jones@linaro.org>
Subject: Re: [PATCH 2/2] dt-bindings: add devicetree bindings for st-pwm regulator
Date: Wed, 17 Sep 2014 20:46:12 +0100 [thread overview]
Message-ID: <20140917194612.GE7983@leverpostej> (raw)
In-Reply-To: <CAD=FV=WCQ4oU1O9JcZ9SuwWJ7g+GLsUiE=wmQQoWvL41o24eWg@mail.gmail.com>
On Wed, Sep 17, 2014 at 07:16:23PM +0100, Doug Anderson wrote:
> Chris,
>
> On Wed, Sep 17, 2014 at 6:08 AM, Chris Zhong <zyw@rock-chips.com> wrote:
> > Document the st-pwm regulator
> >
> > Signed-off-by: Chris Zhong <zyw@rock-chips.com>
> >
> > ---
> >
> > .../devicetree/bindings/regulator/st-pwm.txt | 35 ++++++++++++++++++++
> > 1 file changed, 35 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/regulator/st-pwm.txt
> >
> > diff --git a/Documentation/devicetree/bindings/regulator/st-pwm.txt b/Documentation/devicetree/bindings/regulator/st-pwm.txt
> > new file mode 100644
> > index 0000000..38fec1d
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/regulator/st-pwm.txt
> > @@ -0,0 +1,35 @@
> > +st pwm regulator bindings
> > +
> > +Required properties:
> > + - compatible: "pwm-regulator"
>
> This compatible string doesn't include "st,b2105-pwm-regulator".
>
> Should be something like:
>
> - compatible: Should be "pwm-regulator" to get voltage table / regulator
> period from the device tree. Deprecated: if "st,b2105-pwm-regulator" then
> voltage table and regulator will be handled by the driver.
Do a list, with a bullet point for each string, like:
- compatible: should contain:
* "pwm-regulator" when using voltage-table
* "st,b2105-pwm-regulator" for .... (DEPRECATED)
That's easier to extend and it's clearer as to which strings the
comments above apply to.
>
> Assuming that everyone is OK calling "st,b2105-pwm-regulator" the
> deprecated way of doing things.
>
>
> > + - pwms: OF device-tree PWM specification (see PWM binding pwm.txt)
> > + - voltage-table: voltage and duty table, include 2 merbers in each set of
> > + brackets, first one is voltage(unit: uv), the next is duty(unit: percent)
> > + - pwm-reg-period: duration (in nanoseconds) of one cycle
Perhaps just 'period-ns'? We know it applies to the PWM we're using as a
regulator.
That said, is this even needed? The pwm bindings describe that the
period would typically be described in the pwm-specifier, so duplicating
that feels wrong.
>
> The voltage-table and pwm-reg-period should not be required if we're
> using "st,b2105-pwm-regulator". If someone lists both
> "st,b2105-pwm-regulator" and "pwm-regulator" then I'd assume that
> you'd allow them to override via the device tree but fallback to the
> old hardcoded values.
>
>
> > +
> > +Any property defined as part of the core regulator binding defined in
> > +regulator.txt can also be used.
> > +
> > +Example:
> > + pwm_regulator {
> > + compatible = "st,b2105-pwm-regulator;
> > + pwms = <&pwm1 0 1000000 0>;
> > +
> > + voltage-table = <1114000 0>,
> > + <1095000 10>,
> > + <1076000 20>,
> > + <1056000 30>,
> > + <1036000 40>,
> > + <1016000 50>;
> > +
> > + pwm-reg-period = <8448>;
> > + regulators {
> > + vdd_logic: pwm-regulator {
> > + regulator-always-on;
> > + regulator-boot-on;
> > + regulator-min-microvolt = <1016000>;
> > + regulator-max-microvolt = <1114000>;
> > + regulator-name = "vdd_logic";
> > + };
> > + };
>
> I _think_ that the "regulators" subnode and the "pwm-regulator"
> subnode are not needed at all and should be removed. Other instances
> of devices that are "just" regulators don't have it (like
> fixed-regulator, gpio-regulator, etc).
Yes. The pwm_regulator node _is_ the regulator, so the subnode is
bizarre.
Mark.
next prev parent reply other threads:[~2014-09-17 19:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 13:07 [PATCH 0/2] regulator: get voltage & duty table from dts for st-pwm Chris Zhong
2014-09-17 13:07 ` Chris Zhong
2014-09-17 13:07 ` [PATCH 1/2] regulator: st-pwm: get voltage and duty table from dts Chris Zhong
2014-09-17 15:15 ` Heiko Stübner
2014-09-17 16:51 ` Mark Brown
2014-09-17 16:54 ` Doug Anderson
2014-09-18 1:37 ` Chris Zhong
2014-09-18 3:36 ` Doug Anderson
2014-09-17 18:28 ` Doug Anderson
2014-09-17 21:26 ` Lee Jones
2014-09-17 13:08 ` [PATCH 2/2] dt-bindings: add devicetree bindings for st-pwm regulator Chris Zhong
[not found] ` <1410959280-29662-3-git-send-email-zyw-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-09-17 18:16 ` Doug Anderson
2014-09-17 18:16 ` Doug Anderson
[not found] ` <CAD=FV=WCQ4oU1O9JcZ9SuwWJ7g+GLsUiE=wmQQoWvL41o24eWg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-17 18:35 ` Mark Brown
2014-09-17 18:35 ` Mark Brown
2014-09-17 19:46 ` Mark Rutland [this message]
2014-09-17 19:46 ` Mark Rutland
2014-09-17 21:22 ` Lee Jones
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=20140917194612.GE7983@leverpostej \
--to=mark.rutland-5wv7dgnigg8@public.gmane.org \
--cc=Pawel.Moll-5wv7dgnIgG8@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=cf-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org \
--cc=huangtao-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org \
--cc=lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=zhangqing-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=zyw-TNX95d0MmH7DzftRWevZcw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.