linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: slash.tmp@free.fr, mmcclint@codeaurora.org,
	Rafael Wysocki <rjw@rjwysocki.net>,
	arnd.bergmann@linaro.org
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
	kgene.kim@samsung.com, xf@rock-chips.com, heiko@sntech.de,
	k.kozlowski@samsung.com
Subject: Re: [PATCH V3 0/4] cpufreq: dt: Create platform device from generic code
Date: Wed, 20 Apr 2016 15:25:57 +0530	[thread overview]
Message-ID: <20160420095557.GF12019@vireshk-i7> (raw)
In-Reply-To: <cover.1459325515.git.viresh.kumar@linaro.org>

On 30-03-16, 13:45, Viresh Kumar wrote:
> Multiple platforms are using the generic cpufreq-dt driver now, and all
> of them are required to create a platform device with name "cpufreq-dt",
> in order to get the cpufreq-dt probed.
> 
> Many of them do it from platform code, others have special drivers just
> to do that.
> 
> It would be more sensible to do this at a generic place, where all such
> platform can mark their entries.
> 
> The first patch fixes an issue that came up with an earlier version of
> patch 2/4, but its still worth fixing it.  The second one creates a new
> driver to create platform-device based on current platform and the last
> two converts exynos platform to use this common infrastructure.
> 
> I will migrate rest of the platforms after this is accepted as the right
> way ahead.

@Matthew and @Mason,

Now that this is present in linux-next, you guys can send patches for
your platforms cpufreq support.

-- 
viresh

  parent reply	other threads:[~2016-04-20  9:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30  8:15 [PATCH V3 0/4] cpufreq: dt: Create platform device from generic code Viresh Kumar
2016-03-30  8:15 ` [PATCH V3 1/4] cpufreq: dt: Include types.h from cpufreq-dt.h Viresh Kumar
2016-03-30  8:15 ` [PATCH V3 2/4] cpufreq: dt: Add generic platform-device creation support Viresh Kumar
2016-04-13 19:46   ` Matthew McClintock
2016-03-30  8:15 ` [PATCH V3 3/4] ARM: exynos: exynos-cpufreq platform device isn't supported anymore Viresh Kumar
2016-03-30  8:30   ` Krzysztof Kozlowski
2016-03-30  8:15 ` [PATCH V3 4/4] cpufreq: exynos: Use generic platdev driver Viresh Kumar
2016-04-07  8:31 ` [PATCH V3 0/4] cpufreq: dt: Create platform device from generic code Viresh Kumar
2016-04-20  9:55 ` Viresh Kumar [this message]
2016-04-20 21:27   ` Mason
2016-04-20 22:31     ` Rafael J. Wysocki
2016-04-27 16:47   ` Mason
2016-04-27 16:57     ` Matthew McClintock
2016-04-28  2:27       ` 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=20160420095557.GF12019@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=arnd.bergmann@linaro.org \
    --cc=heiko@sntech.de \
    --cc=k.kozlowski@samsung.com \
    --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=slash.tmp@free.fr \
    --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).