public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Gerlach <d-gerlach@ti.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Rob Herring <robh+dt@kernel.org>,
	Tony Lindgren <tony@atomide.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	Nishanth Menon <nm@ti.com>, Dave Gerlach <d-gerlach@ti.com>,
	Lukasz Majewski <lukma@denx.de>
Subject: [PATCH v5 4/4] cpufreq: dt: Don't use generic platdev driver for ti-cpufreq platforms
Date: Fri, 3 Feb 2017 11:29:29 -0600	[thread overview]
Message-ID: <20170203172929.23940-5-d-gerlach@ti.com> (raw)
In-Reply-To: <20170203172929.23940-1-d-gerlach@ti.com>

Some TI platforms, specifically those in the am33xx, am43xx, dra7xx, and
am57xx families of SoCs can make use of the ti-cpufreq driver to
selectively enable OPPs based on the exact configuration in use. The
ti-cpufreq is given the responsibility of creating the cpufreq-dt
platform device when the driver is in use so drop am33xx and dra7xx
from the cpufreq-dt-platdev driver so it is not created twice.

Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
---
 drivers/cpufreq/cpufreq-dt-platdev.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c
index 7fcaf26e8f81..921b4a6c3d16 100644
--- a/drivers/cpufreq/cpufreq-dt-platdev.c
+++ b/drivers/cpufreq/cpufreq-dt-platdev.c
@@ -87,8 +87,6 @@ static const struct of_device_id machines[] __initconst = {
 	{ .compatible = "socionext,uniphier-ld11", },
 	{ .compatible = "socionext,uniphier-ld20", },
 
-	{ .compatible = "ti,am33xx", },
-	{ .compatible = "ti,dra7", },
 	{ .compatible = "ti,omap2", },
 	{ .compatible = "ti,omap3", },
 	{ .compatible = "ti,omap4", },
-- 
2.11.0


  parent reply	other threads:[~2017-02-03 17:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-03 17:29 [PATCH v5 0/4] cpufreq: Introduce TI CPUFreq/OPP Driver Dave Gerlach
     [not found] ` <20170203172929.23940-1-d-gerlach-l0cyMroinI0@public.gmane.org>
2017-02-03 17:29   ` [PATCH v5 1/4] PM / OPP: Expose _of_get_opp_desc_node as dev_pm_opp API Dave Gerlach
2017-02-03 17:29   ` [PATCH v5 3/4] cpufreq: ti: Add cpufreq driver to determine available OPPs at runtime Dave Gerlach
2017-02-03 17:29 ` [PATCH v5 2/4] Documentation: dt: add bindings for ti-cpufreq Dave Gerlach
2017-02-08 14:44   ` Rob Herring
2017-02-08 14:45     ` Dave Gerlach
2017-02-09  0:02       ` Rafael J. Wysocki
2017-02-09 15:36         ` Dave Gerlach
2017-02-09 15:35   ` [PATCH v6 " Dave Gerlach
2017-02-09 16:01     ` Rob Herring
2017-02-09 22:03     ` Rafael J. Wysocki
2017-02-10  3:13       ` Viresh Kumar
2017-02-10 12:28         ` Rafael J. Wysocki
     [not found]           ` <3046998.7dExGlRDb3-yvgW3jdyMHm1GS7QM15AGw@public.gmane.org>
2017-02-10 20:55             ` Dave Gerlach
2017-02-03 17:29 ` Dave Gerlach [this message]
2017-02-03 23:23 ` [PATCH v5 0/4] cpufreq: Introduce TI CPUFreq/OPP Driver Lukasz Majewski

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=20170203172929.23940-5-d-gerlach@ti.com \
    --to=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=lukma@denx.de \
    --cc=nm@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox