From: Viresh Kumar <viresh.kumar@linaro.org>
To: Dave Gerlach <d-gerlach@ti.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
Tony Lindgren <tony@atomide.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>, Nishanth Menon <nm@ti.com>,
Yegor Yefremov <yegorslists@googlemail.com>
Subject: Re: [PATCH 2/8] ARM: dts: am33xx: Move to operating-points-v2 table and ti-cpufreq driver
Date: Thu, 19 May 2016 10:11:21 +0530 [thread overview]
Message-ID: <20160519044121.GD32001@vireshk-i7> (raw)
In-Reply-To: <f30e0313514cdbb9c3b0a83bbb96f05f2e179775.1463606963.git.d-gerlach@ti.com>
On 18-05-16, 18:36, Dave Gerlach wrote:
> + cpu0_opp_table: opp_table0 {
> + compatible = "operating-points-v2";
> +
> + /*
> + * The three following nodes are marked with opp-suspend
> + * because the can not be enabled simultaneously on a
> + * single SoC.
> + */
> + opp50@300000000 {
> + opp-hz = /bits/ 64 <300000000>;
> + opp-microvolt = <950000 931000 969000>;
> + opp-supported-hw = <0x06 0x0010>;
Is there any place in either of the patchsets you have sent, that details the
usage of the above two values? I mean which defines, what is 0x6 and what is
0x1 ?
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/8] ARM: dts: am33xx: Move to operating-points-v2 table and ti-cpufreq driver
Date: Thu, 19 May 2016 10:11:21 +0530 [thread overview]
Message-ID: <20160519044121.GD32001@vireshk-i7> (raw)
In-Reply-To: <f30e0313514cdbb9c3b0a83bbb96f05f2e179775.1463606963.git.d-gerlach@ti.com>
On 18-05-16, 18:36, Dave Gerlach wrote:
> + cpu0_opp_table: opp_table0 {
> + compatible = "operating-points-v2";
> +
> + /*
> + * The three following nodes are marked with opp-suspend
> + * because the can not be enabled simultaneously on a
> + * single SoC.
> + */
> + opp50 at 300000000 {
> + opp-hz = /bits/ 64 <300000000>;
> + opp-microvolt = <950000 931000 969000>;
> + opp-supported-hw = <0x06 0x0010>;
Is there any place in either of the patchsets you have sent, that details the
usage of the above two values? I mean which defines, what is 0x6 and what is
0x1 ?
--
viresh
next prev parent reply other threads:[~2016-05-19 4:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 23:36 [PATCH 0/8] ARM: dts: Add operating-points-v2 tables for TI platforms Dave Gerlach
2016-05-18 23:36 ` Dave Gerlach
2016-05-18 23:36 ` [PATCH 2/8] ARM: dts: am33xx: Move to operating-points-v2 table and ti-cpufreq driver Dave Gerlach
2016-05-18 23:36 ` Dave Gerlach
2016-05-19 4:41 ` Viresh Kumar [this message]
2016-05-19 4:41 ` Viresh Kumar
2016-05-18 23:36 ` [PATCH 3/8] ARM: dts: am335x-boneblack: Enable 1GHz OPP for cpu Dave Gerlach
2016-05-18 23:36 ` Dave Gerlach
2016-05-18 23:36 ` [PATCH 4/8] ARM: dts: am4372: Add operating-points-v2 table Dave Gerlach
2016-05-18 23:36 ` Dave Gerlach
2016-05-18 23:36 ` [PATCH 5/8] ARM: dts: am437x-gp-evm: Hook dcdc2 as the cpu0-supply Dave Gerlach
2016-05-18 23:36 ` Dave Gerlach
[not found] ` <cover.1463606963.git.d-gerlach-l0cyMroinI0@public.gmane.org>
2016-05-18 23:36 ` [PATCH 1/8] ARM: dts: am335x: Update MPU regulator range for TI boards Dave Gerlach
2016-05-18 23:36 ` Dave Gerlach
2016-05-18 23:36 ` [PATCH 6/8] ARM: dts: dra7: Add dt node for the syscon control module wkup Dave Gerlach
2016-05-18 23:36 ` Dave Gerlach
2016-05-18 23:36 ` [PATCH 7/8] ARM: dts: dra7: Move cpus node to parent dts for dra74x and dra72x Dave Gerlach
2016-05-18 23:36 ` Dave Gerlach
2016-05-18 23:36 ` [PATCH 8/8] ARM: dts: dra7: Move to operating-points-v2 table Dave Gerlach
2016-05-18 23:36 ` Dave Gerlach
2016-05-19 4:47 ` [PATCH 0/8] ARM: dts: Add operating-points-v2 tables for TI platforms Viresh Kumar
2016-05-19 4:47 ` Viresh Kumar
2016-06-10 11:04 ` Tony Lindgren
2016-06-10 11:04 ` Tony Lindgren
2016-06-10 14:50 ` Nishanth Menon
2016-06-10 14:50 ` Nishanth Menon
2016-06-11 2:44 ` Viresh Kumar
2016-06-11 2:44 ` Viresh Kumar
2016-06-20 16:57 ` Dave Gerlach
2016-06-20 16:57 ` Dave Gerlach
2016-09-01 2:46 ` Dave Gerlach
2016-09-01 2:46 ` Dave Gerlach
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=20160519044121.GD32001@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
--cc=yegorslists@googlemail.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 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.