From: "H. Nikolaus Schaller" <hns@goldelico.com>
To: "Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Adam Ford" <aford173@gmail.com>,
"André Roth" <neolynx@gmail.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Viresh Kumar" <viresh.kumar@linaro.org>
Cc: linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
letux-kernel@openphoenux.org, kernel@pyra-handheld.com,
"H. Nikolaus Schaller" <hns@goldelico.com>
Subject: [RFC 5/5] ARM: dts: omap3-beagle: make explicitly compatible to ti,omap34xx
Date: Mon, 2 Sep 2019 12:55:51 +0200 [thread overview]
Message-ID: <150eb34a95b2e7ead8ac81a9ab275592ea31595b.1567421751.git.hns@goldelico.com> (raw)
In-Reply-To: <cover.1567421750.git.hns@goldelico.com>
Matching the ti-cpufreq driver needs to specify explicitly if
a board uses an omap34xx or omap36xx chip.
Signed-off-by: H. Nikolaus Schaller <hns@goldelico.com>
---
arch/arm/boot/dts/omap3-beagle.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap3-beagle.dts b/arch/arm/boot/dts/omap3-beagle.dts
index e3df3c166902..d47213c7a4d0 100644
--- a/arch/arm/boot/dts/omap3-beagle.dts
+++ b/arch/arm/boot/dts/omap3-beagle.dts
@@ -8,7 +8,7 @@
/ {
model = "TI OMAP3 BeagleBoard";
- compatible = "ti,omap3-beagle", "ti,omap3";
+ compatible = "ti,omap3-beagle", "ti,omap34xx", "ti,omap3";
cpus {
cpu@0 {
--
2.19.1
next prev parent reply other threads:[~2019-09-02 10:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 10:55 [RFC 0/5] OMAP3: convert opp-v1 to opp-v2 and read speed binned / 720MHz grade bits H. Nikolaus Schaller
2019-09-02 10:55 ` [RFC 1/5] cpufreq: ti-cpufreq: add support for omap34xx and omap36xx H. Nikolaus Schaller
2019-09-02 10:55 ` [RFC 2/5] ARM: dts: add support for opp-v2 " H. Nikolaus Schaller
2019-09-03 2:38 ` Viresh Kumar
2019-09-03 2:39 ` Viresh Kumar
2019-09-03 5:58 ` H. Nikolaus Schaller
2019-09-02 10:55 ` [RFC 3/5] ARM: dts: omap3-evm-37xx: fix compatible from omap3630 to omap36xx H. Nikolaus Schaller
2019-09-02 10:55 ` [RFC 4/5] ARM: dts: omap3-n950-n9: remove opp-v1 table H. Nikolaus Schaller
2019-09-03 2:36 ` Viresh Kumar
2019-09-03 6:01 ` H. Nikolaus Schaller
2019-09-03 6:14 ` Viresh Kumar
2019-09-03 6:23 ` H. Nikolaus Schaller
2019-09-03 6:28 ` Viresh Kumar
2019-09-03 6:34 ` H. Nikolaus Schaller
2019-09-02 10:55 ` H. Nikolaus Schaller [this message]
2019-09-03 13:40 ` [RFC 5/5] ARM: dts: omap3-beagle: make explicitly compatible to ti,omap34xx Tony Lindgren
2019-09-04 8:47 ` H. Nikolaus Schaller
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=150eb34a95b2e7ead8ac81a9ab275592ea31595b.1567421751.git.hns@goldelico.com \
--to=hns@goldelico.com \
--cc=aford173@gmail.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pyra-handheld.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=neolynx@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
--cc=viresh.kumar@linaro.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.