From: Viresh Kumar <viresh.kumar@linaro.org>
To: sean.wang@mediatek.com
Cc: robh+dt@kernel.org, matthias.bgg@gmail.com, mark.rutland@arm.com,
devicetree@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 06/12] arm64: dts: mt7622: add cpufreq related device nodes
Date: Thu, 4 Jan 2018 15:15:26 +0530 [thread overview]
Message-ID: <20180104094526.GC19742@vireshk-i7> (raw)
In-Reply-To: <7e61305594b7bbcdefe31f64ca5603cbdbd9f4cf.1515057696.git.sean.wang@mediatek.com>
On 04-01-18, 17:40, sean.wang@mediatek.com wrote:
> diff --git a/arch/arm64/boot/dts/mediatek/mt7622.dtsi b/arch/arm64/boot/dts/mediatek/mt7622.dtsi
> index 5b7f0a3..90b2761 100644
> --- a/arch/arm64/boot/dts/mediatek/mt7622.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt7622.dtsi
> @@ -18,6 +18,50 @@
> #address-cells = <2>;
> #size-cells = <2>;
>
> + cpu_opp_table: opp_table {
Rob recently asked me to do name the nodes with "-" instead of "_". So
this becomes "cpu_opp_table: opp-table {" then.
--
viresh
next prev parent reply other threads:[~2018-01-04 9:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 9:40 [PATCH 00/12] add dts nodes to MT7622 SoC sean.wang-NuS5LvNUpcJWk0Htik3J/w
2018-01-04 9:40 ` [PATCH 01/12] dt-bindings: clock: mediatek: add missing required #reset-cells sean.wang
[not found] ` <084288e2520f9bd3ccdb3cf7aeef8ebcae48e6d7.1515057696.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2018-01-09 3:34 ` Rob Herring
2018-01-04 9:40 ` [PATCH 02/12] arm64: dts: mt7622: add clock controller device nodes sean.wang
2018-01-04 9:40 ` [PATCH 03/12] arm64: dts: mt7622: add power domain " sean.wang
2018-01-04 9:40 ` [PATCH 04/12] arm64: dts: mt7622: add pinctrl related " sean.wang
2018-01-04 9:40 ` [PATCH 05/12] arm64: dts: mt7622: add PMIC MT6380 related nodes sean.wang
[not found] ` <0109846a8a501ca3cae33acfceb919960fddfcbf.1515057696.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2018-01-04 10:27 ` Philippe Ombredanne
[not found] ` <CAOFm3uF0WHO6_Y6dKu3DnAd759tA2hNQs=0-P86s1A0e==27Ow-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-05 3:42 ` Sean Wang
2018-01-05 8:21 ` Philippe Ombredanne
2018-01-12 3:33 ` Sean Wang
2018-01-04 9:40 ` [PATCH 06/12] arm64: dts: mt7622: add cpufreq related device nodes sean.wang
2018-01-04 9:45 ` Viresh Kumar [this message]
2018-01-04 10:01 ` Sean Wang
2018-01-04 9:40 ` [PATCH 07/12] arm64: dts: mt7622: turn uart0 clock to real ones sean.wang
2018-01-04 9:40 ` [PATCH 08/12] arm64: dts: mt7622: add SoC and peripheral related device nodes sean.wang
[not found] ` <cover.1515057696.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2018-01-04 9:40 ` [PATCH 09/12] arm64: dts: mt7622: add flash " sean.wang-NuS5LvNUpcJWk0Htik3J/w
2018-01-04 9:41 ` [PATCH 10/12] arm64: dts: mt7622: add ethernet " sean.wang
2018-01-04 9:41 ` [PATCH 11/12] arm64: dts: mt7622: add PCIe " sean.wang
2018-01-04 9:41 ` [PATCH 12/12] arm64: dts: mt7622: add SATA " sean.wang
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=20180104094526.GC19742@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.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;
as well as URLs for NNTP newsgroup(s).