From: Viresh Kumar <viresh.kumar@linaro.org>
To: Dave Gerlach <d-gerlach@ti.com>
Cc: Keerthy <j-keerthy@ti.com>, Simon Horman <horms@verge.net.au>,
Rafael Wysocki <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
geert@linux-m68k.org, maxime.ripard@free-electrons.com,
wens@csie.org, xuwei5@hisilicon.com, kgene@kernel.org,
krzk@kernel.org, yamada.masahiro@socionext.com,
jun.nie@linaro.org, baoyou.xie@linaro.org,
linux-kernel@vger.kernel.org
Subject: Re: [1/2] cpufreq: dt-platdev: Automatically create cpufreq device with OPP v2
Date: Tue, 19 Sep 2017 11:46:35 -0700 [thread overview]
Message-ID: <20170919184635.GA30848@ubuntu> (raw)
In-Reply-To: <7c607393-2a3d-1e5e-7b54-3745cee416e3@ti.com>
On 11-09-17, 09:18, Dave Gerlach wrote:
> Yes, ti-cpufreq registers the cpufreq-dt platdev in order to ensure the
> ti-cpufreq driver probes first and provides the necessary opp-supported-hw for
> cpufreq-dt. This applies to am335x, am437x, dra7xx, and am57xx. I suppose these
> platforms will need to be added to the 'blacklist' to prevent the cpufreq-dt
> platdev from being created automatically, unless there is a better way to handle
> this dependency...
Right. Patches are already on the list to fix all platforms that had such
issues.
--
viresh
next prev parent reply other threads:[~2017-09-19 18:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 13:13 [1/2] cpufreq: dt-platdev: Automatically create cpufreq device with OPP v2 Viresh Kumar
2017-08-21 13:17 ` Simon Horman
2017-08-29 10:11 ` Viresh Kumar
2017-09-11 12:13 ` Keerthy
2017-09-11 12:13 ` Keerthy
2017-09-11 14:18 ` Dave Gerlach
2017-09-11 14:18 ` Dave Gerlach
2017-09-19 18:46 ` Viresh Kumar [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-16 5:37 [PATCH 1/2] " Viresh Kumar
2017-08-21 13:17 ` [1/2] " Simon Horman
2017-08-23 3:48 ` Masahiro Yamada
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=20170919184635.GA30848@ubuntu \
--to=viresh.kumar@linaro.org \
--cc=baoyou.xie@linaro.org \
--cc=d-gerlach@ti.com \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=j-keerthy@ti.com \
--cc=jun.nie@linaro.org \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=rjw@rjwysocki.net \
--cc=vincent.guittot@linaro.org \
--cc=wens@csie.org \
--cc=xuwei5@hisilicon.com \
--cc=yamada.masahiro@socionext.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.