From: Viresh Kumar <viresh.kumar@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linaro-kernel@lists.linaro.org,
Rafael Wysocki <rjw@rjwysocki.net>,
arnd.bergmann@linaro.org, kgene.kim@samsung.com, heiko@sntech.de,
xf@rock-chips.com, mmcclint@codeaurora.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH 0/3] cpufreq: dt: Create platform device from generic code
Date: Fri, 25 Mar 2016 10:11:24 +0530 [thread overview]
Message-ID: <20160325044124.GN22062@vireshk-i7> (raw)
In-Reply-To: <4531000.a0G78BGFu1@wuerfel>
On 24-03-16, 15:16, Arnd Bergmann wrote:
> Hmm, can you give an example where this is needed?
I don't remember them, but I am quite sure that I have seen people
asking for that support again and again.
> I assume you are
> thinking of some clock controller or regulator that gets initialized
> after the cpufreq driver, right?
Yeah.
> Are there any that are in loadable modules, rather than just later
> in the init sequence for built-in drivers?
Maybe both, don't remember. Sorry.
Over that, independent of what the users are doing today, I think its
important to support defer probing for anyone that wants to use it.
> I think we do care about compatibility there, but there are clearly
> other ways to handle the special case for opp-v1 if we want to.
Okay, and what are those ? There is only one platform which has used
the pdata, mvebu.
--
viresh
next prev parent reply other threads:[~2016-03-25 4:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 6:40 [PATCH 0/3] cpufreq: dt: Create platform device from generic code Viresh Kumar
2016-03-24 6:40 ` [PATCH 1/3] cpufreq: dt: Include types.h from cpufreq-dt.h Viresh Kumar
2016-03-24 6:40 ` [PATCH 2/3] cpufreq: dt: Add generic platform-device creation support Viresh Kumar
2016-03-29 4:03 ` Krzysztof Kozlowski
2016-03-24 6:40 ` [PATCH 3/3] cpufreq: exynos: Use generic platdev driver Viresh Kumar
2016-03-29 2:35 ` Krzysztof Kozlowski
2016-03-29 2:38 ` Viresh Kumar
2016-03-29 4:10 ` Krzysztof Kozlowski
2016-03-29 4:18 ` Viresh Kumar
2016-03-29 4:19 ` Viresh Kumar
2016-03-29 4:39 ` Krzysztof Kozlowski
2016-03-24 13:36 ` [PATCH 0/3] cpufreq: dt: Create platform device from generic code Arnd Bergmann
2016-03-24 14:06 ` Viresh Kumar
2016-03-24 14:16 ` Arnd Bergmann
2016-03-25 4:41 ` Viresh Kumar [this message]
2016-03-28 15:05 ` Viresh Kumar
2016-03-29 13:22 ` Arnd Bergmann
2016-03-29 14:02 ` Viresh Kumar
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=20160325044124.GN22062@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=arnd.bergmann@linaro.org \
--cc=arnd@arndb.de \
--cc=heiko@sntech.de \
--cc=kgene.kim@samsung.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=mmcclint@codeaurora.org \
--cc=rjw@rjwysocki.net \
--cc=xf@rock-chips.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).