From: Rob Herring <robh@kernel.org>
To: Yangtao Li <tiny.windzz@gmail.com>
Cc: vireshk@kernel.org, nm@ti.com, sboyd@kernel.org,
mark.rutland@arm.com, maxime.ripard@bootlin.com, wens@csie.org,
rjw@rjwysocki.net, davem@davemloft.net,
mchehab+samsung@kernel.org, gregkh@linuxfoundation.org,
nicolas.ferre@microchip.com, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] dt-bindings: cpufreq: Document allwinner,cpu-operating-points-v2
Date: Fri, 26 Apr 2019 16:15:40 -0500 [thread overview]
Message-ID: <20190426211540.GA890@bogus> (raw)
In-Reply-To: <20190410174139.20012-3-tiny.windzz@gmail.com>
On Wed, Apr 10, 2019 at 01:41:39PM -0400, Yangtao Li wrote:
> Allwinner Process Voltage Scaling Tables defines the voltage and
> frequency value based on the speedbin blown in the efuse combination.
> The sunxi-cpufreq-nvmem driver reads the efuse value from the SoC to
> provide the OPP framework with required information.
> This is used to determine the voltage and frequency value for each
> OPP of operating-points-v2 table when it is parsed by the OPP framework.
>
> The "allwinner,cpu-operating-points-v2" DT extends the "operating-points-v2"
> with following parameters:
> - nvmem-cells (NVMEM area containig the speedbin information)
> - opp-microvolt-<name>: voltage in micro Volts.
> At runtime, the platform can pick a <name> and matching
> opp-microvolt-<name> property.
> HW: <name>:
> sun50iw-h6 speed0 speed1 speed2
We already have at least one way to support speed bins with QC kryo
binding. Why do we need a different way?
>
> Signed-off-by: Yangtao Li <tiny.windzz@gmail.com>
> ---
> .../bindings/opp/sunxi-nvmem-cpufreq.txt | 168 ++++++++++++++++++
> 1 file changed, 168 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/opp/sunxi-nvmem-cpufreq.txt
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Yangtao Li <tiny.windzz@gmail.com>
Cc: nm@ti.com, mark.rutland@arm.com, linux-pm@vger.kernel.org,
maxime.ripard@bootlin.com, vireshk@kernel.org, rjw@rjwysocki.net,
linux-kernel@vger.kernel.org, sboyd@kernel.org, wens@csie.org,
linux-arm-kernel@lists.infradead.org, gregkh@linuxfoundation.org,
mchehab+samsung@kernel.org, davem@davemloft.net,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 2/2] dt-bindings: cpufreq: Document allwinner,cpu-operating-points-v2
Date: Fri, 26 Apr 2019 16:15:40 -0500 [thread overview]
Message-ID: <20190426211540.GA890@bogus> (raw)
In-Reply-To: <20190410174139.20012-3-tiny.windzz@gmail.com>
On Wed, Apr 10, 2019 at 01:41:39PM -0400, Yangtao Li wrote:
> Allwinner Process Voltage Scaling Tables defines the voltage and
> frequency value based on the speedbin blown in the efuse combination.
> The sunxi-cpufreq-nvmem driver reads the efuse value from the SoC to
> provide the OPP framework with required information.
> This is used to determine the voltage and frequency value for each
> OPP of operating-points-v2 table when it is parsed by the OPP framework.
>
> The "allwinner,cpu-operating-points-v2" DT extends the "operating-points-v2"
> with following parameters:
> - nvmem-cells (NVMEM area containig the speedbin information)
> - opp-microvolt-<name>: voltage in micro Volts.
> At runtime, the platform can pick a <name> and matching
> opp-microvolt-<name> property.
> HW: <name>:
> sun50iw-h6 speed0 speed1 speed2
We already have at least one way to support speed bins with QC kryo
binding. Why do we need a different way?
>
> Signed-off-by: Yangtao Li <tiny.windzz@gmail.com>
> ---
> .../bindings/opp/sunxi-nvmem-cpufreq.txt | 168 ++++++++++++++++++
> 1 file changed, 168 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/opp/sunxi-nvmem-cpufreq.txt
_______________________________________________
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:[~2019-04-26 21:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 17:41 [PATCH v3 0/2] cpufreq: Add sunxi nvmem based CPU scaling driver Yangtao Li
2019-04-10 17:41 ` Yangtao Li
2019-04-10 17:41 ` [PATCH v3 1/2] " Yangtao Li
2019-04-10 17:41 ` Yangtao Li
2019-04-11 4:03 ` Viresh Kumar
2019-04-11 4:03 ` Viresh Kumar
2019-04-11 8:09 ` Maxime Ripard
2019-04-11 8:09 ` Maxime Ripard
2019-04-11 18:36 ` Frank Lee
2019-04-11 18:36 ` Frank Lee
2019-04-11 18:41 ` Frank Lee
2019-04-11 18:41 ` Frank Lee
2019-04-10 17:41 ` [PATCH v3 2/2] dt-bindings: cpufreq: Document allwinner,cpu-operating-points-v2 Yangtao Li
2019-04-10 17:41 ` [PATCH v3 2/2] dt-bindings: cpufreq: Document allwinner, cpu-operating-points-v2 Yangtao Li
2019-04-26 21:15 ` Rob Herring [this message]
2019-04-26 21:15 ` [PATCH v3 2/2] dt-bindings: cpufreq: Document allwinner,cpu-operating-points-v2 Rob Herring
2019-04-28 9:53 ` Frank Lee
2019-04-28 9:53 ` [PATCH v3 2/2] dt-bindings: cpufreq: Document allwinner, cpu-operating-points-v2 Frank Lee
2019-04-29 16:18 ` [PATCH v3 2/2] dt-bindings: cpufreq: Document allwinner,cpu-operating-points-v2 Rob Herring
2019-04-29 16:18 ` [PATCH v3 2/2] dt-bindings: cpufreq: Document allwinner, cpu-operating-points-v2 Rob Herring
2019-04-30 4:42 ` [PATCH v3 2/2] dt-bindings: cpufreq: Document allwinner,cpu-operating-points-v2 Viresh Kumar
2019-04-30 4:42 ` Viresh Kumar
2019-05-01 3:44 ` Frank Lee
2019-05-01 3:44 ` [PATCH v3 2/2] dt-bindings: cpufreq: Document allwinner, cpu-operating-points-v2 Frank Lee
2019-05-06 17:27 ` [PATCH v3 2/2] dt-bindings: cpufreq: Document allwinner,cpu-operating-points-v2 Frank Lee
2019-05-06 17:27 ` [PATCH v3 2/2] dt-bindings: cpufreq: Document allwinner, cpu-operating-points-v2 Frank Lee
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=20190426211540.GA890@bogus \
--to=robh@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=mchehab+samsung@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@kernel.org \
--cc=tiny.windzz@gmail.com \
--cc=vireshk@kernel.org \
--cc=wens@csie.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.