From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] devicetree: bindings: Document Kryo cpu
Date: Tue, 17 Nov 2015 17:12:26 -0800 [thread overview]
Message-ID: <1447809149-29724-2-git-send-email-sboyd@codeaurora.org> (raw)
In-Reply-To: <1447809149-29724-1-git-send-email-sboyd@codeaurora.org>
Document the compatible string for the Kryo family of qcom cpus.
Cc: <devicetree@vger.kernel.org>
Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
---
Documentation/devicetree/bindings/arm/cpus.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/cpus.txt b/Documentation/devicetree/bindings/arm/cpus.txt
index 3a07a87fef20..6008b99ccb2b 100644
--- a/Documentation/devicetree/bindings/arm/cpus.txt
+++ b/Documentation/devicetree/bindings/arm/cpus.txt
@@ -177,6 +177,7 @@ nodes to be present and contain the properties described below.
"marvell,sheeva-v5"
"nvidia,tegra132-denver"
"qcom,krait"
+ "qcom,kryo"
"qcom,scorpion"
- enable-method
Value type: <stringlist>
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-11-18 1:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 1:12 [PATCH 0/4] Add DTS for MSM8996 SoC and MTP Stephen Boyd
2015-11-18 1:12 ` Stephen Boyd [this message]
2015-11-18 23:07 ` [PATCH 1/4] devicetree: bindings: Document Kryo cpu Rob Herring
2015-11-18 1:12 ` [PATCH 2/4] arm64: dts: Add msm8996 SoC and MTP board support Stephen Boyd
2015-11-18 5:06 ` kbuild test robot
2015-11-18 19:24 ` Stephen Boyd
2015-11-23 9:12 ` Rajendra Nayak
2015-11-24 0:43 ` Stephen Boyd
2015-11-18 1:12 ` [PATCH 3/4] arm64: dts: qcom: Add pm8994, pmi8994, pm8004 PMIC skeletons Stephen Boyd
2015-11-18 1:12 ` [PATCH 4/4] arm64: dts: qcom: Add pm8994 gpios and MPPs Stephen Boyd
2015-11-18 4:13 ` [PATCH 0/4] Add DTS for MSM8996 SoC and MTP Andy Gross
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=1447809149-29724-2-git-send-email-sboyd@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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 NNTP newsgroup(s).